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






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






3. Conditions required to begin testing activities.






4. Informal testing technique in which test planning and execution run in parallel






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






35. One defect prevents the detection of another.






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






37. Severity - Priority






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






39. Components are integrated in the order in which they are developed






40. Linear Code Sequence and Jump.






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






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






43. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






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






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






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






47. Response of the application to an input






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






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






50. Actual inputs required to execute a test case







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