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 set of conditions that a system needs to meet in order to be accepted by end users






2. A review not based on a formal documented procedure






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






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






5. The capability of a software product to provide agreed and correct output with the required degree of precision






6. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






10. Testing an integrated system to validate it meets requirements






11. Increased load (transations) used to test behavior of system under high volume.






12. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






13. A component of the incident report that determines the actual effect of the incident on the software and its users.






14. A functional testing approach in which test cases are designed based on business processes.






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






16. A document that provides the structure for writing test cases.






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






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






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






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






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






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






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






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






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






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






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






28. Operational testing performed at an _external_ site without involvement of the developing organization.






29. Sequence in which instructions are executed through a component or system






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






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






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






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






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






35. Ability of software to provide appropriate performance relative to amount of resources used.






36. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






39. Human action that generates an incorrect result.






40. Tools used to store and manage incidents return phone defects failures or anomalies.






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






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






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






44. Record details of test cases executed Record order of execution record results






45. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






46. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






49. Occurrences that happen before and after an unexpected event






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