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. Components are combined and tested in the order in which basic functionalities start working






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






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






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






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






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






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






8. Actual inputs required to execute a test case






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. Component - Integration - System - Acceptance






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






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






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






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






15. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






32. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






42. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






47. Linear Code Sequence and Jump.






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






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






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