Question 1
Question
Which of the problems below BEST characterize a result of software failure?
Answer
-
Damaged reputation
-
Lack of methodology
-
Inadequate training
-
Regulatory compliance
Question 2
Question
Faults found by users are due to:
Question 3
Question
Which is not the testing objectives
Question 4
Question
Which of the following statements contains a valuable objective for a test team?
Answer
-
Prove that the remaining defects will not cause any additional failures
-
Run all of the tests that are defined for the test object as quickly as possible
-
Prove that all faults have been identified through thorough testing
-
Cause as many failures as possible so that faults can be identified and corrected
Question 5
Question
Which of these are objectives for software testing?
Answer
-
Determine the productivity of programmers
-
Eliminate the need for future program maintenance
-
Eliminate every error prior to release
-
Uncover software errors
Question 6
Question
Which of the following will be the best definition for Testing:
Answer
-
The goal / purpose of testing is to demonstrate that the program works
-
The purpose of testing is to demonstrate that the program is defect free
-
The purpose of testing is to demonstrate that the program does what it is supposed to do
-
Testing is executing Software for the purpose of finding defects
Question 7
Question
Which of the following are USUALLY stated as testing objectives?
I. Finding defects in the software
II. Reducing maintenance costs
III. Confirming that the system works
IV. Assessing the quality of the software
V. Meeting schedule milestones
Answer
-
I and II
-
I and IV
-
II, IV, and V
-
III and IV
Question 8
Question
Who would USUALLY perform debugging activities?
Answer
-
Developers
-
Analysts
-
Testers
-
Incident Managers
Question 9
Question
What is the process of analyzing and removing causes of failures in software?
Answer
-
Validation
-
Testing
-
Debugging
-
Verification
Question 10
Question
Why is testing necessary?
Answer
-
Because testing is good method to make there are not defects in the software
-
Because verification and validation are not enough to get to know the quality of the software
-
Because testing measures the quality of the software system and helps to increase the quality
-
Because testing finds more defects than reviews and inspections
Question 11
Question
The most important thing about early test design is that it:
Answer
-
Makes test preparation easier
-
Means inspections are not required
-
Can prevent fault multiplication
-
Will find all faults
Question 12
Question
Quality control is
Answer
-
Phase building activity
-
Intermediate activity
-
End of Phase activity
-
Desing activity
Question 13
Answer
-
Incorrect program behavior due to a fault in the program
-
Bug found before product Release
-
Bug found after product Release
-
Bug found during Design phase
Question 14
Question
When what is visible to end-users is a deviation from the specific or expected behavior, this is called:
Answer
-
An error
-
A fault
-
A failure
-
A defect
-
A mistake
Question 15
Question
What is failure?
Question 16
Question
How can software defects in future projects be prevented from reoccurring?
Answer
-
Creating documentation procedures and allocating resource contingencies
-
Asking programmers to perform a thorough and independent testing
-
Combining levels of testing and mandating inspections of all documents
-
Documenting lessons learned and determining the root cause of problems
Question 17
Question
Which defects are OFTEN much cheaper to remove?
Answer
-
Usability defects found by customers
-
Defects in infrequently used functionality
-
Defects that were detected early
-
Minor defects that were found by users
Question 18
Question
What is the MAIN benefit of designing tests early in the life cycle?
Answer
-
It is cheaper than designing tests during the test phases
-
It helps prevent defects from being introduced into the code
-
Tests designed early are more effective than tests designed later
-
It saves time during the testing phases when testers are busy.
Question 19
Question
Which is not a testing principle
Answer
-
Early testing
-
Defect clustering
-
Pesticide paradox
-
Exhaustive testing
Question 20
Question
The cost of fixing a fault:
Answer
-
Is not important
-
Increases as we move the product towards live use
-
Decreases as we move the product towards live use
-
Is more expensive if found in requirements than functional design
-
Can never be determined
Question 21
Question
Consider the following statements about early test design:
i. Early test design can prevent fault multiplication
ii. Faults found during early test design are more expensive to fix
iii. Early test design can find faults
iv. Early test design can cause changes to the requirements
v. Early test design takes more effort
Answer
-
i, iii & iv are true. ii & v are false
-
iii is true, I, ii, iv & v are false
-
iii & iv are true. i, ii & v are false
-
i, iii, iv & v are true, ii are false
-
i & iii are true, ii, iv & v are false
Question 22
Question
The later in the development life cycle a fault is discovered, the more expensive it is to fix. Why?
Answer
-
The documentation is poor, so it takes longer to find out what the software is doing.
-
Wages are rising
-
The fault has been built into more documentation, code, tests, etc
-
None of the above
Question 23
Question
In foundation level syllabus you will find the main basic principles of testing. Which of the following sentences describes one of these basic principles?
Answer
-
Complete testing of software is attainable if you have enough resources and test tools
-
With automated testing you can make statements with more confidence about the quality of a product than with manual testing
-
For a software system, it is not possible, under normal conditions, to test all input and output combinations.
-
A goal of testing is to show that the software is defect free.
Question 24
Question
Which of the following characterizes the cost of faults?
Answer
-
They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases.
-
They are easiest to find during system testing but the most expensive to fix then.
-
Faults are cheapest to find in the early development phases but the most expensive to fix then.
-
Although faults are most expensive to find during early development phases, they are cheapest to fix then.
Question 25
Question
Purpose of test design technique is
Answer
-
Identifying test conditions only, not Identifying test cases
-
Not Identifying test conditions, Identifying test cases only
-
Identifying test conditions and Identifying test cases
-
Identifying test conditions or Identifying test cases
Question 26
Question
Reviewing the test Basis is a part of which phase
Answer
-
Test Analysis
-
Test Design
-
Test Implementation
-
Test Closure Activities
Question 27
Question
Designing the test environment set-up and identifying any required infrastructure and tools are a part of which phase
Answer
-
Test Implementation
-
Test execution
-
Test Analysis
-
Test Design
Question 28
Question
TEST ANALYSIS ACTIVITIES
Answer
-
Analyse the test basis appropriate to the test level being considered
-
Evaluating the test basis and test items to identify defects of various types
-
Identifying features and sets of features to be tested
-
Define and prioritize test conditions for each feature based on analysis of the test basis
-
Capturing bi-directional traceability between test basis and test conditions
-
Developing and prioritizing test procedures, and, potentially, creating
automated test scripts
-
Designing and prioritizing test cases and sets of test cases
-
Analyzing anomalies to establish their likely causes
Question 29
Question
TEST DESIGN ACTIVITIES
Answer
-
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
-
Capturing bi-directional traceability between test basis and test conditions
-
Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test suites
-
Executing tests either manually or by using test execution tools
-
Define and prioritize test conditions for each feature based on analysis of the test basis
-
Reporting defects based on the failures observed
-
Preparing test data and ensuring it is properly loaded in the test environment
Question 30
Question
TEST IMPLEMENTATION ACTIVITIES
Answer
-
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
-
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
-
Define and prioritize test conditions for each feature based on analysis of the test basis
-
Designing the test environment and identifying any required infrastructure and tools
-
Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test results
-
Reporting defects based on the failures observed
Question 31
Question
TEST EXECUTION ACTIVITIES
Answer
-
Recording the IDs and versions of the test item(s) or test object, test tool 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
-
Reporting defects based on the failures observed
-
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
-
Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test results
-
Analyse the test basis appropriate to the test level being considered
-
Designing and prioritizing test cases and sets of test cases
Question 32
Question
TEST COMPLETION ACTIVITIES
Answer
-
Checking whether all defect reports are closed
-
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
-
Designing the test environment and identifying any required infrastructure and tools
-
Preparing test data and ensuring it is properly loaded in the test environment
-
Reporting defects based on the failures observed
-
Define and prioritize test conditions for each feature based on analysis of the test basis
Question 33
Question
Which of the following is not a part of the Test Implementation and Execution Phase
Question 34
Question
Test Implementation and execution has which of the following major tasks?
i. Developing and prioritizing test cases, creating test data, writing test procedures and optionally preparing the test harnesses and writing automated test scripts.
ii. Creating the test suite from the test cases for efficient test execution.
iii. Verifying that the test environment has been set up correctly.
iv. Determining the exit criteria.
Answer
-
i,ii,iii are true and iv is false
-
i,iv are true and ii is false
-
i,ii are true and iii,iv are false
-
ii,iii,iv are true and i is false
Question 35
Question
Which of the following are MAJOR test implementation and execution tasks?
I. Comparing results
II. Creating test suites
III. Reporting discrepancies
IV. Logging the outcome
V. Analyzing lessons learned
Answer
-
II, III and IV
-
I, III, IV and V
-
I, II, III and IV
-
III, IV and V
Question 36
Question
If an expected result is not specified then:
Answer
-
We cannot run the test
-
It may be difficult to repeat the test
-
It may be difficult to determine if the test has passed or failed
-
We cannot automate the user inputs
Question 37
Question
Which activity in the fundamental test process creates test suites for efficient test execution?
Answer
-
Test Implementation
-
Test execution
-
Test Analysis
-
Test design
Question 38
Question
Which of the following MAIN activity is part of the fundamental test process?
Question 39
Question
Which of the following is a KEY test closure task?
Answer
-
Ensuring proper environment setup
-
Writing a test summary report
-
Assessing the need for additional tests
-
Finalizing and archiving testware
Question 40
Question
Which of the following is a part of Test Closure Activities?
i. Checking which planned deliverables have been delivered
ii. Defect report analysis.
iii. Finalizing and archiving testware.
iv. Analyzing lessons.
Answer
-
i, ii, iv are true and iii is false
-
i, ii, i are true and iv is false
-
i, iii, iv are true and ii is false
-
All of above are true
Question 41
Question
Testings Contributions to Success
Answer
-
User Requirement
-
System Requirement
-
Global Design
-
Detailed Design
-
IMPLEMENTATION
-
Static testing
-
Dynamic testing
-
End phase
-
Analysis phase
-
Desing phase
Question 42
Question
THREE MIS CONCEPTIONS
Answer
-
Testing only consists of running test cases
-
Testing only involves the execution of the component or system being tested
-
Testing focuses entirely on verification of requirements
-
Test consist in detect defects
Question 43