Your supervisor said, "Integration testing is a waste of time. If each program is tested adequately, integration testing is not needed. Instead, we should move on to system testing as soon as possible. If modules don't interact properly, we'll handle it then." Do you agree or disagree with this comment?

Question

Guest

Computers & Technology

9 February, 02:56

Your supervisor said, "Integration testing is a waste of time. If each program is tested adequately, integration testing is not needed. Instead, we should move on to system testing as soon as possible. If modules don't interact properly, we'll handle it then." Do you agree or disagree with this comment?

+4

Answers (1)

Know the Answer?

Kameron Ellis · Answer 1

No

Explanation:

Integration testing is done to see how the various modules of a program works together to achieve a goal or a functional requirement. So skipping this phase is a bad idea. This is because, these programs are part of a bigger system, and they are expected to function properly by working with each other when the system is up and running. The integration phase is used to check how these programs function together to achieve a goal. So skipping this phase might not be a good idea. More so, if this phase is performed, any issues concerning program integration would have been dealt with thoroughly. This will will prevent tackling a lot of problems coupled with integration problem in the other phases after integration.