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. A component of the incident report that determines the actual effect of the incident on the software and its users.






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






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






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






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






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






7. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






9. Component - Integration - System - Acceptance






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






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






12. Special-purpose software used to simulate a component called by the component under test






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






14. Response of the application to an input






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






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






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






18. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






19. Tests interfaces between components and between integrated components and systems.






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






21. One defect prevents the detection of another.






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






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






24. Waterfall iterative-incremental "V"






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






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






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






28. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






43. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






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






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






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






47. Testing an integrated system to validate it meets requirements






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests