13 April,2013 by Jack Vamvas
Software testing and the test life cycle is critical to software development. My understanding is not always the same as other team members
I’ve made a note of the software testing terms I’ve heard in the last two weeks and how I define them .
A solid project plan covers all or a subset of these tests , also known as the testing life cycle , depending on the project. Generally the order goes from unit test progressing to the Acceptance test.
Unit test – Testing smallest isolatable unit performed by Engineers
Unit test suite – A collection of unit tests performed by Engineers
Integration test – Testing two components or more
Systems test – Do all components work together on an integrated system.
Glass-box (white-box) testing – Testing all the parts with full knowledge of how things work
Black-box testing – Test the public interface , without knowledge of the inner workings
Regression testing – Tests to reproduce bugs. A repeatable test
Smoke test – A quick test to ensure all parts of the system are working OK
Functional test – Test all components against a specification.
Acceptance test – The customer test
Performance test – Testing against benchmarks for user response times
WorkLoad test – Testing a “typical” workload for user response times
Stress test – testing a higher than normal workload , to identify breaking points