CTFL CHAPTER 3 AND 6

3.2 REVIEW PROCESS

100

Which is not a type of review? a. Walkthrough b. Inspection c. Informal review d. Management approval

d. Management approval

200

What statement about reviews is true? a. Inspections are led by a trained moderator, whereas technical reviews are not necessarily. b. Technical reviews are led by a trained leader, inspections are not. c. In a walkthrough, the author does not attend. d. Participants for a walkthrough always need to be thoroughly trained

a. Inspections are led by a trained moderator, whereas technical reviews are not necessarily.

300

What is the main difference between a walkthrough and an inspection? a. An inspection is led by the authors, whilst a walkthrough is led by a trained moderator. b. An inspection has a trained leader, whilst a walkthrough has no leader. c. Authors are not present during inspections, whilst they are during walkthroughs. d. A walkthrough is led by the author, whilst an inspection is led by a trained moderator

d. A walkthrough is led by the author, whilst an inspection is led by a trained moderator

400

The set of generic and specific conditions, agreed upon with the stakeholders ATM for permitting a process to be officially completed.

What is Exit Criteria?

500

Which of the following characteristics and types of review processes belong together? 1. Led by the author 2. Undocumented 3. No management participation 4. Led by a trained moderator or leader 5. Uses entry and exit criteria s. Inspection t. Technical review u. Informal review v. Walkthrough a. s = 4, t = 3, u = 2 and 5, v = 1 b. s = 4 and 5, t = 3, u = 2, v = 1 c. s = 1 and 5, t = 3, u = 2, v = 4 d. s = 5, t = 4, u = 3, v = 1 and 2

b. s = 4 and 5, t = 3, u = 2, v = 1

3.3. STATIC ANALYSIS BY TOOLS

100

Which statement about the function of a static analysis tool is true? a. Gives quality information about the code without executing it. b. Checks expected results against actual results. c. Can detect memory leaks. d. Gives information about what code has and has not been exercised.

a. Gives quality information about the code without executing it.

200

What statement about static analysis is true? a. With static analysis, defects can be found that are difficult to find with dynamic testing. b. Compiling is not a form of static analysis. c. When properly performed, static analysis makes functional testing redundant. d. Static analysis finds all faults.

a. With static analysis, defects can be found that are difficult to find with dynamic testing

300

Static code analysis typically identifies all but one of the following problems. Which is it? a. Unreachable code b. Undeclared variables c. Faults in the requirements d. Too few comments

c. Faults in the requirements

400

An abstract representation of the sequence and possible changes of state of data objects, where the state of an object is any of: creation, usage, modification or destruction.

What is Data flow?

500

A sequence of events (paths) in the execution through a component or system.

What is Control flow?

6.1 TYPES OF TEST TOOL

100

Which tools help to support static testing? a. Static analysis tools and test execution tools. b. Review process support tools, static analysis tools and coverage measurement tools. c. Dynamic analysis tools and modeling tools. d. Review process support tools, static analysis tools and modeling tools.

d. Review process support tools, static analysis tools and modeling tools.

200

Which test activities are supported by test harness or unit test framework tools? a. Test management and control. b. Test specification and design. c. Test execution and logging. d. Performance and monitoring.

c. Test execution and logging.

300

What are Tools that support performance and monitoring?

o dynamic analysis tool; o performance-testing, load-testing and stress-testing tool; o monitoring tool.

400

A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system. [After TMap]

What is a driver?

500

A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect.

Debugging tool

6.2 EFFECTIVE USE OF TOOLS: POTENTIAL BENEFITS AND RISKS

100

What are the potential benefits from using tools in general to support testing? a. Greater quality of code, reduction in the number of testers needed, better objectives for testing. b. Greater repeatability of tests, reduction in repetitive work, objective assessment. c. Greater responsiveness of users, reduction of tests run, objectives not necessary. d. Greater quality of code, reduction in paperwork, fewer objections to the tests.

b. Greater repeatability of tests, reduction in repetitive work, objective assessment.

200

What is a potential risk in using tools to support testing? a. Unrealistic expectations, expecting the tool to do too much. b. Insufficient reliance on the tool, i.e. still doing manual testing when a test execution tool has been purchased. c. The tool may find defects that aren't there. d. The tool will repeat exactly the same thing it did the previous time.

a. Unrealistic expectations, expecting the tool to do too much.

300

Which of the following are advanced scripting techniques for test execution tools? a. Data-driven and keyword-driven b. Data-driven and capture-driven c. Capture-driven and keyhole-driven d. Playback-driven and keyword-driven

a. Data-driven and keyword-driven

400

Which of the following would NOT be done as part of selecting a tool for an organization? a. Assess organizational maturity, strengths and weaknesses. b. Roll out the tool to as many users as possible within the organization. c. Evaluate the tool features against clear requirements and objective criteria. d. Identify internal requirements for coaching and mentoring in the use of the tool.

b. Roll out the tool to as many users as possible within the organization.

500

What are the benefits to using tools to support testing?

• reduction of repetitive work; • greater consistency and repeatability; • objective assessment; • ease of access to information about tests or testing.

6.3 INTRODUCING A TOOL INTO AN ORGANIZATION

100

Which of the following would NOT be done as part of selecting a tool for an organization? a. Assess organizational maturity, strengths and weaknesses. b. Roll out the tool to as many users as possible within the organization. c. Evaluate the tool features against clear requirements and objective criteria. d. Identify internal requirements for coaching and mentoring in the use of the tool

b. Roll out the tool to as many users as possible within the organization.

200

Which of the following is a goal for a proof-of-concept or pilot phase for tool evaluation? a. Decide which tool to acquire. b. Decide on the main objectives and requirements for this type of tool. c. Evaluate the tool vendor including training, support and commercial aspects. d. Decide on standard ways of using, managing, storing and maintaining the tool and the test assets.

d. Decide on standard ways of using, managing, storing and maintaining the tool and the test assets.

300

What are the 6 factors tthat are important in selecting a tool?

• assessment of the organization's maturity (e.g. readiness for change); • identification of the areas within the organization where tool support will help to improve testing processes; • evaluation of tools against clear requirements and objective criteria; • proof-of-concept to see whether the product works as desired and meets the requirements and objectives defined for it; • evaluation of the vendor (training, support and other commercial aspects) or open-source network of support; • identifying and planning internal implementation (including coaching and mentoring for those new to the use of the tool).

400

What is one of the ways to do a proof-of-concept as the first thing done with a new tool?

Have a pilot project

500

The objectives for a pilot project for a new tool are:

• to learn more about the tool (more detail, more depth); • to see how the tool would fit with existing processes or documentation, how those would need to change to work well with the tool and how to use the tool to streamline existing processes; • to decide on standard ways of using the tool that will work for all potential users (e.g. naming conventions, creation of libraries, defining modularity, where different elements will be stored, how they and the tool itself will be maintained); • to evaluate the pilot project against its objectives (have the benefits been achieved at reasonable cost?).