Title ISTQB CTFL 4.0 notes.pdf ✅

TestoMeter Chapter 1 : Testing Fundamentals Objective of Testing Finding Defects Evaluating work products Verify requirements have been fulfilled Verify test object complies with contractual, legal, and regulatory requirements Provide information to stakeholders to make informed decisions Building Confidence in the quality of test object Validating test object is complete and works as expected by the stakeholder Whole team Approach Everyone is responsible for quality Testers work closely with other team members to ensure that the desired quality levels are achieved. This includes collaborating with business representatives to help them create suitable acceptance tests and working with developers to agree on the test strategy and decide on test automation approaches. Testers can thus transfer testing knowledge to other team members and influence the development of the product. Depending on the context, the whole team approach may not always be appropriate. For instance, in some situations, such as safety-critical, a high level of test independence may be needed. Error, Defect, Failure ● Error→Defects→Failure ● Error- human mistake is error. ● E.g.- 1. In a banking app, a developer mistakenly assigns the wrong interest rate calculation formula. 2. Developer forgets to handle null pointers in the code of A video streaming service. ©TestoMeter Pvt. Ltd. | +91 9096153227 | https://testometer.co.in 1
TestoMeter ● Defect—Difference between expected and actual result ● E.g. 1. Incorrect interest calculation, 2. Null pointer exceptions occur causing app to crash ● Failure- Inability of system to deliver correct result ● E.g. 1. Users' bank statements show incorrect interest earnings, causing financial discrepancies, 2. Users experience frequent app crashes 1.4.1. Test Activities and Tasks Test planning consists of defining the test objectives and then selecting an approach that best achieves the objectives within the constraints imposed by the overall context. Test monitoring and control. Test monitoring involves the ongoing checking of all test activities and the comparison of actual progress against the plan. Test control involves taking the actions necessary to meet the objectives of testing. ©TestoMeter Pvt. Ltd. | +91 9096153227 | https://testometer.co.in 2
TestoMeter Test analysis includes analyzing the test basis to identify testable features and to define and prioritize associated test conditions, together with the related risks and risk levels . The test basis and the test objects are also evaluated to identify defects they may contain and to assess their testability. Test analysis is often supported by the use of test techniques (see chapter 4). Test analysis answers the question “what to test?” in terms of measurable coverage criteria. Test design includes elaborating the test conditions into test cases and other testware (e.g., test charters). This activity often involves the identification of coverage items, which serve as a guide to specify test case inputs. Test techniques can be used to support this activity. Test design also includes defining the test data requirements, designing the test environment and identifying any other required infrastructure and tools. Test design answers the question “how to test?”. Test implementation includes creating or acquiring the testware necessary for test execution (e.g., test data). Test cases can be organized into test procedures and are often assembled into test suites. Manual and automated test scripts are created. Test procedures are prioritized and arranged within a test execution schedule for efficient test execution. The test environment is built and verified to be set up correctly. Test execution includes running the tests in accordance with the test execution schedule (test runs). Test execution may be manual or automated. Test execution can take many forms, including continuous testing or pair testing sessions. Actual test results are compared with the expected results. The test results are logged. Anomalies are analyzed to identify their likely causes. This analysis allows us to report the anomalies based on the failures observed. Test completion activities usually occur at project milestones (e.g., release, end of iteration, test level completion) for any unresolved defects, change requests or product backlog items created. Any testware that may be useful in the future is identified and archived or handed over to the appropriate teams. The test environment is shut down to an agreed state. The test activities are analyzed to identify lessons learned and improvements for future iterations, releases, or projects. A test completion report is created and communicated to the ©TestoMeter Pvt. Ltd. | +91 9096153227 | https://testometer.co.in 3
TestoMeter stakeholders. RTM ● Establish traceability throughout the test process between the test basis, testware associated (e.g., test conditions, risks, test cases), test results, and detected defects ● Advantages: ○ Ensure requirements coverage and test coverage ○ Traceability of test results to risks ○ Impact analysis become easy ○ Testing become auditable ○ Helps to meet IT governance criteria/agency. Chapter 2: Testing Through SDLC Good Testing Practices ● For every software development activity, there is a corresponding test activity ● Different test levels have specific and different test objectives ● Test analysis and design for a given test level begins during the corresponding development phase of the SDLC (Early Testing Principle) ● Testers are involved in reviewing work products as soon as drafts of this documentation are available (Shift Left approach) Testing as a Driver for Software Development TDD, ATDD and BDD are similar development approaches, where tests are defined as a means of directing development. Each of these approaches implements the principle of early testing and follows a shift-left approach, since the tests are defined before the code is written. They support an iterative development model. ©TestoMeter Pvt. Ltd. | +91 9096153227 | https://testometer.co.in 4