Girmiti Software provides a variety of business services that enable efficiency, increase performance and drive innovation to help organizations meet their business goals.
Acceptance Testing is a critical phase of any 'systems' project and requires significant participation by the 'End Users'. To be of real use, an Acceptance Test Plan should be developed in order to plan precisely, covering end-to-end business scenarios, the means by which 'Acceptance' will be achieved. Girmiti’s approach is from the business user perspective to ensure the system satisfies their requirements. Girmiti’s User Acceptance Team help software vendors and business software users assure, that their software is “functionally fit for use” and working as expected.
Expertise on both the business and technical sides of testing has enabled us to create innovative approaches that deliver accelerated results. We use an established testing methodology and employ a wide range of industry-standard testing tools that leverage established methodologies to provide your organization with superior software quality, enhanced business readiness and real competitive advantage. We work hard to encourage a spirit of innovation in all of our testing professionals and to share continually what we learn with customers. Girmiti' domain knowledge has led us to work with client’s right from the requirement definition stage and to effectively participate and manage the user acceptance testing process.
Analysis of business requirements
Creation of UAT test plan
Identify test scenarios
Create UAT test cases
Preparation of test data (Production like Data)
Run the test cases
Record the results
Confirm business objectives
One of the most important activities in the UAT is to identify and develop test scenarios. These test scenarios are derived from the following documents:
Business Use Cases
Process Flow Diagrams
Business Requirements Document (BRD)
System Requirements Specification (SRS)
The Girmiti UAT test plan outlines the strategy that will be used to verify and ensure an application meets its business requirements. It documents entry and exit criteria for UAT, test scenarios and test cases approach and timelines of testing.
Identifying the test scenarios with respect to high level business process and create test cases with clear test steps. Test Cases should sufficiently cover most of the UAT scenarios. Business Use cases are input for creating the test cases.
It is best advisable to use live data for UAT. Data should be scrambled for privacy and security reasons. Girmiti testers are expertise and familiar with the data base flow.
Executing test cases and reporting bugs if anything. Re-testing bugs once fixed. Utilizing test management tools for execution.
Build strong set of Automated Acceptance Test cases which can be run for every release
Business Analysts or Girmiti UAT Testers will confirm sign off mail the UAT testing. After sign-off the product is good to go for production.
Before moving into production, following needs to be considered:
No critical defects open
Business process works satisfactorily
UAT Sign off meeting with all stakeholders
Girmiti’s User Acceptance Testing Services validate end-to-end business process, system transactions and user access, confirms the system or application is functionally fit for use and behaves as expected. Also, identifies areas where user needs are not included in the system or the needs are incorrectly specified or interpreted in the system.
Product knowledge transfer
UA test planning
Executing test cases
Reporting and documenting defect found during UAT
Girmiti recognizes that the specific focus during UAT should be in terms of the exact real world usage of the application. Our UAT testing will be done in an environment that simulates the real world or production environment. The test cases are written using real world scenarios for the application. The test team develops test scenarios, and scenario-based testing is used to conduct User Acceptance Testing.
The Key Deliverables of Girmiti’s User Acceptance Testing:
The Test Plan- Outlining the testing strategy
The User Acceptance Test cases – Helping the team to effectively test the application
The Test Log – A log of all the test cases executed and the actual results
Defect Log - A log of all the defects
User Sign Off – Customer buy-in, indicating customer finds the product delivered to their satisfaction
For more information, please contact us at firstname.lastname@example.org