Testing throughout the software life cycle
- 1. UIN SUSKA RIAU FAKULTAS SAINS DAN TEKNOLOGI PRODI SISTEM INFORMASI Oleh : Miftahul Jannaty 11453201835
- 3. Testing is not a stand-alone activity. It has its place within a software development life cycle model and therefore the life cycle applied will largely determine how testing is organized.
- 4. SOFTWARE DEVELOPMENT MODELS 1. V-model 2. Iterative life cycle 3. Testing within a life cycle model
- 6. V-model
- 8. Testing within a life cycle model 1. for every development activity there is a corresponding testing activity 2. each test level has test objectives specific to that level 3. the analysis and design of tests for a given test level should begin during the corresponding development activity; 4. 4. testers should be involved in reviewing documents as soon as drafts are avail able in the development cycle. there are several characteristics of good testing:
- 9. TEST LEVELS • may include testing of functionality and specific non-functional characteristics such as resource-behavior (e.g. memory leaks), performance or robustness testing, as well as structural testing (e.g. decision coverage). Component testing • tests interfaces between components, interactions to different parts of a system such as an operating system, file system and hardware or interfaces between systems Integration testing • concerned with the behavior of the whole system/product as defined by the scope of a development project or product. It may include tests based on risks and/or requirements specification, business processes, use cases, or other high level descriptions of system behavior, interactions with the operating system, and system resources. System testing
- 10. 1. Testing of function (functional testing) 2. Testing of software product characteristics (non-functional testing) 3. Testing of software structure/architecture (structural testing) 4. Testing related to changes (confirmation and regression testing) TEST TYPES: THE TARGETS OF TESTING
- 12. Copy Right by Miftahul Jannaty