ISTQB Test Process
•Download as PPTX, PDF•
5 likes•8,767 views
The document provides an overview of fundamentals of testing including the testing process, psychology of testing, and exams. It describes the typical activities in a test process including test planning, monitoring and control, analysis, design, implementation, execution, and completion. For each activity, it outlines the common tasks and work products. It also discusses how human psychology and the different mindsets of testers and developers can impact testing. The document emphasizes the importance of independence in testing to avoid author bias and more effectively find defects.
Report
Share
Recommended for you
Recommended for you
Recommended for you
Recommended for you
Recommended for you
Recommended for you
More Related Content
What's hot
What's hot (20)
Similar to ISTQB Test Process
Similar to ISTQB Test Process (20)
More from HoangThiHien1
Recently uploaded
Recently uploaded (20)
ISTQB Test Process
- 3. Contents 1. Tesing process 2. Psychology of testing 3. Exam
- 4. Testing process (K2) Explain the impact of context on the test process (2) Describe the test activities and respective tasks within the test process (K2) Differentiate the work products that support the test process (K2) Explain the value of maintaining traceability between the test basis and test work products
- 5. Test process in Context Contextual factors that influence the test process for an organization: Software development lifecycle model and project methodologies Test levels and test types being considered Product and project risks Business domain Operational constraints (Budgets and resources, Timescales, Complexity, Contractual and regulatory requirements) Organizational policies and practices Required internal and external standards
- 6. Test Activities and Task Test planning Test monitoring and control Test analysis Test design Test implementation Test execution Test completion Each activity within each group of activities consist of multiple individual tasks, which would vary from one project or release to another.
- 7. Test planning Task: • Define the objectives of testing • Define the approach for meeting test objectives within constraints imposed by the context Work product: Test plan • Test basic • Tracebility information (exit criteria)
- 8. Test monitoring and control Task • Comparing actual progress against the test plan • Taking actions necessary to meet the objectives of the test plan • Checking test results and logs against specified coverage criteria • Assessing the level of component/system quality based on test results and log • Determining if more tests are needed
- 9. Test monitoring and control Work product: Test report (test progress report, Test summary report) • Audience-relevant details about the test progress as of the date of the report • Summarizing the test execution results • Address project management concerns, such as task completion, resource allocation and usage, and effort.
- 10. Test analysis Task: identify what to test • Analyzing the test basis appropriate to the test level being considered • Evaluating the test basis and test items to identify defects of various types • Identifying features and sets of features to be tested • Defining and prioritizing test conditions for each feature based on analysis of the test basis, and considering functional, non-functional, and structural characteristics, other business and technical factors, and levels of risks • Capturing bi-directional traceability between each element of the test basis and the associated test conditions
- 11. Test analysis Work products: • Test condition (include priority) • Testabel features
- 12. Task: identify how to test • Designing and prioritizing test cases and sets of test cases • Identifying necessary test data to support test conditions and test cases • Designing the test environment and identifying any required infrastructure and tools • Capturing bi-directional traceability between the test basis, test conditions, test cases, and test procedures Test design
- 13. Test design Work products: • Test cases and sets of test cases • Test data • Test environment
- 14. Task: answers the question “do we now have everything in place to run the tests? • Developing and prioritizing test procedures, and, potentially, creating automated test scripts • Creating test suites from the test procedures and (if any) automated test scripts • Arranging the test suites within a test execution schedule • Building the test environment and verifying that everything needed has been set up correctly • Preparing test data and ensuring it is properly loaded in the test environment • Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test suites Test implementation
- 15. Test implementation Work products: • Test procedures and the sequencing of those test procedures • Test suites • A test execution schedule
- 16. Test execution Task: run test • Recording the IDs and versions of the test item(s) or test object, test tool(s), and testware • Executing tests either manually or by using test execution tools • Comparing actual results with expected results • Analyzing anomalies to establish their likely causes • Reporting defects based on the failures observed • Logging the outcome of test execution (e.g., pass, fail, blocked) • Repeating test activities either as a result of action taken for an anomaly, or as part of the planned testing • Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test results
- 17. Test execution Work products: • Documentation of the status of individual test cases or test procedures (e.g., ready to run, pass, fail, blocked, deliberately skipped, etc.) • Defect reports • Documentation about which test item(s), test object(s), test tools, and testware were involved in the testing
- 18. Test completion Task: collect data from completed test activities to consolidate experience, testware, and any other relevant information • Checking whether all defect reports are closed, entering change requests or product backlog items for any defects that remain unresolved at the end of test execution • Creating a test summary report to be communicated to stakeholders • Finalizing and archiving the test environment, the test data, the test infrastructure, and other testware for later reuse • Handing over the testware to the maintenance teams, other project teams, and/or other stakeholders who could benefit from its use • Analyzing lessons learned from the completed test activities to determine changes needed for future iterations, releases, and projects • Using the information gathered to improve test process maturity
- 19. Test completion Work products: • Test summary reports • Action items for improvement of subsequent projects or iterations (e.g., following a project Agile retrospective) • Change requests or product backlog items • Finalize testware
- 20. Psychology of Testing Recall that the success of testing is influenced by psychological factors: (K1) Contrast the mindset of a tester and that of a developer. (K2)
- 21. Human Psychology and Testing Human psychology • Identifying defects may be perceived as criticism of the product and of its author • An element of human psychology called confirmation bias can make it difficult to accept information that disagrees with currently held beliefs • , it is a common human trait to blame the bearer of bad news, and information produced by testing often contains bad news
- 22. Human Psychology and Testing Ways to communicate well • Start with collaboration rather than battles. Remind everyone of the common goal of better quality systems. • Emphasize the benefits of testing • Communicate test results and other findings in a neutral, fact-focused way without criticizing the person who created the defective item. Write objective and factual defect reports and review findings. • Try to understand how the other person feels and the reasons they may react negatively to the information. • Confirm that the other person has understood what has been said and vice versa.
- 23. Tester’s and Developer’s Mindsets Developers and testers often think differently Developers Testers • Objective of development is to design and build a product • A developer’s mindset are often more interested in designing and building solutions than in contemplating what might be wrong with those solutions • Objectives of testing include verifying and validating the product, finding defects prior to release, and so forth • Tester’s mindset should include curiosity, professional pessimism, a critical eye, attention to detail, and a motivation for good and positive communications and relationships.
- 24. Tester’s and Developer’s Mindsets Independence avoids author bias and is often more effective at finding defects and failures. Independence : • Tests by the person who wrote the item under test; • Tests by another person within the same team, such as another programmer; • Tests by a person from a different organizational group, such as an independent test team
- 25. THANKS! Any questions? You can find me at @Hoang Hien/ hthien@software.misa.com.vn