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. Informal testing technique in which test planning and execution run in parallel






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






3. Testing performed to determine whether the system meets acceptance criteria






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






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






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






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






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






9. Linear Code Sequence and Jump.






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






11. Component - Integration - System - Acceptance






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






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






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






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






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






17. Human action that generates an incorrect result.






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






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






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






21. Testing software in its operational environment






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






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






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






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






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






27. Allows storage of test input and expected results in one or more central data sources or databases.






28. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






47. A review not based on a formal documented procedure






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






49. Occurrences that happen before and after an unexpected event






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests