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. Develop & proiroitize test cases Create groups of test cases Set up test environment






2. Calculates the number of executed branch outcomes in code.






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






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






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






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






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






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






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






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






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






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






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






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






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






16. A table showing combinations of inputs and their associated actions.






17. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






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






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






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






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






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






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






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






26. Response of the application to an input






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






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






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






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






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






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






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






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






35. Conditions required to begin testing activities.






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






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






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






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






40. Testing an integrated system to validate it meets requirements






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






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






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






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






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






46. One defect prevents the detection of another.






47. Occurrences that happen before and after an unexpected event






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






49. Waterfall iterative-incremental "V"






50. Human action that generates an incorrect result.