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. Integration approach components or subsystems are combined all at once rather than in stages.






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






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






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






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






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






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






8. Waterfall iterative-incremental "V"






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






10. One defect prevents the detection of another.






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






12. Tools used to identify and calculate coverage items in program code.






13. A functional testing approach in which test cases are designed based on business processes.






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






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






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






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






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






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






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






21. Human action that generates an incorrect result.






22. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






23. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






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






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






26. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






28. Severity - Priority






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






30. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






31. Component - Integration - System - Acceptance






32. Actual inputs required to execute a test case






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






34. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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







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