Download to read offline
Uploaded byAjeng Savitri
Software Testing Documentation
The document discusses the importance of documentation in software testing. It notes that documentation is needed to record test implementation and results, and helps direct testing and reuse tests. There are different types of test documentation, including test plans, specifications, and analysis reports. Effective documentation provides benefits like training, communication, maintenance, and historical reference. Test documentation should be maintained throughout the software development life cycle.
More Related Content
![Testing concepts [3] - Software Testing Techniques (CIS640)](https://cdn.slidesharecdn.com/ss_thumbnails/testing-concepts-170926174731-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Similar to Software Testing Documentation
More from Ajeng Savitri
Software Testing Documentation
- 1. MEETING 15 SOFTWARE TESTING DOCUMENTATION SOFTWARETESTING By : Ajeng Savitri Puspaningrum, M.Kom
- 2. OBJECTIVE • Learning Howto Document Software Testing Process
- 3.
- 4. 4 DEFINITION • Documentation isthe process of recording the implementation of the test and the results obtained from the test. • Computer testing is not very complex to formalize the process, therefore documentation is an integral part of the formalization of testing.
- 5. 5 • Test documentationis essential for directing testing and 'reuse' of program tests during maintenance. • The test documentation will provide further guidance on updating. • Tests must be wrapped in the same standard documentation which is entirely part of the documentation system, furthermore, the documentation will make it easier to 'update' and 'reuse'.
- 6. 6 • A softwaretest documentation typically tracks : • The kind of tests conducted, • The parameters and conditions that are applied to them, • The involved employees, and • The outcome. • It also varies with the testing phases to reflect changing aims.
- 7. 7 PURPOSE OF DOCUMENTATION 1.Training 2. Instruction 3. Communication 4. Setting performance standards 5. System maintenance 6. Historical reference
- 8. 8 USE OF TESTDOCUMENTATION • Test documentation should be an integral part of the application documentation. • The standard documentation of the data processing will be of a specific form and has a broad range of test documentation that will provide guidance and maintenance instructions. • The type and extent of documentation depending on the extent to which the documentation will be used.
- 9. 9 Test documentation beginsat the requirements stage and continues over the life of the project. A test process that defines boundaries at each stage of the documentation life cycle.
- 10. 10 THE BENEFITS OFDOCUMENTATION • Checking the correctness of the requirements/needs. • Help users understand 'data processing'. Help users to understand the application system. • Provide justification for test resources. Help determine test risk. • Create test transactions and evaluate test results. • Retest the system. • Analyze the effectiveness of the test.
- 11. 11 MAIN AREAS OFDOCUMENTATION The four main areas of documentation 1. User documents 2. System Documents 3. Software Document 4. Operation documents
- 12. 12 TEST DOCUMENTATION TYPE Ingeneral, test documentation is divided into two categories, namely: 1. Test Plan Documentation : • Contains a plan for testing the application system, including detailed specifications, descriptions, test procedures, and test data reduction and criteria. 2. Test Analysis Documentation : • Contains analysis of test results and conclusions, demonstrated abilities and deficiencies, and also application instructions in its implementation.
- 13. 13 • Documentation canbe done manually or automatically, in general automation is needed according to the needs. • It is prioritized to test transactions and the expected results of transactions through reading machine media. • Experience has shown that machine-readable documentation is easier to update over time and more effective than manually creating documentation.
- 14. 14 TEST DOCUMENTATION RESPONSIBILITY •The responsibility for preparing test documents depends on the team assigned the responsibility. • For example, if a Project Team is responsible for testing, then the team prepares and maintains the test documentation, but when an Independent Team is formed, they will hand over the responsibility to the team. • The team formed is responsible for maintaining test documentation
- 15. 15 • Test documentationprovides further direction for each period, many sections are involved in this process including : • 'data processing' personnel, • users, and • test professionals who each contribute to the test documentation, but • individuals or groups will be assigned responsibility for related documentation. • The recommended approach in testing application systems is to form a Test Team, which in turn will be designated as responsible for the entire test lifecycle and during maintenance.
- 16. 16 TEST DOCUMENTATION STORAGE •Test documentation is part of a documentation system, which will contribute to the documentation system. • However, the test documentation must reflect as test documentation and not be mixed with other documentation. • It is recommended that each form of documentation is stored according to its form.
- 17. 17 • The testplan document must be stored in a different container from the test results documentation. • Each form is entered in an outline table that contains part of the documentation information and the placement of that information. • For example, information about computer media is stored in a bibliography.
- 18. 18 TEST PLAN DOCUMENTATION •The test plan framework is followed by a pattern with application system testing, in which the framework contains the plan, test specifications, and how the test evaluation is carried out as well as a description of the test itself. • Information in the test plan is minimal during the requirements phase but is continued throughout the entire development life cycle.
- 19. 19 1. Discussion-1: GeneralInformation • Scope • Summary • Reference 2. Discussion-2: Plan (Plan for application system test) • Software Description • Milestones • Testing 3. Discussion-3: Specifications and Evaluation • Specifications (requirements, application functions, relationship functions, progress testing) • Methodology and constraints. • Evaluation 4. Discussion-4: Test Description • Description Test carried out Description of Test steps The test plan documentation contains 4 topics, namely:
- 20. 20 TEST ANALYSIS REPORTING DOCUMENTATION •Documentation of the test analysis reporting is the result of the test that the analysis results are recorded and is a report of each part that is analyzed. • The information contained in this documentation can be used to evaluate the effectiveness of the work of the test process department. • The analysis resulting from testing various applications provides an indication of whether the process running effectively or not. • This information can be used to modify and define test methods by the process organization.
- 21. 21 The test analysisreporting documentation contains 4 sections, namely: 1. Discussion-1: General Information • Summary • Scope • Reference 2. Discussion-2: Test Results and Conclusions • Identification of tests on data performance (static and dynamic) • Conclusions obtained. 3. Discussion-3: Conclusion Software Functions. • Identify the performance of software functions. • Conclusions obtained. 4. Discussion-4: Summary Analysis • Application system capabilities • Application system deficiencies • Recommendations and Estimated • Opinions
- 22. References Chopra, R. (2018).Software Testing: Principles and Practices. Mercury Learning & Information. 02 Majchrzak, T. A. (2012). Improving Software Testing: Technical And Organizational Developments. Springer Science & Business Media. 03 Myers, G. J., Sandler, C., & Badgett, T. (2012). The Art Of Software Testing. John Wiley & Sons. 04 Perry, W. E. (1983). A structured approach to systems testing. Prentice-Hall, Inc. 01 Singh, Y. (2011). Software Testing. Cambridge University Press 05
- 23. THANK YOU Insert theSubtitle of Your Presentation