Challenges in Automotive Testing

Even the highest quality organizations have tradeoffs when it comes to their testing coverage.

In Japan, Europe, and the United States, automotive manufacturers are aiming to enhance automotive functions by using software; in Japan in particular, Toyota, Nissan, Honda, Mazda, and Subaru are all adding endless amounts of software to their vehicles in the form of convenience and safety features. In the automotive industry, many companies are original equipment manufacturers (OEM), meaning they make most (if not all) of their automotive parts in-house. While, Sony, Panasonic, and other electronic manufacturing companies are researching ways to increase their sales and profit, automotive companies’ business is growing. According to statista.com, in 2016, the sales value of the automotive software market in Japan was valued at ¥525 billion Japanese yen ($4.8 billion USD); it is expected to reach ¥747.5 billion Japanese yen ($6.8 billion USD) in 2020 and ¥995 billion Japanese yen ($9 billion USD) by 2030. Japanese automotive brands have a history of being the most reliable vehicles; thus, they will want to ensure their software is reliable as well.

According to J.D. Power’s 2019 U.S. Vehicle Dependability Study, which ranks brands based on problems per 100 vehicles, two out of the top three brands are Japanese: Lexus is number 1 and Toyota is number 3. Infiniti and Subaru make it above the industry average and Nissan is just 1 ranking below said average.

The Tradeoffs of Coverage and Risk

Even the highest quality organizations have tradeoffs. As old as Software Testing, automotive Software Testing has the same issues. Technology aside, companies have to balance coverage and risk with cost and time. High risk needs more testing, more people, more time, and more coverage. Less risk often means less testing, less time, and less coverage. No one wants to make these tradeoffs-especially in a safety-critical product. In a regulated industry, these tradeoffs are often standardized levels demanded for regulatory compliance.

With shift-left, more Continuous Delivery (CD), and modern development techniques like test-driven development (TDD),  there is more unit testing and more meaningful measures of unit test code coverage. The tradeoff may become coverage at what level. Test coverage at the unit level, API or service level, or testing at the UI level. The following is an example of how a Japanese software company balances coverage and risk on an automotive project.

The level of quality demanded varies from project to project. Testing car navigation may require a different level of quality than an electronic control unit (ECU) because car navigation does not have the direct power to kill people.

On the other hand, ECU testing—a system that can kill—requires a higher quality, such as 100% C1 (code-level Branch Coverage) coverage rate, sometimes requiring MC/DC coverage rate. The aforementioned testing terms form a basic idea and methodology toward quality assurance for automotive software.

In one automotive project, we had to balance and think about the size of software and the relationship between ECU and the car navigation system (see Figure below).

· Software size of car navigation = Huge (using Linux, Car Play, Android Auto)

· Software size of ECU = Small (Using automotive specific OS or non-OS)

Based on risk:

· It is okay to cover 100% coverage testing with small ECU software.

· It may be okay to cover less than 20% code-level coverage testing with huge car navigation software.

Figure – Relationship between ECU and the car’s navigation system

Treated separately, it is okay to not communicate between ECU and car navigation. When the ECU communicates too much with car navigation, there could be critical quality problems. But, automotive software is becoming increasingly complicated every year.

And the size of data communication between the ECU and the car navigation is increasing. An ECU may use Open Source Software (OSS). The ECU may also use virtualized software. The ECU may communicate to the internet or cloud directory. ECU software may be updated by internet.

By themselves, the pieces can be tested. The integration and many workflow paths can be very complicated and leave data under various loads—calling for different testing than code coverage.

The Other Side of the Equation: More People, More Time

We are test engineers. We need to prepare ourselves to strategize such kind of complicated automotive Software Testing tradeoffs between coverage and risk. Currently, there are too many developers compared to testers working for automotive system software.

I worked at Microsoft’s headquarters in Seattle. At that time on my team, more than 300 development and testing engineers worked together to develop Windows OS.

