.
I, III
I, IV, V
I, V
II, IV
Regression testing is intended to find side-effects after changes have been applied to the system under test
Regression testing is a technique for system testing and acceptance testing only
Regression testing can be used in any level of testing, but must be done after white-box testing has been finished
Regression testing is an alternative term for re-testing
An operation on a system by a user, with no regards to the systems response
A response of on e system to users interaction with other, integrated systems
An description of an environment in which a system needs to operate
A sequence of transactions between a user and a system to achieve a certain goal
I, II and IV
III and V
I, III and V
II, III and V
3
2
1
4
Priority
Severity
Difficulty
Urgency
Intrusive test tools are tools that do not exhibit the probe-effect
Testing tools allow developers do testing. Use of such tools changes the role of the test team
Testing tools can be use by both developers and testers
Use of testing tools is effective only when done as part of a test automation system
Pair programming is an alternative term for code inspection
Pair programming is done with developer and tester pairing together
Pair programming is, among other things, an informal review method
Pair programming is used usually in water fall model
I, III, IV and V are true. II is false
II, III, IV and V are correct. I is false
I, II and IV are true. III and V are false
II, III and V are true. I and IV are false
Security tools check for viruses and denial of service attacks
Static analysis tools support developers and testers in finding defects before dynamic testing
Test execution tools generate test inputs or executable tests e.g. from requirements
Monitoring tools provide information that can be used for testing purposes
Analysis of linked web pages
Calculation of complexity of the code
Quantitative analysis related to the tests (e.g tests passed)
Enforcement of coding standards
Boundary value analysis
Use case based testing
Equivalence class partitioning
Decision table
50, 100, 250, 1000
50, 100, 200, 1000
0, 50, 100, 150, 200, 350, 500
0, 1, 99, 100, 200, 201, 499, 500
I, II, III
III, IV
I, II
II, III, IV
Test derived from the ability of the testers and their intuition and experience with similar applications and technologies (sometimes used to strengthen systematic techniques)
Test on an individual software component in isolation from other components, to avoid external influence
Test of the interfaces between components and of the interactions with different parts of a system
Tests that investigate the input vs. the output behavior of a software system
They store version information and can be replaced by configuration management tools
They make it possible to observe possible performance problems and give warnings
They supervise the testing effort and report related metrics
They are technical tools a used by developers and not testers
Test implementation and execution
Test closure activates
Evaluating exit criteria and reporting
Test planning and control
2 test case for statement coverage; 2 test case for branch coverage
1 test case for statement coverage; 1 test case for branch coverage
1 test case for statement coverage; 2 test case for branch coverage
1 test case for statement coverage; 3 test case for branch coverage
Monitoring system resources
The amount of testers needed in order to achieve "dead line"
Time response and system breaking point
Correct behavior of the system under test
Perform bug isolation to find the conditions that cause the crash
Report the incident as is without any further action
Try to identify the code fragment causing the problem
Do a root cause analysis
Provides test leaders with information to report test progress
Provides ideas for test process improvement
Provides developers with information to isolate the failure
Does not belong in an incident report
The author documents the problems and open points
The manager allocates time in project schedules
The manager is responsible for planning the review
The moderator determines if the review objectives have been met
All combinations of valid equivalence classes could be covered with 4 test cases
There are two invalid equivalence classes for the age input parameter
The total number of combinations of valid equivalence classes of age and gender is 8
All valid equivalence classes could be covered with 6 test cases
I and II
I, II and III
I, II and IV
I and IV
It may include testing the ease of modification of systems
It tests "how" the system works
It covers the evaluation of the interaction of various specified components
It may be performed at unit, integration, system and acceptance test levels
Covering only start and end states
Covering all transitions at least once
Can't be determined
Covering all states at least once
It identifies defects in the functionality of modules, objects and classes
It may be applied using a test-first approach.
It mainly tests interfaces and interactions between components
Simulators and stubs may be required
I, II
I, IV
II, III
IV
Multiple condition coverage
Decision table
Use case testing
Statement coverage
At least 2 test cases are needed to achieve 100% statement coverage of program Y
At least 2 test cases are needed to achieve 100% decision coverage of program X
At least 2 test cases are needed to achieve 100% statement coverage of program X
At least 2 test cases are needed to achieve 100% decision coverage of program Y
To control contractual problems and minimize the impacts of company policies
To increase the success probability for the project regardless of costs
To increase focus on preventative processes and to increase satisfaction for the testers
To reduce the probability of undesired situations and to reduce the effect of potential impact
17, 18, 75, 76
0, 18, 75, 99
0, 17, 18, 75, 76, 99
17, 18, 19, 50,75, 76
II, III
II, IV
I, III
I, IV
Independent testing may be performed at any level of testing
Independent testing is often more effective at finding defects and failures
Independent testing is not appropriate for unit testing
Independent testing can be performed by developers with the right mindset
Checking memory leaks for a program by executing it
Testing for performance
Coverage analysis
Code inspection
To set up the test environment
To coordinate the test strategy with project managers
To prepare and acquire test data
To automate tests
Requirements specification
Implementation and execution
Analysis and design
Evaluating exit criteria and reporting
II, III, IV
II, III, V
I, III, IV, V
I, II, V
Use case testing
Man machine interface testing
Decision table testing
State Transition Testing
The testing of software demonstrates the absence of defects
Performing a review of the requirement specifications before implementing the system can enhance quality
Properly designed tests that pass reduce the level of risk in a system
Software testing identifies defects, which can be used to improve development activities
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.