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. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






2. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






5. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






7. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






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






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






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






13. One defect prevents the detection of another.






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






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






16. Sequence in which data items are accessed or modified by code.






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






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






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






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






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






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






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






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






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






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






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






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






29. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






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






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






32. Tools used to store and manage incidents return phone defects failures or anomalies.






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






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






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






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






37. Waterfall iterative-incremental "V"






38. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






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






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






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






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






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






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