Hi, To what extent you want to test a SW? Do you have access to source code? If yes, then white box after the unit test you should check integrity between different parts. When you have a complete system ready and then you need system-level testing. There is no one-size-fits-all in SW testing. The company opted for different methods the way they want to gain confidence in their product. Regards,
The answer is probably: It depends. What is best for your company/application may not be best for all. But it is helpful to have a consistent method for software development process, including documentation of initial software requirement/specifications, test planning, test execution, and defect tracking for iterations. Then some process for change management to allow for changing requirements over time.
Our company evaluated several programs and ended up using HP ALM (Application Lifecycle Management) for final testing on product hardware, and Target Process/Agile for the subsystem software development to delivery phase.
We can not select one method as the best. It depends on your software and the accessibility of codes. In some situations, you should use the unit method, sometimes the black/white box method, and sometimes integration or other methods.