Difference between revisions of "Acceptance Test Level"

From Glitchdata
Jump to navigation Jump to search
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 +
Acceptance Testing is often the responsiblity of the customers or users of a system; other stakeholders may be involved as well. The goal in acceptance testing is to establish confidence in the system, parts of the system or specific non-functional characteristics of the system.
  
 +
==Inputs==
 +
* User Requirements
 +
* [[System Requirements]]
 +
* [[Use Cases]]
 +
* Business processes
 +
* Risk Analysis Reports
  
 +
==Test Objects==
 +
* [[Business Process]]es on fully integrated system
 +
* Operational and maintenance processes
 +
* User Procedures
 +
* Forms
 +
* Reports
 +
* [[Configuration Data]]
  
  
 +
==Methods==
 +
* [[Operational Acceptance Testing]]
 +
* [[Contract Acceptance Testing]]
 +
* [[Regulation Acceptance Testing]]
 +
* [[Alpha Testing]]
 +
* [[Beta Testing]]
  
  

Latest revision as of 23:49, 4 September 2016

Acceptance Testing is often the responsiblity of the customers or users of a system; other stakeholders may be involved as well. The goal in acceptance testing is to establish confidence in the system, parts of the system or specific non-functional characteristics of the system.

Inputs

Test Objects


Methods


Related