RTI uses cookies to offer you the best experience online. By clicking “accept” on this website, you opt in and you agree to the use of cookies. If you would like to know more about how RTI uses cookies and how to manage them please view our Privacy Policy here. You can “opt out” or change your mind by visiting: http://optout.aboutads.info/. Click “accept” to agree.
Software quality assurance (SQA) testers can perform exploratory testing (ET) using test charters to focus directly on functionality and key areas of a software application and uncover defects early in the test cycle. In this presentation, we will show how test charter(s) are used as a baseline for evaluating features and detecting nonconformance early in the testing cycle. A test charter is a simpler form of test plan/test case. We list objectives as bullet points in the test charter in the ‘Areas to Test’ section, document the test execution in the ‘Test Notes’ section, and list all defects in the document. We also discuss varies types of ET and the benefits of using this approach to detect software defects. ET typically requires one 1- to 2-hour uninterrupted test session in which pair testing [1] is performed between two SQA testers. While one person tests, the other documents the results in the test charter. The goal in this time boxed session is to find as many potential issues as possible. Once the session ends, the testers review the findings and determine the next course of action. They then log defects and send questions to the appropriate subject matter experts for clarification. Basic steps in the ET process include the following: 1. SQA resource plans separate mission statements per charter 2. SQA resource lists specific areas to cover during testing 3. Execute charter 4. Review session 5. Research issues 6. Document issues