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. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






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






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






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






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






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






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






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






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






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






11. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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






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






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






22. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






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






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






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






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






28. A task of maintaining and controlling changes to all entities of a system.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






49. A review not based on a formal documented procedure






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