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. Used to test the functionality of software as mentioned in software requirement specifications.






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






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






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






5. Linear Code Sequence and Jump.






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 to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






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






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






11. White-box design technique used to design test cases for a software component using LCSAJ.






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






13. Allows storage of test input and expected results in one or more central data sources or databases.






14. Severity - Priority






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






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






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






18. Response of the application to an input






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






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






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






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






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






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






25. A review not based on a formal documented procedure






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






27. Testing software in its operational environment






28. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






31. Component - Integration - System - Acceptance






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






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






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. Increased load (transations) used to test behavior of system under high volume.






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






37. Waterfall iterative-incremental "V"






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






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






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






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






42. One defect prevents the detection of another.






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






44. Conditions required to begin testing activities.






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






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






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






48. Integrate different kinds of tools to make test management more efficient and simple.






49. A unique identifier for each incident report generated during test execution.






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






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests