I and ii.
I, ii and iii
Iii.
Ii and iv
Log defects.
Explain the documents to the participants.
Gather metrics.
Allocate the individual roles.
Shows the number of newly discovered defects per unit time
Shows the number of open defects per unit time.
Shows the cumulative total number of defects found up to this time.
Any of these, depending on the company.
You have discovered every bug in the program.
You have tested every statement, branch, and combination of branches in the program.
You have completed every test in the test plan.
You have reached the scheduled ship date.
That you have tested every statement in the program.
That you have tested every statement and every branch in the program.
That you have tested every IF statement in the program.
That you have tested every combination of values of IF statements in the program
Testers spend more energy early in the product trying to find bugs than preparing to do the rest of the project's work more efficiently
Managers might not realize that the testing effort is ineffective, late in the project, because they expect a low rate of bug finding, so the low rate achieved doesn't alarm them.
It can increase the end-of-project pressure on testers to not find bugs, or to not report bugs.
All of the above
Deviations from standards,
Requirement defects,
Design defects,
Insufficient maintainability and incorrect interface specifications.
All of the above.
Identifying defects.
Fixing defects.
A. and B
None of the above
The failure occurs only if you reach a statement taking the TRUE branch of an IF statement, and you got to the statement with a test that passed through the FALSE branch.
The failure depends on the program's inability to handle specific data values, rather than on the program's flow of control.
We are not required to test code that customers are unlikely to execute.
All of the above
Even though the numbers you look at appear better, to achieve these numbers, people are doing other aspects of their work much less well.
We don't know how to measure a variable (our measurement is dysfunctional) and so we don't know how to interpret the result.
You are measuring the wrong thing and thus reaching the wrong conclusions.
All of the above.
We can never be certain that the program is bug free.
We have no definite stopping point for testing, which makes it easier for some managers to argue for very little testing.
We have no easy answer for what testing tasks should always be required, because every task takes time that could be spent on other high importance tasks.
All of the above.
Only Project risks
Only Product risks
Project risks and Product risks
Project risks or Product risks
Non-functional requirements only not Functional requirements
Functional requirements only not non-functional requirements
Non-functional requirements and Functional requirements
Non-functional requirements or Functional requirements
System testing
Acceptance testing
Integration testing
Smoke testing
Planning, Review meeting, Rework, Kick off
Planning, Individual preparation, Kick off, Rework
Planning, Review meeting, Rework, Follow up
Planning, Individual preparation, Follow up, Kick off
Finding defects
Gaining confidence about the level of quality and providing information
Preventing defects.
Debugging defects
External failure
Internal failure
Appraisal
Prevention
Supplier issues
Organization factors
Technical issues
Error-prone software delivered
Open, Assigned, Fixed, Closed
Open, Fixed, Assigned, Closed
Assigned, Open, Closed, Fixed
Assigned, Open, Fixed, Closed
Moderator
Scribe
Reviewers
Author
0,1,2,99
1, 99, 100, 98
0, 1, 99, 100
–1, 0, 1, 99
Early testing
Defect clustering
Pesticide paradox
Exhaustive testing
Eliminate some of the requirements that have not yet been implemented.
Add more engineers to the project to make up for lost work.
Ask the current developers to work overtime until the lost work is recovered.
Hire more software quality assurance personnel.
Alpha testing
Field testing
Performance testing
System testing
ISO 1926
ISO 829
ISO 1012
ISO 1028
Equivalence partition
Decision tables
Transaction diagrams
Decision testing
Test data preparation tools – Manipulate Data bases
Test design tools – Generate test inputs
Requirement management tools – Enables individual tests to be traceable
Configuration management tools – Check for consistence
Performance testing
Unit testing
Business scenarios
Static testing
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
Confront the person and ask that other team members be allowed to express their opinions.
Wait for the person to pause, acknowledge the person’ s opinion, and ask for someone else’ s opinion.
Switch the topic to an issue about which the person does not have a strong opinion.
Express an opinion that differs from the person’ s opinion in order to encourage others to express their ideas.
Heuristic testing approach
Methodical testing approach
Model based testing approach
Process or standard compliant testing approach
Process flow model
State transaction model
Menu structure model
Plain language specification model
Branch testing
Agile testing
Beta testing
Ad-hoc testing
Define when to stop testing
End of test level
When a set of tests has achieved a specific pre condition
All of the above
Boundary value analysis
Equivalence partitioning
Decision table testing
State transition testing
Unit testing
Regression testing
Alpha testing
Integration testing
Inexpensive way to get some benefit
Find defects
Learning, gaining understanding, effect finding
Discuss, make decisions, solve technical problems
Check the memory leaks
Check the robustness
Check the branch coverage
Check the decision tables
To identify, evaluate, and rank tools, and recommend tools to management
To determine what kind of tool is needed, then find it and buy it
To initiate the tool search and present a case to management
To identify, evaluate and select the tools
Planning and control
Test closure activities
Analysis and design
None
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.