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. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






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






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






5. Occurrences that happen before and after an unexpected event






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






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






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






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






10. Testing software in its operational environment






11. Allows storage of test input and expected results in one or more central data sources or databases.






12. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






13. 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).






14. Conditions required to begin testing activities.






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






16. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






17. Based on analysis of functional specifications of a system.






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






19. A review not based on a formal documented procedure






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






21. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






23. A table showing combinations of inputs and their associated actions.






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






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






26. Human action that generates an incorrect result.






27. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






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






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






30. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






31. Process used to create a SW product from initial conception to public release






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






33. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






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






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






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






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






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






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






41. Waterfall iterative-incremental "V"






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






43. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






47. One defect prevents the detection of another.






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






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






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