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 testing activities that must be repeated when testing is re-started after a suspension. [After IEEE 829]






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






3. A form of static analysis based on the definition and usage of variables.






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






5. A minimal software item that can be tested in isolation.






6. Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers - to determine whether or not a component or system satisfies the user/customer needs and fits within the business process






7. The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate. [After IEEE 610] See also efficiency. The capability of the software product to provide appropriat






8. A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.






9. The capability of the software product to avoid unexpected effects from modifications in the software. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects - modified to meet new requirements






10. A type of test tool that is able to execute other software using an automated test script - e.g. capture/playback. [Fewster and Graham]






11. A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made - and to design tests specifically to expose them.






12. Simulated or actual operational testing by potential users/customers or an independent test team at the developers' site - but outside the development organization. Alpha testing is often employed for off-the-shelf software as a form of internal acce






13. The period of time in a software development life cycle during which the components of a software product are executed - and the software product is evaluated to determine whether or not requirements have been satisfied. [IEEE 610]






14. A test approach in which the test suite comprises all combinations of input values and preconditions.






15. A test plan that typically addresses one test level. See also test plan. A document describing the scope - approach - resources and schedule of intended test activities. It identifies amongst others test items - the features to be tested - the testin






16. Execution of the test process against a single identifiable release of the test object.






17. A set of input values - execution preconditions - expected results and execution postconditions - developed for a particular objective or test condition - such as to exercise a particular program path or to verify compliance with a specific requireme






18. An uninterrupted period of time spent in executing tests. In exploratory testing - each test session is focused on a charter - but testers can also explore new opportunities or issues during a session. The tester creates and executes test cases on th






19. A set of one or more test cases. [IEEE 829]






20. A test result which fails to identify the presence of a defect that is actually present in the test object.






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






22. Execution of a test on a specific version of the test object.






23. Testing that runs test cases that failed the last time they were run - in order to verify the success of corrective actions.






24. A systematic evaluation of software acquisition - supply - development - operation - or maintenance process - performed by or on behalf of management that monitors progress - determines the status of plans and schedules - confirms requirements and th






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






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






27. The organizational artifacts needed to perform testing - consisting of test environments - test tools - office environment and procedures.






28. The capability of the software product to provide appropriate performance - relative to the amount of resources used under stated conditions. [ISO 9126]






29. Hardware and software products installed at users' or customers' sites where the component or system under test will be used. The software may include operating systems - database management systems - and other applications.






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






31. An input for which the specification predicts a result.






32. The capability of the software product to be used in place of another specified software product for the same purpose in the same environment. [ISO 9126] See also portability. The ease with which the software product can be transferred from one hardw






33. A set of interrelated activities - which transform inputs into outputs. [ISO 12207]






34. A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script. [After IEEE 829]






35. A distinct set of test activities collected into a manageable phase of a project - e.g. the execution activities of a test level. [After Gerrard]






36. A group of people responsible for evaluating and approving or disapproving proposed changes to configuration items - and for ensuring implementation of approved changes. [IEEE 610]






37. Tests aimed at showing that a component or system does not work. Negative testing is related to the testers' attitude rather than a specific test approach or test design technique - e.g. testing with invalid input values or exceptions. [After Beizer]






38. An element of configuration management - consisting of the evaluation - co-ordination - approval or disapproval - and implementation of changes to configuration items after formal establishment of their configuration identification. [IEEE 610]






39. A document that consists of a test design specification - test case specification and/or test procedure specification.






40. A source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system (for a benchmark) - a user-manual - or an individual's specialized knowledge - but should not be the code. [Afte






41. An integration test type that is concerned with testing the interfaces between components or systems.






42. The process of recording information about tests executed into a test log.






43. A Linear Code Sequence And Jump - consisting of the following three items (conventionally identified by line numbers in a source code listing): the start of the linear sequence of executable statements - the end of the linear sequence - and the targe






44. A formula based test estimation method based on function point analysis. [TMap]






45. An approach to testing to reduce the level of product risks and inform stakeholders on their status - starting in the initial stages of a project. It involves the identification of product risks and their use in guiding the test process.






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






47. The degree to which a component - system or process meets specified requirements and/or user/customer needs and expectations. [After IEEE 610]






48. A detailed check of the test basis to determine whether the test basis is at an adequate quality level to act as an input document for the test process. [After TMap]






49. The process of finding - analyzing and removing the causes of failures in software.






50. A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain.







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