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. A document that provides the structure for writing test cases.






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






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






4. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






5. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






6. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






8. 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






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






10. One defect prevents the detection of another.






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






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






13. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






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






15. A review not based on a formal documented procedure






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






17. Informal testing technique in which test planning and execution run in parallel






18. Severity - Priority






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






20. Combining components or sytems into larger structural units or subsystems.






21. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






24. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






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






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






28. An event or item that can be tested using one or more test cases






29. Tests interfaces between components and between integrated components and systems.






30. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






31. Special additions or changes to the environment required to run a test case.






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






33. Component - Integration - System - Acceptance






34. Response of the application to an input






35. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






37. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






38. Integration approach components or subsystems are combined all at once rather than in stages.






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






40. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






41. Integrate different kinds of tools to make test management more efficient and simple.






42. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






43. A unique identifier for each incident report generated during test execution.






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






45. Testing software in its operational environment






46. 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






47. Actual inputs required to execute a test case






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






49. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






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