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. Tools used to identify and calculate coverage items in program code.






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






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






4. A task of maintaining and controlling changes to all entities of a system.






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






6. A table showing combinations of inputs and their associated actions.






7. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






8. White-box design technique used to design test cases for a software component using LCSAJ.






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






10. Allows storage of test input and expected results in one or more central data sources or databases.






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






12. Testing an integrated system to validate it meets requirements






13. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






14. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






16. One defect prevents the detection of another.






17. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






18. Conditions required to begin testing activities.






19. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






20. A review not based on a formal documented procedure






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






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






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






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






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






26. The capability of a software product to provide agreed and correct output with the required degree of precision






27. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






28. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






30. Integration approach components or subsystems are combined all at once rather than in stages.






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






32. Testing software in its operational environment






33. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






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






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






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






38. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






39. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






41. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






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






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






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






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






48. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






50. Testing performed to determine whether the system meets acceptance criteria







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