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 code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






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






4. Tools used to identify and calculate coverage items in program code.






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






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






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






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






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






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






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






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






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






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






15. Severity - Priority






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






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






18. Waterfall iterative-incremental "V"






19. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






20. Linear Code Sequence and Jump.






21. Actual inputs required to execute a test case






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






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






24. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






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






35. The process of finding analyzing and removing causes of failure in a software product.






36. Tools used by developers to identify defects in programs.






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






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






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






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. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






42. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






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






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






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






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






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






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






49. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






50. Separation of testing responsibilities which encourages the accomplishment of objective testing