Agile Test Documentation

Test Strategy (Domain Specific where we need to be)

o V&V (traceability/examples within USs) TW to send list.
o Code coverage % limits
o Automated functional test coverage %
o Build pipeline
o Agile Testing quadrants.
o Security Test requirements
o NFR approach (part of CI & formal in integration test env)
o 100% User story coverage.
o Approach to defect handling (Agile)
o Approach to defect handling (Waterfall)
o Test Env Strategy

Test Plan (individual to projects within domain)

o QA Methodology (Agile (BDD, TDD)/Waterfall/V-model)
o Agile e.g. Requirements will change, fixed cost & time. Will be made
up of release, but release content will change throughout
process/sprints.
o Define toolset to be used, CI, deployment, NFT, code coverage
analysis.
o Approach to test automation.
o Exit criteria is essentially all user stories as defined by PO being
completed to definition of done. DOD needs to be included in Test
Plan.
o Document is living
o HW requirements (Selenium, test env, CI, multi-browser testing).
o Test Env requirements
o NFR toolset & requirements.
o Dependencies
o Assumptions
o Constraints (items out of scope/cant physically be tested).

Test Exit Report

o Per release not per sprint.
o Summary of info to allow PO & stakeholders to make informed
choice to launch or not.
o NFR test results
o Security test results
o Functional coverage by test automation.
o Code coverage
o Exploratory testing (how many sessions, themes used & tests
automated as a result).
o Outstanding risks for launch (defects open etc)
o Define DOD that all user stories were completed against.
o Test Env config definition (i.e. software levels/versions in test vs
live).