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






2. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






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






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






9. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






17. The process of finding analyzing and removing causes of failure in a software product.






18. Waterfall iterative-incremental "V"






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






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






21. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






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






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






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






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






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






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






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






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






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






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






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






34. Examine changes made to an operational system cause defects.






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






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






37. Conditions required to begin testing activities.






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






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






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






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






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






43. Component - Integration - System - Acceptance






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






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






46. Severity - Priority






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






48. Human action that generates an incorrect result.






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






50. Testing an integrated system to validate it meets requirements