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. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






2. Testing an integrated system to validate it meets requirements






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






4. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






11. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






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






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. Response of the application to an input






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






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






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






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






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. Input or combination of inputs required to test software.






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






31. Component - Integration - System - Acceptance






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






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. Testing software components that are separately testable. Also module program and unit testing.






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






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






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






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






39. Waterfall iterative-incremental "V"






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






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






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






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






44. Actual inputs required to execute a test case






45. One defect prevents the detection of another.






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






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






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






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






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