What test roles (or parts in the testing process) is a developer most likely to perform?

What test roles (or parts in the testing process) is a developer most likely to perform?

(i) Executing component integration tests.

(ii) Static analysis.

(iii) Setting up the test environment.

(iv) Deciding how much testing should be automated.
A . (i) and (ii)
B . (i) and (iv)
C . (ii) and (iii)
D . (iii) and (iv)

Answer: A

Explanation:

(i) Executing component integration tests is usually done by developers. Developers are usually responsible for unit and component integration testing. Independent testing usually follows at system and acceptance test levels.

(ii) Static analysis is usually done by developers because: it requires an understanding of the code and therefore the person doing this needs skills in the programming language; and it can be done as soon as the code is written. Therefore it is quick and effective for the developer to do it. The risk of a lack of test independence can be mitigated by performing independent system and acceptance testing.

(iii) Setting up the test environment is an activity typically performed by a tester. It may require support from developers and staff from other departments and on some occasions environments could be set up by developers. However, it is a task that could be done by a tester rather than a developer.

(iv) Deciding how much testing should be automated is typically a decision made by the test leader, who will consult other staff in the decision-making process. Developers may be involved and their skills may be required to automate some tests. However, the decision on how much to automate should not be made by developers.