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. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






2. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






4. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






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






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






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






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






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






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






12. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






16. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






18. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






22. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






38. Component - Integration - System - Acceptance






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






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






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






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






43. Severity - Priority






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






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






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






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






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






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






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






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