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. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






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






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






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






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






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






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






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. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






12. Occurrences that happen before and after an unexpected event






13. One defect prevents the detection of another.






14. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






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






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






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






19. Linear Code Sequence and Jump.






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






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






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






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






24. Measures amount of testing performed by a collection of test cases






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






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






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






28. A functional testing approach in which test cases are designed based on business processes.






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






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






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






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






33. Conditions required to begin testing activities.






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






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






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






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






38. Black-box test design technique - test cases are designed from a decision table.






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






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






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






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






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






44. A component of the incident report that determines the actual effect of the incident on the software and its users.






45. The smallest software item that can be tested in isolation.






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






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






48. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






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