Acceptance Testing - Definition
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
- Marketing, Advertising, Sales & PR
- Accounting, Taxation, and Reporting
- Professionalism & Career Development
Law, Transactions, & Risk Management
Government, Legal System, Administrative Law, & Constitutional Law Legal Disputes - Civil & Criminal Law Agency Law HR, Employment, Labor, & Discrimination Business Entities, Corporate Governance & Ownership Business Transactions, Antitrust, & Securities Law Real Estate, Personal, & Intellectual Property Commercial Law: Contract, Payments, Security Interests, & Bankruptcy Consumer Protection Insurance & Risk Management Immigration Law Environmental Protection Law Inheritance, Estates, and Trusts
- Business Management & Operations
- Economics, Finance, & Analytics
What is Acceptance Testing?
Acceptance testing, part of a quality assurance program, can be described as a performance testing metric that tests whether a product has acceptable standards before it is put on the market for sale. It is commonly used in engineering and software industries.
The major types of acceptance testing are;
- Operational testing,
- Alpha & Beta Testing,
- Regulation Acceptance testing, and
- Contract Acceptance testing.
Academics research on Acceptance Testing
- Toward preprototype user acceptance testing of new information systems: implications for software project management, Davis, F. D., & Venkatesh, V. (2004). IEEE Transactions on Engineering management, 51(1), 31-46. Miscalculations in specifying requirements have been identified as a significant contributor to failures in the software project. It is imperative for developers of information systems to verify requirements by preempting acceptance of a new framework for workplace built on user evaluations of its requirements evaluated at the pre-launch phase of the development project. Ideally, before the sneak peek test of the prototype. Meanwhile, the customary mindset among system developers assumes that each user must be clever to use at least a functioning prototype of the new system before assessment which reflects future behavior can be provided.
- Automated acceptance testing: A literature review and an industrial case study, Haugset, B., & Hanssen, G. K. (2008, August). Automated acceptance testing: A literature review and an industrial case study. In Agile 2008 Conference (pp. 27-38). IEEE. A novel testing idea in agile software is called Automated acceptance testing. It offers a future for improved communication and collaboration. Existing literature was summarized by this paper, and it also provides a case study from an industrial vantage point on the adoption of automated acceptance testing. It also aims at establishing an updated overview of prior knowledge to add value to practice and future research. We established the possibilities of the proposed benefits and agreed that subsequent research and enhancements are required to access the optimal potential value.
- Testing the technology acceptance model across cultures: A three country study, Straub, D., Keil, M., & Brenner, W. (1997). Testing the technology acceptance model across cultures: A three country study. Information & management, 33(1), 1-11. IS researchers popularized the use of the technology acceptance model(TAM) to gain an in-depth knowledge of the application and adoption of information systems. While TAM already mainstreamed in North America, little has been done to popularized its use globally. With the advancement in business and operations, there is a need to test the application of the TAM model in the different cultural milieu. This study provides comparison across three countries: United States, Japan, and Switzerland. The outcome of the study shows that TAM works in the United States and Switzerland, but not in Japan.