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. Increased load (transations) used to test behavior of system under high volume.






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






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






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






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






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






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






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






9. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






20. A review not based on a formal documented procedure






21. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






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






24. One defect prevents the detection of another.






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






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






27. An analysis that determines the portion of code on software executed by a set of test cases






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






29. Insertion of additional code in the existing program in order to count coverage items.






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






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






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






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






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






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






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






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






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






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






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






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






42. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






43. Waterfall iterative-incremental "V"






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






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






46. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






47. Component - Integration - System - Acceptance






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






49. Testing an integrated system to validate it meets requirements






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