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. Ability of software to provide appropriate performance relative to amount of resources used.






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






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






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






5. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






6. Response of the application to an input






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






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






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






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






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






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






13. Component - Integration - System - Acceptance






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






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






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






17. Conditions required to begin testing activities.






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






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






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






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






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






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






24. Actual inputs required to execute a test case






25. Severity - Priority






26. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






27. Separation of testing responsibilities which encourages the accomplishment of objective testing






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






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






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






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






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






33. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






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






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






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






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






48. Increased load (transations) used to test behavior of system under high volume.






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






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