Skip to main content

Acceptance Testing

Acceptance Testing is the formal testing as per the user needs, requirement and the business requirement to determine whether system satisfies the acceptance criteria and enable the user or customer to determine weather to accept the system or not.

Acceptance Testing is perform after the all errors and defects fixes in the System Testing. Acceptance Testing perform by the customer or stakeholder.Acceptance Testing is the last phase of the software testing process.



Internal Acceptance Testing is also called Alpha Testing and performed by the member of the organisation that develop the software but they are not directly involved with the project. Usually these members are from sales, marketing and product managers. External Acceptance Testing also called Beta Testing performed by the members who are the Customers, Users and Stakeholders who are not the members of the organisation.

In Acceptance Testing if there is any contract between the customer and team then on time of acceptance Test, running those Acceptance Test with ensure that no requirement is changed during meantime and  system is working as mentioned in the requirement.

Following are the Acceptance Testing Criteria that need to met before System Acceptance
  • Functional Correctness and Completeness
  • Data Integrity 
  • Data Conversion
  • Usability
  • Performance
  • Timeliness
  • Confidentiality and Availability
  • Installability and Upgradability
  • Scalability
  • Documentation
Acceptance Testing Type 
  • User Acceptance Testing
  • End User Testing
  • Operational Acceptance Testing
  • Field Testing
  • Contract Acceptance Testing 
  • Compliance Acceptance Testing
  • Alpha Testing  
  • Beta Testing
When Acceptance Testing Should Start
  • Business requirement must be Present
  • Unit Testing, Integration Testing and System Testing Completed
  • There are no showstopper bugs, high or medium bugs in System
  • Code written completely
  • Regression Testing completed with no major defects
  • All the reported defects are recorded and fixes
  • Tractability matrix for all testing must be completed
  • UAT Environment must be ready

Comments

Popular posts from this blog

Why Jmeter is best option for Performance Testing?

There are multiple tools in market for performance testing of any software but Jmeter is the best solution among all of them due to some reason listed below 1) Jmeter is the open source application so users who use this application will not to pay anything. 2) You can use Jmeter for performance of any web application,  Databases and Web Services (REST and SOAP APIs). 3) Jmeter have the user friendly UI component so it is very easy to use. 4) Jmeter can be used to simulate to put maximum number of concurrent users on a server, network or object to test its strength or to analyze overall performance under different load types. 5) Jmeter also use for functional testing for static( JavaScript and HTML) and dynamic( JSP, Servlets and AJAX) resources. 6) Jmeter provides Verity of graphical representations for performance report so it is easy to understand.

How You Can Test Database?

Now we know the Database Testing which you can learn in my last article. In this article we will discuss about the steps that need to following to test any Database. Database Tester should have some basic knowledge regarding SQL Command like DDL (create/drop),  DML (Insert/Delete/Update) and DCL (Grant/Revoke).

Causes of Software Defects

It is practically impossible that developer develop a bug free software and that software we can deliver without Testing. If the complexity of the software increased then there must be bugs that can harm the users who will use that software.