UAT Testing Case Study The Octad Project
In software development, user acceptance testing (UAT) - also called beta testing, application testing, and end user testing - is a phase of software development in which the software is tested in the "real world" by the intended audience.
This Audience is The Team we have Assembled in Nigeria
We would recommend a period of 1Month Minimum
Team Will Work Closely With IT Project Manager & Professional Software Testers and Super Admin .
The Octad UAT directly involves the intended users of the software. UAT can be implemented by making software available for a free beta trial on the internet or through an in-house testing team comprised of actual software users.
Following are the steps involved in in-house UAT:
Planning: The UAT strategy is outlined during the planning step.
The Strategy is to have a Record of all Tests Done so Vendor is aware of Pending Errors /Bugs
Landing Pages
1.Authentication of Tradesmen/Customers/Administrators
2.Transactional Processes
3.Payments/Reconciliations
4.Approvals/Closures/Logouts
Designing test cases: Test cases are designed to cover all the functional scenarios of the software in real-world usage according to the Approved Request for Propasal and Original Agreements. They are designed in a simple language and manner to make the test process easier for the testers.
The Test Processes are designed Adhoc for Each of 1 To 4 Above . and should be inexhaustible
Selection of testing team: The testing team is comprised of real-world end users.
We are looking at 3 Teams with about 2people each minimum
1.Tradesmen 2. Customers 3.Admins (BAs or 1 and 2 )
1 and 2 can and should be normal average Users While 3 should at least have some basic CMS knowledge
Executing test cases and documenting: The testing team executes the designed test cases. Sometimes it also executes some relevant random tests. All bugs are logged in a testing document with relevant comments.
We will use Slack for Logging of bugs in 3 Different Channels 1,2,3
Bug fixing: Responding to the bugs found by the testing team, the software development team makes final adjustments to the code to make the software bug-free.
We will create Bug Fixing Slack Channel that both Software Vendors (Promatics) and Testers can Verify Acceptance
Sign-off: When all bugs have been fixed, the testing team indicates acceptance of the software application. This shows that the application meets user requirements and is ready to be rolled out in the market.
UAT is important because it helps demonstrate that required business functions are operating in a manner suited to real-world circumstances and usage.
Agile Based Industry Pre Requisites
The Systems/Functional/Penetration Testing Will be Carried out by Manual and Automated Processes to meet industry Standards
We will Nominate Professional Software Testers for this .
Blog Read
User acceptance testing is often the most essential to get right. Why? Because when implemented correctly, it’s the most effective in reducing both time and cost, whilst increasing customer satisfaction. User Acceptance Testing, also known as UAT (or UAT testing), in a nutshell, is:
A process of verifying that a solution works for the user
And the key word here, is user. This is crucial because they’re the people who will use the software on a daily basis. There are many aspects to consider with respect to software functionality.
There’s unit testing, functional testing, integration testing, and system testing, amongst many others. As part of these processes, we regularly ask questions such as:
Does the application crash ? Why ? When Log it
Do all the functions accept the correct inputs and give the correct outputs?
Does the application consume only the minimum amount of resources?
What’s the load time of the application?
Whilst these are valid and essential, ultimately they’re quite meaningless – if the application doesn’t perform as the end user expects. As software artisans, we need to avoid situations such as:
Can the user use the software?
Is it really what they asked for?
Do they have trouble using it?
Does it behave exactly as anticipated?
What Is User Acceptance Testing?
User acceptance testing (UAT) is the last phase of the software testing process but With The Agile Software Dev Model We want to keep our Tests concurrent and in cases where immediate detection is required . During UAT, actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications. UAT is one of the "final" and critical software project procedures that must occur before newly developed software is rolled out to the market.
User acceptance testing (UAT), otherwise known as Beta, Application, or End-User Testing, is often considered the last phase in the web development process, the one before final installation of the software on the client site, or final distribution of it.
The goal of User Acceptance Testing is to assess if the system can support day-to-day business and user scenarios and ensure the system is sufficient and correct for business usage.
When Should You Start User Acceptance Testing
Whilst UAT – User Acceptance Testing – is essential, typically, it’s not able to be undertaken until the application is largely feature-complete. Guru99 lists 10 prerequisites, which must be met before UAT can begin. These are:
Business Requirements must be available
Application Code should be fully developed
Unit Testing, Integration Testing & System Testing should be completed
No Show stoppers, or High or Medium defects in the System Integration Test Phase
Only Cosmetic errors are acceptable before UAT
Regression Testing should be completed with no major defects
All the reported defects should be fixed and tested
Traceability matrix for all testing should be completed
UAT Environment must be ready
Sign off mail or communication from System Testing Team that the system is ready for UAT execution
Who should be involved in User Acceptance testing?
The most important peer group to include in UAT testing are “real” end users of your software. Every role and stakeholder group should be included which means that people from each group should be selected to join the UAT team.
How To Get Started With User Acceptance Testing
Firstly, the criteria which the software is considered to be “working” needs to be assembled. These are likely to be collated from the system requirements, and user stories. Next, a set of UAT test cases must be created.
A set of test steps, execution conditions and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement
Each case covers a specific usage scenario of the software. It is normally a set of actions which the user can carry out and be able to verify if the software’s worked as intended.
With these in place, the tests then have to be run and the results recorded. Were the tests successful, or did defects result? Any bugs then need to be corrected and re-tested.
Finally, assuming that everything is working as expected, an orderly sign-off needs to be completed. This is done more easily with an individual client, where they state that what they’ve received works as expected and meets their criteria.
And that’s what, why, and how of integrating User Acceptance Testing as a standard part of your web development projects. It reduces the likelihood of issues being raised, which in turn reduces the amount of work required in development and maintenance.
re-edited from various online sources for systemini.net
General OCtad Checklists for Business/User Stories for Testers
UAT Checklist
"The following checklist's purpose is to ensure that the appropriate steps have been taken to execute a user acceptance test (UAT),
to wrap up the process and ensure proper documentation has been completed. Simply choose ""Yes, No or N/A"" as it applies to the UAT process in the organization.
The criteria listed below may not apply to all organizations, however, if a column contains a ""No"" answer, it should be revisited."
Criteria Completed?
Web Project Team Awareness / Preparations
Has the project team been made aware of its role in advising on changes to business processes and procedures?
Has the project team been made aware of its role in providing support for all testing issues?
Has the project team been made aware of its role in tracking and managing website bugs?
UAT Team Preparations
Has the UAT team been defined?
Does the UAT team understand its responsibility in executing the test cases and ensuring that the final outcomes of the tests are satisfactory?
Has the UAT team been told about its role and responsibility in ensuring that all test case input sources and output results are documented?
Has the UAT team agreed that the test cases provides comprehensive and effective coverage of all aspects of functionality of the application?
Has the UAT team been told about its role in documenting bugs/problems and working with the project team to resolve problems identified during testing?
Does the UAT team understand the responsibilities and required actions for each category of problem identified during testing?
Has the UAT team been made aware of its role in accepting the results on behalf of the relevant user population?
"Does the UAT team understand that it must recognize any changes necessary to existing processes and
take a lead role in ensuring that the changes are made and communicated to other users?"
Does the UAT team understand its role in verifying performance on business critical functions?
Does the UAT team understand its role in confirming the integrity of data?
Does the UAT team understand its role in assessing system final production readiness?
Test Preparation
Has the plan for acceptance testing been created?
Have all possible system functions been described?
Is all input data available that is required for testing?
Has acceptance criteria be defined on which the completion of the acceptance test will be judged?
Have all user specific constraints been considered?
Has the testing procedure been defined?
Have test cases been created to discover contradictions between the software product and the requirements?
Have test cases been created to review whether timing constraints are met by the system?
Test Execution and Evaluation
Were all steps of the test run documented?
Was the acceptance test performed according to the test plan?
Did the users review the test results?
Are the services provided by the system in compliance with user requirements?
Were all defect documented?
Were all identified defects and issues resolved?
Did the users judge acceptability in accordance with the predetermined criteria?
Did each user sign off on output?