An internal developer deploys a new customer information system at a company. The system has an updated graphical interface with new fields. Which…

Acceptance testing, specifically User Acceptance Testing (UAT), is the final phase of functional testing where the system is validated by its intended end-users. In this scenario, employees test the new customer information system to confirm that its graphical interface and functionality meet their specific business needs and requirements for data entry. This process ensures the system is "fit for purpose" from the user's perspective before it is formally accepted and moved into production. It directly addresses whether the system behaves as the employees need it to.

A. Load testing: This is a non-functional test that measures system performance and stability under heavy user traffic, not its functional suitability for user needs.

B. Regression testing: This type of testing ensures that new code changes or updates have not adversely affected existing, previously working functionalities.

C. Security testing: This focuses on identifying and mitigating vulnerabilities and ensuring the system is resilient against malicious attacks, not on user-centric functional validation.

1. Sommerville

I. (2016). Software Engineering (10th ed.). Pearson. In Chapter 8

Section 8.1.3

"Testing stages

" acceptance testing is defined as "testing with customer data to check that the system meets the customer’s needs." This directly aligns with the scenario of employees validating the new system.

2. MIT OpenCourseWare. (2013). 6.170 Software Studio

Lecture 18: Testing. Massachusetts Institute of Technology. Retrieved from https://ocw.mit.edu/courses/6-170-software-studio-spring-2013/resources/mit6170s13lec18/. Slide 10 defines Acceptance Testing as being "Done by the customer to decide whether to accept the product

" which is precisely the goal described in the question.

3. Koomen

T.

& van der Aalst

L. (2007). Test Process Improvement: A practical step-by-step guide to structured testing. In Software Quality Professional

9(2)

12-22. The article describes acceptance testing as the process where "the user organization determines whether a system meets its acceptance criteria." (p. 15).