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. An analysis that determines the portion of code on software executed by a set of test cases






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






3. Black-box test design technique - test cases are designed from a decision table.






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






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






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






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






8. Events that occurred during the testing process our investigation.






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






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






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






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






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






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






15. Severity - Priority






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






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






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






19. Component - Integration - System - Acceptance






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






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






22. Waterfall iterative-incremental "V"






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






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






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






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






27. Conditions required to begin testing activities.






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






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






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






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






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






33. Testing an integrated system to validate it meets requirements






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






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






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






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






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






39. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






48. Actual inputs required to execute a test case






49. Tools used to identify and calculate coverage items in program code.






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