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. Software products or applications designed to automate manual testing tasks.






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






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






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






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






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






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






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






9. Events that occurred during the testing process our investigation.






10. Conditions required to begin testing activities.






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






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






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






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






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






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






17. Human action that generates an incorrect result.






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






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






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






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






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






23. Occurrences that happen before and after an unexpected event






24. Components are integrated in the order in which they are developed






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






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






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






28. Waterfall iterative-incremental "V"






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






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






31. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






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






42. One defect prevents the detection of another.






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






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






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






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






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






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






49. Process used to create a SW product from initial conception to public release






50. Testing an integrated system to validate it meets requirements