Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Develop & proiroitize test cases Create groups of test cases Set up test environment






2. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






3. Severity - Priority






4. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






5. Events that occurred during the testing process our investigation.






6. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






7. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






8. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






9. A task of maintaining and controlling changes to all entities of a system.






10. Components are integrated in the order in which they are developed






11. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






12. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






13. An analysis that determines the portion of code on software executed by a set of test cases






14. Used to replace a component that calls another component.






15. Black-box testing technique used to create groups of input conditions that create the same kind of output.






16. Special-purpose software used to simulate a component called by the component under test






17. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






18. One defect prevents the detection of another.






19. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






20. Testing software components that are separately testable. Also module program and unit testing.






21. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






22. Incident Report - Identifier - Summary - Incident - Description - Impact






23. A document that records the description of each event that occurs during the testing process and that requires further investigation






24. White-box design technique used to design test cases for a software component using LCSAJ.






25. Special-purpose software used to simulate a component that calls the component under test






26. All possible combinations of input values and preconditions are tested.






27. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






28. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






29. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






30. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






31. The ratio between the number of defects found and the size of the component/system tested.






32. Response of the application to an input






33. A set of conditions that a system needs to meet in order to be accepted by end users






34. Black-box test design technique - test cases are designed from a decision table.






35. Specific groups that represent a set of valid or invalid partitions for input conditions.






36. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






37. Deviation of a software system from its expected delivery services or results






38. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






39. A technique used to improve testing coverage by deliberately introducing faults in code.






40. Testing performed to determine whether the system meets acceptance criteria






41. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






42. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






43. Software products or applications designed to automate manual testing tasks.






44. Used to test the functionality of software as mentioned in software requirement specifications.






45. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






46. The smallest software item that can be tested in isolation.






47. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






48. Examine changes made to an operational system cause defects.






49. Behavior or response of a software application that you observe when you execute the action steps in the test case.






50. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations