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 ratio between the number of defects found and the size of the component/system tested.






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






3. Actual inputs required to execute a test case






4. Used to test the functionality of software as mentioned in software requirement specifications.






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






6. A set of conditions that a system needs to meet in order to be accepted by end users






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






8. Testing software in its operational environment






9. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






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






12. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






13. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






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






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






18. A technique used to improve testing coverage by deliberately introducing faults in code.






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






20. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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






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






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






27. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






29. Occurrences that happen before and after an unexpected event






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






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






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






33. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






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






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






36. A functional testing approach in which test cases are designed based on business processes.






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






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






39. Testing an integrated system to validate it meets requirements






40. Combining components or sytems into larger structural units or subsystems.






41. Ability of software to provide appropriate performance relative to amount of resources used.






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






43. Linear Code Sequence and Jump.






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






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






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






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






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






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






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