Sec1

Knowledge portal provides users with comprehensive information on specific tools, various roles, streamlined processes, and transformation initiatives. This Portal also has the estimator Tool, which will standardize the way how Solution Architects develop estimates for new initiatives. The intake process identifies standards and processes that will be utilized for the intake of work requests. The goal is to create a unified method across digital teams that will streamline all work requests in order to use our resources to their fullest capabilities.

Acceptance Testing

Published date: April 15, 2024, Version: 1.0

Purpose: Acceptance testing evaluates whether the system meets the specified business requirements and is ready for deployment. It involves end-users or client representatives validating the system against their expectations and use cases. Acceptance testing aims to gain confidence that the system functions as intended, aligns with the users' needs, and meets the business objectives.

Acceptance testing consists of two main types: User Acceptance Testing (UAT) and Business Acceptance Testing (BAT).

Quick Links

System Regression ART Regression Risk Based Testing In-Sprint Regression

User Acceptance Testing (UAT)

focuses on verifying the system's functionality, usability, and suitability for real-world scenarios. End-users or representatives from the target user group are actively involved in UAT. They perform test cases, execute common workflows, and provide feedback based on their experience and expectations. UAT aims to ensure that the system meets the users' requirements, is intuitive to use, and fulfills their specific needs. Refer to UAT guidelines for details.

Business Acceptance Testing (BAT)

assesses the system's alignment with business processes, rules, and objectives. It involves representatives from the business or stakeholders who evaluate the system's functionality and its impact on business operations. BAT verifies that the system supports the desired workflows, complies with regulatory requirements, and meets the organization's strategic goals.

During acceptance testing, the focus is identifying defects and validating the system's fitness for deployment. Any deviations or discrepancies from the expected behaviour or requirements are documented, reported, and addressed before the system is ready for deployment.

Acceptance testing provides a final validation step, ensuring that the system meets the business needs and is ready to be put into production. It helps build confidence among stakeholders and end-users, ensuring that the developed software meets their expectations and will contribute to the business's success.

Product Owners, End-users, or Client representatives

Acceptance testing is typically performed towards the end of the software development lifecycle, after completing system testing. It is the final phase of testing before the system is deployed.

qTest: A test management tool that facilitates the organization and tracking of acceptance test cases and results.
JIRA: A project management and issue-tracking tool that can be utilized for managing acceptance testing tasks, test cases, and defects.