A. The test approach that will be applied at system integration testing.

B. A detailed identification of the resources that will carry out structural testing in the first iteration.

C. A description of how the test cases are cross-referenced to requirements in the test management tool.

D. A list of the names of the testers who will carry out the performance testing for the final iteration.

A. Which project will be selected to perform the tool pilot?

B. What are the problems we are trying to address?

C. How will the change process be managed?

D. Is customized training available?

E. How will the implementation be organized?

F. Do we have a set of tool requirements to validate the tool against?

G. Has there been sufficient comparison of tools?

A. i and ii and v and vi

B. i and ii and iv and vi

C. ii and iii and iv and v

D. i and ii and iii and vi

A. Keyword-driven testing cannot be used with test execution tools

B. Expected results for tests are not required because the tool generates expected results

C. Data-driven testing cannot be used with test execution tools

D. Recorded manual tests may become unstable in use

A. 전달된 코드의 모든 결함을 감지 및 제거하고 모든 테스트가 프로젝트에 설정된 품질 표준을 준수하는지 확인합니다.

B. 소프트웨어의 신뢰성을 측정하고 항상 99.99% 이상인지 확인

C. 과거 프로젝트에서 결함의 근본 원인을 식별하고 학습한 내용을 사용하여 프로세스를 개선하여 결함 수를 줄이는 데 도움이 됩니다.

D. 코딩 모범 사례에서 모든 편차를 감지하고 수정되었는지 확인합니다.