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. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






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






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






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






8. A set of conditions that a system needs to meet in order to be accepted by end users






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






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






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






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






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






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






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






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






17. Human action that generates an incorrect result.






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






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






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






21. Examine changes made to an operational system cause defects.






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






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






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






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






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






27. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






38. One defect prevents the detection of another.






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






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






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






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






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






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






45. Linear Code Sequence and Jump.






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






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






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






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






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







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