QA Exploratory Test Charter template

QA Exploratory Test Charter templateProject Name: <XX> Author <XX>

Project ID: <XX> DATE: XX/XX/20XX

Application Name: <XX> Version: <XX> • INTRODUCTION: NOTE: <REMOVE OR REPLACE ALL BLUE

TEXT>• Exploratory test charters are used for keeping track of an

exploratory test session’s findings. Exploratory testing itself is a documented approach to testing a system’s functionality with an architecture that is largely unknown for the SYSTEM UNDER TEST <SUT>.

• CHARTER SESSION <NAME OR #>• The <SUT-topic> charter session will verify the system performs as

anticipated and needed with no adverse functionality or errors encountered.

• Charter: The name of the charter, which is a sentence, describing what will be explored terminated by a period. Using the following format Charter: <Portal App> <Project-Optional> <Web Page Name (Title)> <Task Item Summary>. For example: Test the Web Self-Service-Portal-registration page, validate fields for valid & invalid data

CHARTER CONTEXT

• Describes the test environment, platforms and versions, test harness, application areas covered, timeframe, and list of tasks as part of the charter.

• Coverage Area • Test Environment & URL

– EXAMPLE – Portal Dev1– EXAMPLE – https://e0.pncie.com/content/aaa-ie/b2e/english/passport.html

• Browser Platforms & Versions– EXAMPLE – IE 9.0 – EXAMPLE – Google Chrome 7.5– EXAMPLE – Mobile IOS/Android

• Test Harness– EXAMPLE – Manual test– EXAMPLE – Automation– EXAMPLE – Performance

• Application Components– EXAMPLE – Menus & Sub-Menus, Hyperlinks, Navigation, Content

Timeframe/Task Breakdown/Input Data Files

• Timeframe• Tester: Tester Name, Test Start: The start date and time• Test Duration: (30-60 mins) (60-90 mins) (90-120 mins).• Task Breakdown• EXAMPLE – BUG LOGGING

– Defect Tracker Id & Description <hyperlink>• EXAMPLE – MODIFIED/ENHANCED FUNCTIONALITY

– UI Standards Spelling, Links, Layout, Usability

– Comprehensive Functionality Prerequisites, Conditions, Constraints– Authentication SSO, Security & User Level

Access• EXAMPLE – REGRESSION/SMOKE

– Comprehensive Functionality– Input Data Files– Detail any input data required master list with file names and location for testing that cannot

be populated on-demand as part of the usual exploratory testing workflow– TestData1.xls; PolicyID.xls

CHARTER EXECUTION

• CHARTER EXECUTION• Testing Notes• “Journal” of the exploratory test. The format for this is a sentence describing what actions were taken when

testing followed by an outline to describe the observations and steps performed to complete the action described.• EXAMPLE – Open browser to landing page

– Verify header, footer, menus left navigation– Click Search Box

• EXAMPLE – Click all content hyperlinks– Open same window– Open new tab– Open new browser– Back

• Output Data Files• Test verification screen recordings, screen shots, online test journals, or master list with file names and location.• EXAMPLE – TestData1.xls; PolicyID.xls• Issues • What questions or challenges were found during the exploratory test? Each numbered issue should be described

in one or more sentences including Tracker Id & Description <hyperlink>• EXAMPLE – #2333 Issue xyz• EXAMPLE – #87565 Issue www• Bugs• What bugs were found during the exploratory test? Each numbered bug should be described in one sentences

including Tracker Id & Description <hyperlink>. The “Steps to reproduce,” as well as the “Actual Results” should be detailed in Tracker.

• EXAMPLE – #8577 Missing webpage header• EXAMPLE – #87565 Hyperlink opens incorrect page

CHARTER REPORTING SUMMARY

• CHARTER REPORTING SUMMARY• Test Design and Execution 70%• Percentage of time spent on this phase of the exploratory test• EXAMPLE – 30% design (charter documentation and preparation) 40% actual

execution = 70%• Issue Investigation & Reporting 10%• EXAMPLE -10% on emails or IM questions and brief conversations• Bug Review & Reporting 10%• EXAMPLE -10% on repeating a series of steps that appeared to return different

results but was unsubstantiated. • Session Set-up 10%• EXAMPLE -10% Percentage of time spent on this phase of the exploratory test• Charter vs Opportunity 90/10%• EXAMPLE -90% of the time was spent on expected areas of the system under test as

defined by the product team and previously reviewed and tested within the development environment versus unexpected areas as not much of the functionality was unknown upon delivery to test.