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






2. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






10. Occurrences that happen before and after an unexpected event






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






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






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






14. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






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






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






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






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






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






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






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






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






23. Tests interfaces between components and between integrated components and systems.






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






25. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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






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






31. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






47. Testing software in its operational environment






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






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






50. Input or combination of inputs required to test software.