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. Software products or applications designed to automate manual testing tasks.






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






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






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






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






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






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






8. Human action that generates an incorrect result.






9. Deviation of a software system from its expected delivery services or results






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






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






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






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






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






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






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






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






18. Actual inputs required to execute a test case






19. Severity - Priority






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. 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. Calculates the number of executed branch outcomes in code.






23. Testing software in its operational environment






24. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






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






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






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






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






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






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






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






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






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






36. Occurrences that happen before and after an unexpected event






37. Linear Code Sequence and Jump.






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






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






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






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






42. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






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






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






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






48. Measures amount of testing performed by a collection of test cases






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






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