Acceptance testing BPTS
(unchanged)
Validating systems, products, business processes or services to determine whether the acceptance criteria have been satisfied.
SFIA 9 is in development
- SFIA 9 beta due in early July 2024
- SFIA 9 planned for publication October 2024
This is a prototype for SFIA 9. It is subject to change before publication.
Guidance notes
(modified)
Activities include, but are not limited to:
- setting and applying standards for acceptance testing
- planning, identifying, designing, managing, executing and reporting on the outcomes of acceptance tests
- encouraging effective and efficient collaboration with a range of relevant stakeholders
- requesting and enabling formal acceptance of systems, products or services
- creating measurable acceptance criteria related to functional and non-functional requirements, features, business processes, user stories and business rules
- devising acceptance test cases and scenarios from acceptance criteria
- enabling exploratory testing by stakeholders to discover unexpected behaviours
- deploying model office testing to simulate real-world working practices and system usage.
The acceptance testing approach will be based on the context of the work and may be selected from predictive (plan-driven) or adaptive (iterative/agile) approaches.
Understanding the responsibility levels of this skill
Where lower levels are not defined...
- Specific tasks and responsibilities are not defined because the skill requires a higher level of autonomy, influence, and complexity in decision-making than is typically expected at these levels. You can use the essence statements to understand the generic responsibilities associated with these levels.
Where higher levels are not defined...
- Responsibilities and accountabilities are not defined because these higher levels involve strategic leadership and broader organisational influence that goes beyond the scope of this specific skill. See the essence statements.
Developing skills and demonstrating responsibilities related to this skill
The defined levels show the incremental progression in skills and reponsibilities.
Where lower levels are not defined...
You can develop your knowledge and support others who do have responsibility in this area by:
- Learning key concepts and principles related to this skill and its impact on your role
- Performing related skills (see the related SFIA skills)
- Supporting others with tasks (generic examples are provided by the essence statements for each level)
Where higher levels are not defined...
- You can progress by developing related skills which are better suited to higher levels of organisational leadership.
Levels
Defined at these levels: | 2 | 3 | 4 | 5 | 6 |
Click to learn why SFIA skills are not defined at all 7 levels.
Show/hide extra descriptions and levels.
Level 1
Acceptance testing: Level 2
(modified)
Assists in planning and preparing acceptance tests for systems, products, business processes or services.
Assists in collecting feedback from acceptance testing.
Acceptance testing: Level 3
(modified)
Follows agreed standards and techniques to devise test cases and scenarios based on pre-defined acceptance criteria.
Analyses and reports on test activities, results, issues and risks.
Acceptance testing: Level 4
(modified)
Develops acceptance criteria related to functional and non-functional requirements, business processes, features, user stories and business rules.
Designs and specifies test cases and scenarios to test that systems, products and services fulfil the acceptance criteria and deliver the predicted business benefits.
Collaborates with project colleagues and stakeholders involved in the analysis, development and operation of products, systems or services to ensure accuracy and comprehensive test coverage.
Analyses and reports on test activities, results, issues and risks including the work of others.
Acceptance testing: Level 5
(unchanged)
Plans and manages acceptance testing activity.
Specifies the acceptance testing environment for systems, products, business processes and services. Manages the creation of acceptance test cases and scenarios. Ensures that defined tests reflect realistic operational conditions and required level of coverage.
Ensure tests and results are documented, analysed and reported to stakeholders, and required actions taken. Highlights issues and risks identified during testing to stakeholders.
Provides authoritative advice and guidance on planning and execution of acceptance tests.
Acceptance testing: Level 6
(unchanged)
Leads the implementation and delivery of the organisation's approach to acceptance testing.
Engages with senior stakeholders to secure organisational commitment and resources needed for effective acceptance testing.
Reports on any significant risks or issues related to acceptance testing and recommends required actions.
Develops organisational policies, standards, and guidelines for acceptance testing. Develops acceptance testing capabilities and methods for the organisation.