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. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






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






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






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






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






9. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






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






15. Human action that generates an incorrect result.






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






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






18. Response of the application to an input






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






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






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






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






23. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






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






27. Conditions required to begin testing activities.






28. Severity - Priority






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






30. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






40. Allows storage of test input and expected results in one or more central data sources or databases.






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






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






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






44. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






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






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






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






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