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. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






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






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






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






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






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






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






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






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






12. Linear Code Sequence and Jump.






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






14. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






16. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






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






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






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






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






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






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






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






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






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






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






27. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






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






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






32. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






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






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






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






37. Testing software in its operational environment






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






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






40. Used to replace a component that calls another component.






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






42. Find defects in code while the software application being tested is running.






43. Component - Integration - System - Acceptance






44. Severity - Priority






45. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






49. A document that provides the structure for writing test cases.






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






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