.
An inspection may be led by a trained moderator who shall not be the author
An inspection shall follow a formal process based on rules and checklists with entry and exit criteria
The main purpose of an inspection is to check the conformance to specifications an standards
An inspection can be performed within a peer group
Cann't be determined
3
6
9
Decision table testing, Use case testing, State transition testing
Exploratory testing, State transition testing, Control flow testing
Decision table testing, Use case testing, Control flow testing
Use case testing, Statement testing, State transition testing
Perform bug isolation to find the conditions that cause the crash
Do a root cause analysis
Try to identify the code fragment causing the problem
Report the incident as is without any further action
1 test case for statement coverage; 1 test case for branch coverage
1 test case for statement coverage; 2 test case for branch coverage
2 test case for statement coverage; 2 test case for branch coverage
1 test case for statement coverage; 3 test case for branch coverage
Only V is inherently reactive
III, IV and V are inherently reactive
All file strategies, I, II, III, IV and V are inherently reactive strategies
All five test strategies, I, II, III, IV and V are inherently preventive strategies
All are common test objectives.
I, II, III, and V are common test objective
I, III, IV and V are common test objectives
II and V are common test objectives
The absence of errors fallacy
The contrasting mindset of developers and testers
The fundamental testing process
The Contribution of testing to higher quality
0.00,0.01,50.00,50.01
-0.01,0.00,25.00,49.99,50.00,50.01,75.00
0.00,0.01,50.00,70.00
0.00,20.00
10.0, 28.0
0.2, 0.9, 29.5
12.3
0.4, 0.5, 25.0, 25.1
To allow non expert testers to participate in test execution
To identify special test conditions
To augment systematic techniques
To go beyond tests created with formal techniques
Factors I, II, and III are important to successful deployment of a test tool, bu IV and V are not important.
All these factors are important to successful deployment of a test tool
Factor I is important to successful deployment of a test tool, but II, III, IV and V are not important
Factors I, III, IV, and V are important to successful deployment of a test tool, but II is not important
A tester performing maintenance testing.
A tester performing exhaustive testing.
A tester's curious mindset.
A tester's effective communication with development.
An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests.
The process of intentionally adding known defects to those already in the component or system for the purpose of monitoring the rate of detection and removal, and estimating the number of remaining defects.
A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made, and to design tests specifically to expose them.
The ability of a system or component to continue normal operation despite the presence of errorneous inputs.
"It doesn't matter, really, since the customer's will be satisfied as long 80% of the tests pass."
"Depending on the customer's reaction to some of the bugs that affect those tests, we might have contractual problems with acceptance and final payment."
"Oh, I'm sorry, I shouldn't have mentioned those tests and their status, as that's not appropriate test progress monitoring data."
"All software should always be released completely defect free, and this software does not meet that standard."
A development life cycle where code is written by two programmers sitting at a single computer.
A development life cycle where a project is outsourced to a number of development teams.
A development life cycle where a project is broken into a number of iterations
A development life cycle where a project has multiple test levels,Which are referred to as iterations
Data that exists(for example, in the database)before a test is executed and that affects or is affected by the component or system under test
A statement of test objectives, and possibly test ideas on how to test
A scripting technique that uses data files to contain not only test data and expected results,but also keywords related to the application being tested.
A scripting technique that stores test input and expected results in a table or spreadsheet,so that a single control script can execute all of the tests in the table
II is useful for IV during V; I is useful for III during VI.
II is useful for IV during V; but I is not useful for III during VI.
I is useful for IV during V; II is useful for III during VI.
I is not useful for IV during V; but II is useful for III during VI.
Eliminate the possibility that there are no remaining undiscovered bugs.
Find new bugs through repetition of the same tests.
Measure the quality of software in terms of defects found
Find, analyze, and remove the causes of failures
Test1,invalid1,fail;test1,valid1,success.
Test0,valid0,,success:test1,invalid1,fail;test1,valid1,success:test2,invalid2,
Test1,invalid1,fail;test1,valid1,fail.
test0,valid0,,success.
Experience based test
Component tests
Structure based test
Specification based tests
The test team is isolated from the rest of the project team.
Independent testers can verify assumptions that other people made
The test team is seen as responsible for the delays.
Independent testers see other and different defects, and are unbiased
Experience based
Specification based
Structure based
Static testing
You have identified a product risk that should be considered for testing.
You have identified a project risk which is unlikely to affect testing.
Response time is not a quality attribute for e commerce applications
The application's performance will fail to meet requirements during testing
A step by step presentation by the author of a document in order to gather information and to establish a common understanding of its contents
A review characterized by documented procedures and requirements
A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken.
Analysis of software artifacts, e.g. requirements or code, carried out without execution of these software artifacts.
5
15
2
3
Random testing
Pesticide paradox
Early testing
Absence of error fallacy
Productivity Improvements
Improved communication within the team
Reduced testing cost and time
Reduced post release support costs.
Items I,II,IV, and V belong in an incident report.
None of this information belongs in an incident report.
All of this information belongs in an incident report.
Items I,II and III belong in an incident report.
Non functional
Change related
Structural
Functional
The effect on the component or system when it is being measured
A skeletal or special purpose implementation of a software component, used to develop or test a component that calls or is otherwise dependent on it.
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.
A test environment needed to conduct a tester
Testing of a previously tested program following modification.
The assessment of the impact of a change to the layers of development documentation,test documentation and components
The process of assessing identified risks to estimate their impact and probability of occurrence.
Testing the changes to an operational system or the impact of a changed environment to an operational system
A synonym for confirmation testing
Testing to determine the reliability of a software product
Testing that runs test cases that failed the last time they were run
Testing of a previously tested program following modification
This excerpt belongs in the impact section of an IEEE 829 incident report
This excerpt does not conform to best practices in terms of tester/developer communications
This excerpt belongs in the incident description section of an IEEE 829 incident report.
This excerpt belongs in an IEEE 829 test log,not an IEEE 829 incident report
i,ii,iii,iv is correct
iv, ii is correct
i,ii,iii and iv are incorrect
Iii,is correct I,ii,iv are incorrect.
I,ii,iii are true and iv is false
I,iii,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
Find as many defects as possible.
Show that the system works before we ship it.
Prevent defects through early involvement.
Reduce the overall level of product risk.
State transition diagram
Decision table
BVA
ECP
Id, iic, iiia, ivb
id, iib, iiia, ivc
Ib, iia, iiid, ivc
ic, iid, iiia, ivb
Obtain good test coverage.
Find as many faults as possible.
Test whatever is easiest to test.
Test high risk areas.
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.