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. Record details of test cases executed Record order of execution record results






2. Actual inputs required to execute a test case






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






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






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






6. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






9. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






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






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






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






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






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






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






16. A review not based on a formal documented procedure






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






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






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






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






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






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






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






24. Human action that generates an incorrect result.






25. Severity - Priority






26. Separation of testing responsibilities which encourages the accomplishment of objective testing






27. Waterfall iterative-incremental "V"






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






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






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






31. Special additions or changes to the environment required to run a test case.






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






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






34. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






35. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






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






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






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






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






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






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






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






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






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






46. Component - Integration - System - Acceptance






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






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






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






50. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.







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