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. Allows storage of test input and expected results in one or more central data sources or databases.






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






3. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






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






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






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






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






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






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






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






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






13. Sequence in which data items are accessed or modified by code.






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






15. One defect prevents the detection of another.






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






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






18. Find defects in code while the software application being tested is running.






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






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






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






22. Components are combined and tested in the order in which basic functionalities start working






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






24. Testing an integrated system to validate it meets requirements






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






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






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






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






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






30. Testing software in its operational environment






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






32. Requirements that determine the functionality of a software system.






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






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






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






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






37. Input or combination of inputs required to test software.






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






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






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






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






42. Conditions required to begin testing activities.






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






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






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






46. A review not based on a formal documented procedure






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






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






49. Response of the application to an input






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