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

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.

Structural Testing

Structural Testing is the type of testing in which user should have the knowledge of the code because in this testing user need to check the structure of the system. Structural Testing is White Box Testing.