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: A frame or backbone is created and components are progressively integrated into it.






2. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






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






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






7. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






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






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






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






13. A component of the incident report that determines the actual effect of the incident on the software and its users.






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






15. Testing software in its operational environment






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






17. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






28. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






30. Special additions or changes to the environment required to run a test case.






31. A review not based on a formal documented procedure






32. Occurrences that happen before and after an unexpected event






33. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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






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






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






44. Human action that generates an incorrect result.






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






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






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






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






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






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







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