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. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






3. Linear Code Sequence and Jump.






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






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






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






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






8. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






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






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






13. Response of the application to an input






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






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






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






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






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






19. Record details of test cases executed Record order of execution record results






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






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






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






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






24. Testing software components that are separately testable. Also module program and unit testing.






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






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






27. The process of finding analyzing and removing causes of failure in a software product.






28. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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