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. Find defects in code while the software application being tested is running.






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






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






4. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






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






8. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






9. Testing software in its operational environment






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






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






12. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






13. Severity - Priority






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. The smallest software item that can be tested in isolation.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






46. Human action that generates an incorrect result.






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






48. Linear Code Sequence and Jump.






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






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