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






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






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






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






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






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






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






8. Response of the application to an input






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






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






11. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






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






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






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






24. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






25. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






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






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






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






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






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






33. Testing software in its operational environment






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






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






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






37. Conditions required to begin testing activities.






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






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






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






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






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






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






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






45. Component - Integration - System - Acceptance






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






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






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






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






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