Which do you prefer, acceptance testing or functional testing?
When asked a question about which process you prefer, it is best to answer by picking the one you use and then describing why you prefer it. Your rationale should discuss the benefits of the process, the technology it employs, and the operational advantages realized from using it. If you have done your research, you also can choose the process currently used by the employer to confirm that you will fit into their operations seamlessly.
"When given the option, I prefer functional testing to verify my code. This is because a functional test confirms that the product we developed works and performs the tasks we redesigned it for. The alternative is acceptance testing. This validates that we developed the product that the end-user requested and needs. It typically addresses whether the software solves the problem for the end-user. When using functional testing, it is important to clearly understand the end-users issue and the type of software they need to address it. Doing this enables the functional test to simultaneously perform the acceptance test."
Community answers are written by other candidates practicing this set. Reading how others frame the same question is one of the fastest ways to sharpen your own.
Anonymous Answer
I prefer functional testing. The purpose of functional testing is to verify that the application performs as intended by checking its behavior and output for various inputs and user interactions. It confirms that the product works and performs the tasks it was designed for. If the needs of the end-user are understood, then functional testing can also perform as acceptance testing to validate that the end user's goals and needs are met.
Marcie's Feedback
Can you also explain within your answer what acceptance testing is so it's easier to compare the two? Otherwise, you've done an excellent job explaining what functional testing is and why you prefer it. Great job!
