Staying on track with ISO 26262 to meet automotive functional safety standards requires automation throughout the software lifecycle. The result is cost-effective production of high-assurance software ...
Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with content, and download exclusive resources. Jinsong Yu shares deep architectural insights ...
In this example I will show how you can perform a standard Maven build whilst keeping your unit and integration tests in separate packages. Other techniques specify using either a naming convention or ...
Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with content, and download exclusive resources. Jinsong Yu shares deep architectural insights ...
This example shows how to split unit and integration tests using Maven and JUnit categories. It is especially useful for existing test suites and can be implemented in minutes. This has been a very ...
Really, you only need to do two kinds of testing: Unit testing (to make sure that your individual components work) and end-to-end testing (to make sure your application works). Anything else is just a ...
The only tests that are useful are tests that actually give useful information about your code unit test or not. If a unit test is fully covered by an integration test, and you have to run the ...
How evolving standards, design-for-test strategies, and automation are shaping efficient production testing for 2.5D and 3D ...
When it comes to embedded engineering, toolchains are the worst. Getting a new toolchain up and running correctly is often hard, and often prone to breaking when the IDE or other software is upgraded.
Some results have been hidden because they may be inaccessible to you
Show inaccessible results
Feedback