Option D is close, but it's got the concepts mixed up. Acceptance testing is about verifying the system against the customer's requirements, not just how it interacts with other systems.
Haha, I bet the developer who wrote option A was just trying to confuse us. Clearly, system integration testing and acceptance testing have different purposes.
Option B seems a bit off. Developers typically do both system integration testing and acceptance testing, but the acceptance testing is done on behalf of the customer.
I think option C is the correct answer. System integration testing focuses on verifying how different components of the system work together, while acceptance testing checks if the system meets the customer's requirements.
I see. So, system integration testing is like making sure the system plays well with others, while acceptance testing is like making sure it does what it's supposed to do.
I agree with Nieves. System integration testing is more about verifying interfaces, while acceptance testing is all about meeting the requirements set by the customer.
I think the difference is that system integration testing focuses on interfaces with other systems, while acceptance testing is about compliance to requirements.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Abel
5 days agoElza
6 days agoCarole
8 days agoAlana
18 days agoRickie
3 days agoJaney
19 days agoAntonio
21 days agoNieves
25 days ago