Qa study week 3
What are the characteristics of an effective defect report?
All of the above
The software defect report content consists of six main components. Which of the following is not one of those components?
Associated defect reports
Testing and verification notes belong to which of the following categories?
Close
It is normal to accept requirements with a 'to-be-determined' in them.
Correct: requirements with TBDs can't really be tested because we do not know how the system is expected to respond.
Which of the following is the kind of test that determines whether or not you built the correct thing for the customer?
Customer Acceptance Test
Which of the following components would contain an overview of the problem along with what you did and the results of that action?
Description of the problem
Testing modules to ensure they work together properly occurs at which stage of software testing process?
Design Verification Testing
Assume that a particular low-severity defect is such that by fixing it, it will cause many more problems to come up. What final state should this defect be given?
Do not fix
Which of the following is NOT an important component of a test plan according to the Quality Assurance Institute?
Entry and Exit Conditions
Reproducibility and repeatability are the same thing when it comes to defects.
False
Severity and priority are essentially the same in terms of status indication.
False
The best defect reports have new and ingenious introductions of terminology and abbreviations.
False
The only test report is the final report and is sent only when all testing is complete.
False
The unit testing plan that is generated is always a formal document.
False, The unit testing plan is often not a formal document. It is a plan put in place by the developer while working on the project.
System validation testing is when the system is tested for error prone constructs and low level functionality assurances.
FalseYou are correct; system validation testing is when the system is tested for high level behavior and nonfunctional performance. Unit testing is when the system is tested (usually by the developer) for error prone constructs and low level functionality.
Lets say you are working on an unmanned aerial vehicle and a defect is found. This defect happens only occasionally, but if it does the vehicle would come crashing out of the sky onto an unsuspecting population killing many. What severity level should this defect be given?
High
Which of the following components would contain a defect identification number?
Identification Information
The stages in software defect life cycles include all of the following except for one. Choose the incorrect stage in the list below:
Ignore the bug
Testing is _______ but not _________ from development.
Independent; Isolated
Which of the following is not true about a traceability (requirements) matrix.
It will list any missing requirements
The report phase consists of four main steps. Which of the following is not one of those steps?
Let developers decide whether to report defect
Assume that there is a defect that is found to be a problem, but you can essentially ignore it. Which severity level should it have?
Low
Which of these should NOT be included in unit testing?
Module integration testing
When considering risk, it is important to consider categories of impact. Which of the following is NOT given as an example in the lecture slides.
Motivation
Which of the following is not a conclusion reached by the retesting phase?
Problem is insurmountable
The amount of loss management is willing to accept is known as:
Risk appetite
Asking the question: What can you do to control (reduce) the risk? is an example of:
Risk mitigation
The act of reducing risk is known as:
Risk mitigation
System validation testing will test the system for quality of behavior delivery on many aspects. Which of the following is not one of those aspects?
Scalability
In terms of risk impact, depth of impact refers to:
Severity of damage
Assume that you are writing a defect report and this particular defect is known to have an impact of medium severity. Which component would contain this information?
Status Indicator
Part of analysis is figuring out where the fault of the defect lies. The fault could lie with the:
Test Tester Product
Which of the following is NOT part of the test (status) report.
Test case code
There is always pressure on ______ to prove a product is not ready for release (especially in the Waterfall Method).
Testers
Test (status) reports are important because:
That is correct. There are many reasons for doing test status reports.
Which of the following traces test cases back to requirements?
Traceability Report
If there is a relatively easy workaround to a problem, STATE IT in the defect report.
True
Not all defects are created equal.
True
Only about half of testing efforts are spent on actual testing.
True
System validation testing occurs once the full system is complete.
True
Unit testing is usually white box testing done by the developer on a small piece of code (a function or class).
True
When it comes to tracking defects, the most important aspect is to have a process and follow it.
True
You should always include the minimum number of steps to reproduce the defect in a defect report.
True
When considering concerns or risks of test planning, it's important to take preventative action when possible.
True, Yes: if you know there are deficiencies in the test plan, they should be addressed. For example, if requirements are incomplete or there is not management support for test, it is better to fix these issues early rather than late.
When risk avoidance fails, the best thing to do is to test features with the highest impact and the features that are most likely to fail.
True, Yes; avoid risks whenever possible, but this will not always be possible. When all else fails, risks will help prioritize.
Testing is the only way to locate bugs in a system.
Yes, there are many other ways including proof.
Design Verification Testing has two aspects: Integration testing and Functional testing.
Yes: integration testing checks whether the modules work together, and functional testing checks whether they do something useful.
The risk equation is:
risk = impact * likelihood