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 number of independent paths through a program. Cyclomatic complexity is defined as: L - N + 2P - where - L = the number of edges/links in a graph - N = the number of nodes in a graph - P = the number of disconnected parts of the graph (e.g. a cal






2. The process of testing to determine the reliability of a software product.






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






4. The total costs incurred on quality activities and issues and often split into prevention costs - appraisal costs - internal failure costs and external failure costs.






5. A set of several test cases for a component or system under test - where the post condition of one test is often used as the precondition for the next one.






6. Artifacts produced during the test process required to plan - design - and execute tests - such as documentation - scripts - inputs - expected results - set-up and clear-up procedures - files - databases - environment - and any additional software or






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






8. Any event occurring that requires investigation. [After IEEE 1008]






9. A device or storage area used to store data temporarily for differences in rates of data flow - time or occurrence of events - or amounts of data that can be handeld by the devices or processes involved in the transfer or use of the data. [IEEE 610]






10. A tool that carries out static analysis.






11. Testing the methods and processes used to access and manage the data(base) - to ensure access methods - processes and data rules function as expected and that during access to the database - data is not corrupted or unexpectedly deleted - updated or






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






13. The process consisting of all life cycle activities - both static and dynamic - concerned with planning - preparation and evaluation of software products and related work products to determine that they satisfy specified requirements - to demonstrate






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






15. The degree to which a component or system has a design and/or internal structure that is difficult to understand - maintain and verify. See also cyclomatic complexity. The number of independent paths through a program. Cyclomatic complexity is define






16. 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]






17. A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. [After IEEE 829]






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






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






20. The process of testing to determine the maintainability of a software product.






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






22. An instance of an output. See also output.A variable (whether stored within a component or outside) that is written by a component.






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






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






25. A five level staged framework for test process improvement - related to the Capability Maturity Model Integration (CMMI) - that describes the key elements of an effective test process.






26. The level of (business) importance assigned to an item - e.g. defect.






27. The process of testing an integrated system to verify that it meets specified requirements. [Hetzel]






28. The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs. [After ISO 9126]






29. Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled. [ISO 9000]






30. A point in time in a project at which defined (intermediate) deliverables and results should be ready.






31. The process of testing to determine the interoperability of a software product.






32. The person responsible for project management of testing activities and resources - and evaluation of a test object. The individual who directs - controls - administers - plans and regulates the evaluation of a test object.






33. Recording the details of any incident that occurred - e.g. during testing.






34. An aggregation of hardware - software or both - that is designated for configuration management and treated as a single entity in the configuration management process. [IEEE 610]






35. The method used to perform the actual test execution - either manual or automated.






36. A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements - including the constraints of time - cost and resources. [ISO 9000]






37. The process of confirming that a component - system or person complies with its specified requirements - e.g. by passing an exam.






38. A test result in which a defect is reported although no such defect actually exists in the test object.






39. The capability of the software to be understood - learned - used and attractive to the user when used under specified conditions. [ISO 9126]






40. A computational model consisting of a finite number of states and transitions between those states - possibly with accompanying actions. [IEEE 610]






41. A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item - control changes to those characteristics - record and report change processi






42. The degree of impact that a defect has on the development or operation of a component or system. [After IEEE 610]






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






44. 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 testing tasks - who will do each task - degree of tester independence - the tes






45. The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions. [IEEE 610] See also error-tolerance - fault-tolerance. The ability of a system or component to continue normal o






46. The ability of the software product to perform its required functions under stated conditions for a specified period of time - or for a specified number of operations. [ISO 9126]






47. During the test closure phase of a test process data is collected from completed activities to consolidate experience - testware - facts and numbers. The test closure phase consists of finalizing and archiving the testware and evaluating the test pro






48. A tool to support performance testing and that usually has two main facilities: load generation and test transaction measurement. Load generation can simulate either multiple users or high volumes of input data. During execution - response time measu






49. Comparison of actual and expected results - performed while the software is being executed - for example by a test execution tool.






50. The process of testing to determine the maintainability of a software product.







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