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






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






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






4. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






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






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






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






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






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






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






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






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






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






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






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






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






17. Calculates the number of executed branch outcomes in code.






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






19. Insertion of additional code in the existing program in order to count coverage items.






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






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






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






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






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






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






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






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






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






29. Response of the application to an input






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






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






32. Occurrences that happen before and after an unexpected event






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






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






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






36. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






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






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






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






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






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