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. Special-purpose software used to simulate a component called by the component under test






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






3. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






21. Testing software in its operational environment






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






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






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






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






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






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






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






29. Severity - Priority






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






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. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






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






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






36. Input or combination of inputs required to test software.






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






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






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






40. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






41. Combining components or sytems into larger structural units or subsystems.






42. Occurrences that happen before and after an unexpected event






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






44. Response of the application to an input






45. Waterfall iterative-incremental "V"






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






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






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






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






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