From my experience, I can say the team ratio is that there are many more developers compared to testers working on automotive software than the entirety of the Windows OS.

Interestingly, some companies are afraid to increase the size of the software test teams.

I believe that software engineers for the automotive industry need to prepare and improve their effectiveness and efficiency for production. Both developer-level unit testing skills are needed as well as integration level testing. Test Automation is key to increase productivity.

Summary

How much testing is enough? This is a question as old as software itself. How much gets covered in the test effort is a balance of risk, cost, and schedule. These days, with shift-left mindset of more developer testing, how much test coverage happens at each level is the new question.

To achieve the level of quality and testing needed for safety-critical applications, highly skilled engineers are needed for both developer level testing and all aspects of Test Automation.

Juichi Takahashi
Juichi Takahashi is CEO of LogiGear Japan. Prior to LogiGear, Dr. Takahashi held engineering and technical leadership positions in software testing and QA for prominent software/IT and product companies including Microsoft, SAP, and Sony. Throughout his career, he has gained extensive experience in testing and quality engineering. Dr. Takahashi is the author of the top-selling testing book in Japan, “Software Testing for Beginners.”

The Related Post

All too often, software development organizations look at automating software testing as a means of executing existing test cases faster. Very frequently there is no strategic or methodological underpinning to such an effort. The approach is one of running test cases faster is better, which will help to deliver software faster. Even in organizations that ...
I got some comments on my post “Test Everything all the Time” — most notably people commenting that it’s impossible to test “everything”. I can’t agree more. The intention of the post was to make the point that we need to be able to test “everything we can” all the time. That is, you should ...
Bringing in experts can set you up for automation success. Test automation isn’t easy when your testing gets beyond a few hundred test cases. Lots of brilliant testers and large organizations have, and continue to struggle with test automation, and not for lack of effort. Everyone understands the value of test automation, but few testing ...
There is no one recipe to make big testing a big success. It takes planning and careful execution of the various aspects, like test design, infrastructure and organization – a mix that can be different for each situation in which you may find yourself. In writing about big testing, the first question that comes up ...
From automotive Software Testing standards, testing techniques, and process, this article is an in-depth guide for those looking to transfer their existing skills to this exciting industry. For the Software Car, autonomous driving gets most of the hype, but most overlook the fact that there is so much more to Software Testing for the automotive ...
“Happy About Global Software Test Automation: A Discussion of Software Testing for Executives” Author: Hung Q. Nguyen, Michael Hackett, and Brent K. Whitlock Publisher: Happy About (August 1, 2006) Finally, a testing book for executives!, November 17, 2006 By Scott Barber “Chief Technologist, PerfTestPlus” Happy About Global Software Test Automation: A Discussion of Software Testing ...
One of the basic challenges with test automation is adoption. I can’t tell you how many times I’ve cataloged licenses for a company and found out they already have many different automation software packages, none of which is being used. Traditionally I’ve been told that is because the tools don’t work and that the teams ...
From cross-device testing, to regression testing, to load testing, to data-driven testing, check out the types of testing that are suitable for Test Automation. Scene: Interior QA Department. Engineering is preparing for a final product launch with a deadline that is 12 weeks away. In 6 weeks, there will be a 1 week quality gate, ...
Utility: A program that performs a specific task related to the management of computer functions, resources, or files, as password protection, memory management, virus protection, and file compression. Tool: A program or application that software development teams use to create, debug, maintain, or otherwise support other programs and applications. The term usually refers to programs that can be combined together ...
Every once in a while a book is put together that should be read by every person with a relationship to software development. This book is one of them. Everyone dreams of automating their software testing, but few make it a reality. This down-to-earth book contains stories of 28 teams that went for it, including ...
With the new year just around the corner, here’s a look at the Test Automation trends that have the potential to dominate. DevOps is being relied upon more than ever. With there being strong Market Drivers for the adoption of DevOps, the need for Test Automation has also never been greater. But what’s next after ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe