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. 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. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






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






5. Operational testing performed at an _external_ site without involvement of the developing organization.






6. Testing an integrated system to validate it meets requirements






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






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






9. Find defects in code while the software application being tested is running.






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






11. Sequence in which data items are accessed or modified by code.






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






13. Human action that generates an incorrect result.






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






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






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






17. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






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






35. Tools used by developers to identify defects in programs.






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






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






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






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






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






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






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






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






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






45. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






48. Occurrences that happen before and after an unexpected event






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






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







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