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. Waterfall iterative-incremental "V"






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






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






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






5. Linear Code Sequence and Jump.






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






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






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






9. Conditions required to begin testing activities.






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






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






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. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






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






24. Input or combination of inputs required to test software.






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






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






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






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






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






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






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






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






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






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






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






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






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






38. A review not based on a formal documented procedure






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






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






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






42. Testing an integrated system to validate it meets requirements






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






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






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






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






47. Occurrences that happen before and after an unexpected event






48. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






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