3.2 Testing In SDLC (Doshi) Flashcards
Unit testing:
Testing for individual program or module
Characteristics of unit testing:
(1) Testing is done by the developer as and when individual program or module is ready.
(2) No need to wait till completion of full software.
(3) White box approach (i.e. testing of internal program logic) is applied in unit testing
Integrated testing:
(1) Testing for an accurate flow of information between two or more system.
(2) Connection of modules is tested
System testing
It’s a full-fledged test which Includes stress test, load test, volume test, recovery test, security test, and performance test
The primary reason for system testing:
The primary reason for system testing is to evaluate the entire system functionality.
Final Acceptance testing
Final Acceptance Testing includes
i) Quality Assurance Testing (QAT
(ii) User Acceptance Testing (UAT)
Regression testing
Regression = act of going back,
System testing includes:
(i) Recovery testing
(ii) Security testing
(iii) Load testing
(iv) Volume testing
(v) Stress testing
(vi) Performance testing.
ISACA will try to confuse us with three terms i.e. regression testing, sociability testing and interface testing.
Please remember difference between the three.
Regression
(dictionary meaning- ‘to return’) is test to check again that changes/modifications have not introduced any new errors.
Sociability
(dictionary meaning- ‘’ability to have companionship with others’) is test to determine adoptability of new system to settle in existing environment.
Integration
(dictionary meaning-‘to connect’) is test to ensure flow of information between two or more system is correct and accurate.
In any given scenario, for unit testing appropriate strategy is
white box approach (as both involve testing of internal logic).
In any given scenario, test data should be
designed as per live workload for accurate test result.
In any given scenario, test environment
should always be used (i.e. test should not be conducted in live/production environment).
