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. The set from which valid output values can be selected. See also domain. The set from which valid input and/or output values can be selected.






2. An element of storage in a computer that is accessible by a software program by referring to it by a name.






3. Testing of software used to convert data from existing systems for use in replacement systems.






4. The capability of the software product to enable the user to learn its application. [ISO 9126] See also usability. The capability of the software to be understood - learned - used and attractive to the user when used under specified conditions. [ISO






5. Any (work) product that must be delivered to someone other than the (work) product's author.






6. The process of testing to determine the interoperability of a software product. See also functionality testing. The process of testing to determine the functionality of a software product.






7. Software developed specifically for a set of users or customers. The opposite is off-the-shelf software.






8. A skeletal or special-purpose implementation of a software component - used to develop or test a component that calls or is otherwise dependent on it. It replaces a called component. [After IEEE 610]






9. A transition between two states of a component or system.






10. The behavior produced/observed when a component or system is tested.






11. A sequence of events (paths) in the execution through a component or system.






12. Separation of responsibilities - which encourages the accomplishment of objective testing. [After DO-178b]






13. Deviation of the component or system from its expected delivery - service or result. [After Fenton]






14. A white box test design technique in which test cases are designed to execute combinations of single condition outcomes (within one statement).






15. Testing aimed at ensuring that the component or system can operate in conjunction with new or existing users' business procedures or operational procedures.






16. An item or event of a component or system that could be verified by one or more test cases - e.g. a function - transaction - feature - quality attribute - or structural element.






17. The first executable statement within a component.






18. The ratio of the number of failures of a given category to a given unit of measure - e.g. failures per unit of time - failures per number of transactions - failures per number of computer runs. [IEEE 610]






19. The fundamental test process comprises test planning and control - test analysis and design - test implementation and execution - evaluating exit criteria and reporting - and test closure activities.






20. A tool that provides objective measures of what structural elements - e.g. statements - branches have been exercised by a test suite.






21. A risk directly related to the test object. See also risk. A factor that could result in future negative consequences; usually expressed as impact and likelihood.






22. A test basis document that can only be amended by a formal change control process. See also baseline. A specification or software product that has been formally reviewed or agreed upon - that thereafter serves as the basis for further development - a






23. A program element is said to be exercised by a test case when the input value causes the execution of that element - such as a statement - decision - or other structural element.






24. Environmental and state conditions that must be fulfilled after the execution of a test or test procedure.






25. A tool used to check that no brtoken hyperlinks are present on a web site.






26. A black box test design technique in which test cases are designed to execute all possbile discrete combinations of each pair of input parameters. See also orthogonal array testing. A systematic way of testing all-pair combinations of variables using






27. A pointer within a web page that leads to other web pages.






28. Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system.






29. A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 transitions. [Chow] See also state transition testing. A black box test design technique in which test cases are designed to execute valid and i






30. The process of recognizing - investigating - taking action and disposing of incidents. It involves logging incidents - classifying them and identifying the impact. [After IEEE 1044]






31. A type of peer review that relies on visual examination of documents to detect defects - e.g. violations of development standards and non-conformance to higher level documentation. The most formal review technique and therefore always based on a docu






32. A review not based on a formal (documented) procedure.






33. A grid showing the resulting transitions for each state combined with each possible event - showing both valid and invalid transitions.






34. The behavior predicted by the specification - or another source - of the component or system under specified conditions.






35. Comparison of actual and expected results - performed after the software has finished running.






36. The process through which decisions are reached and protective measures are implemented for reducing risks to - or maintaining risks within - specified levels.






37. A graphical representation of inputs and/or stimuli (causes) with their associated outputs (effects) - which can be used to design test cases.






38. A collection of components organized to accomplish a specific function or set of functions. [IEEE 610]






39. The result of a decision (which therefore determines the branches to be taken).






40. A list of activities - tasks or events of the test process - identifying their intended start and finish dates and/or times - and interdependencies.






41. An entity or property used as a basis for test coverage - e.g. equivalence partitions or code statements.






42. A source of a defect such that if it is removed - the occurance of the defect type is decreased or removed. [CMMI]






43. The assessment of change to the layers of development documentation - test documentation and components - in order to implement a given change to specified requirements.






44. Testing to determine how the occurrence of two or more activities within the same interval of time - achieved either by interleaving the activities or by simultaneous execution - is handled by the component or system. [After IEEE 610]






45. The process of demonstrating the ability to fulfill specified requirements. Note the term 'qualified' is used to designate the corresponding status. [ISO 9000]






46. A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation - correction and re-testing of defects and provide reporting facilities. See also incid






47. A software tool used to carry out instrumentation.






48. Procedure used to derive and/or select test cases.






49. Acceptance testing by users/customers at their site - to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes - normally including hardware as well as software.






50. The set of generic and specific conditions for permitting a process to go forward with a defined task - e.g. test phase. The purpose of entry criteria is to prevent a task from starting which would entail more (wasted) effort compared to the effort n







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