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 functional testing approach in which test cases are designed based on business processes.






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






3. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






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






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






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






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






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






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






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






12. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






13. Waterfall iterative-incremental "V"






14. Response of the application to an input






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






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






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






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






19. Conditions required to begin testing activities.






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






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






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






23. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






31. Human action that generates an incorrect result.






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






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






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






35. Component - Integration - System - Acceptance






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






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






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






39. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






47. Linear Code Sequence and Jump.






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






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






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