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. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






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






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






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






7. Response of the application to an input






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






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






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






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






12. Waterfall iterative-incremental "V"






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






14. Testing an integrated system to validate it meets requirements






15. Informal testing technique in which test planning and execution run in parallel






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






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






18. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






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






20. Occurrences that happen before and after an unexpected event






21. Actual inputs required to execute a test case






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






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






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






25. A technique used to improve testing coverage by deliberately introducing faults in code.






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






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






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






29. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






42. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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