Chapter 1: Fundamentals of Testing

Question 1

What are the Typical Objectives of Testing

Answer 1

Objectives vary dependent on the context (7)
 To prevent defects by evaluate work products such as requirements, user stories, design, and
code
 To verify whether all specified requirements have been fulfilled
 To check whether the test object is complete and validate if it works as the users and other
stakeholders expect
 To build confidence in the level of quality of the test object
 To find defects and failures thus reduce the level of risk of inadequate software quality
 To provide sufficient information to stakeholders to allow them to make informed decisions,
especially regarding the level of quality of the test object
 To comply with contractual, legal, or regulatory requirements or standards, and/or to verify the
test object’s compliance with such requirements or standards

Question 2

What is test analysis?

Answer 2

The activity that identifies test conditions by analyzing the test basis.-requirements

Question 3

What is test basis?

Answer 3

The body of knowledge used as the basis for test analysis and design.

Question 4

What is validation?

Answer 4

checking whether the system will meet user and other

stakeholder needs in its operational environment(s).

Question 5

What is the main objective of acceptance testing?

Answer 5

To confirm that the system works as expected
and satisfies requirements. Another objective of this testing may be to give information to
stakeholders about the risk of releasing the system at a given time.

Question 6

What is the test object?

Answer 6

The work product to be tested.

Question 7

What is Debugging?

Answer 7

Debugging is the development activity that finds, analyzes, and fixes such defects. Subsequent
confirmation testing checks whether the fixes resolved the defects

Question 8

What is Quality assurance?

Answer 8

focused on adherence to proper processes, in order to provide confidence that the
appropriate levels of quality will be achieved.

Question 9

What is root cause analysis?

Answer 9

Detect and remove the causes of defects, along with the properapplication of the findings of retrospective meetings to improve processes

Question 10

What is the difference between Defects, Root Causes and Effects?

Answer 10

Defects can be analyzed to identify their root causes, so as to reduce the occurrence of similar defects in
the future. effect is the flaw that is in production

Question 11

What are the Seven Testing Principles?

Answer 11

1. Testing shows the presence of defects, not their absence
2. Exhaustive testing is impossible
3. Early testing saves time and money
4. Defects cluster together
5. Beware of the pesticide paradox
6. Testing is context dependent
7. Absence-of-errors is a fallacy

Question 12

What are the main activities of the Test Process?

Answer 12

Test planning
  Test monitoring and control 
 Test analysis 
 Test design
  Test implementation
  Test execution
  Test completion

Question 13

What is the Test planning?

Answer 13

Test planning involves activities that define the objectives of testing and the approach for meeting test
objectives within constraints imposed by the context

Question 14

What is Test monitoring and control

Answer 14

Test monitoring involves the on-going comparison of actual progress against planned progress using any
test monitoring metrics defined in the test plan

Question 15

What is Test analysis

Answer 15

What to test? the test basis is analyzed to identify testable features and define associated test
conditions.
1. Analyzing the test basis appropriate to the test level being considered
2. Evaluating the test basis and test items to identify defects of various types- omissions, unclarities..
3. Identifying features and sets of features to be tested
4. Defining and prioritizing test conditions for each feature
5. Capturing bi-directional traceability between each element of the test basis and the associated
test conditions

Question 16

What is Test design?

Answer 16

How to test?
During test design, the test conditions are elaborated into high-level test cases
 Designing and prioritizing test cases and sets of test cases
 Identifying necessary test data to support test conditions and test cases
 Designing the test environment and identifying any required infrastructure and tools
 Capturing bi-directional traceability between the test basis, test conditions, and test cases

Question 17

What is Test implementation?

Answer 17

The testware necessary for test execution is created and/or completed,
including sequencing the test cases into test procedures

Question 18

Test Implementation Major Activities?

Answer 18

 Developing and prioritizing test procedures, and, potentially, creating automated test scripts
 Creating test suites from the test procedures and (if any) automated test scripts
 Arranging the test suites within a test execution schedule in a way that results in efficient test
execution (see section 5.2.4)
 Building the test environment (including, potentially, test harnesses, service virtualization,
simulators, and other infrastructure items) and verifying that everything needed has been set up
correctly
 Preparing test data and ensuring it is properly loaded in the test environment
 Verifying and updating bi-directional traceability between the test basis, test conditions, test
cases, test procedures, and test suites

Question 19

What is Test Execution?

Answer 19

During test execution, test suites are run in accordance with the test execution schedule.
Test execution includes the following major activities:
 Recording the IDs and versions of the test item(s) or test object, test tool(s), and testware
 Executing tests either manually or by using test execution tools
 Comparing actual results with expected results
 Analyzing anomalies to establish their likely causes (e.g., failures may occur due to defects in the
code, but false positives also may occur (see section 1.2.3)
 Reporting defects based on the failures observed (see section 5.6)
 Logging the outcome of test execution (e.g., pass, fail, blocked)
 Repeating test activities either as a result of action taken for an anomaly, or as part of the
planned testing (e.g., execution of a corrected test, confirmation testing, and/or regression
testing)
 Verifying and updating bi-directional traceability between the test basis, test conditions, test
cases, test procedures, and test results.

Question 20

What is Test completion?

Answer 20

Collect data for experience,
 Checking whether all defect reports are closed, entering change requests or product backlog
items for any defects that remain unresolved at the end of test execution
 Creating a test summary report to be communicated to stakeholders
 Finalizing and archiving the test environment, the test data, the test infrastructure, and other
testware for later reuse
 Handing over the testware to the maintenance teams, other project teams, and/or other
stakeholders who could benefit from its use
 Analyzing lessons learned from the completed test activities to determine changes needed for
future iterations, releases, and projects
 Using the information gathered to improve test process maturity

Question 21

What are the Test Work Products?

Answer 21

Test work products are created as part of the test process
1. Test planning work products -> test plans, exit criteria
2. Test monitoring and control work products -> test reports, including test progress reports
3. Test analysis work products-> Test analysis work products include defined and prioritized test conditions, each of which is ideally bidirectionally traceable to the specific element(s) of the test basis it covers
4. Test design work products -> Test design results in test cases and sets of test cases to exercise the test conditions defined in test analysis, ident of test data, env..
5. Test implementation work products -> test suites, schedule, Test procedures and the sequencing of those test procedures
6. Test execution work products->Documentation on status, Documentation on which tc was executed, Defect reports
7. Test completion work products-> summary reports, action items for improvement of subsequent
projects or iterations, change requests or product backlog items, and finalized testware.

Question 22

What is Traceability between the Test Basis and Test Work Products?

Answer 22

maintain traceability throughout the test process between each element of the test basis and the various test work products associated with that element
 Analyzing the impact of changes
 Making testing auditable  Meeting IT governance criteria
 Improving the understandability of test progress reports and test summary reports to include the
status of elements of the test basis (e.g., requirements that passed their tests, requirements that
failed their tests, and requirements that have pending tests)
 Relating the technical aspects of testing to stakeholders in terms that they can understand
 Providing information to assess product quality, process capability, and project progress against
business goals