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. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






4. A review not based on a formal documented procedure






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






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






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






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






9. Testing an integrated system to validate it meets requirements






10. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






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






21. Linear Code Sequence and Jump.






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






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






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






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






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






27. Human action that generates an incorrect result.






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






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






30. Increased load (transations) used to test behavior of system under high volume.






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






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






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






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






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






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






37. Special-purpose software used to simulate a component that calls the component under test






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






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






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






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






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






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






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






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






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






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






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






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






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







Sorry!:) No result found.

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