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. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






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






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






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






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






10. Conditions required to begin testing activities.






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






12. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






13. Linear Code Sequence and Jump.






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






15. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






17. Waterfall iterative-incremental "V"






18. An event or item that can be tested using one or more test cases






19. Sequence in which instructions are executed through a component or system






20. Measures amount of testing performed by a collection of test cases






21. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






23. Separation of testing responsibilities which encourages the accomplishment of objective testing






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






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






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






27. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






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






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






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






32. Tools used by developers to identify defects in programs.






33. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






35. Black-box test design technique - test cases are designed from a decision table.






36. Software products or applications designed to automate manual testing tasks.






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






38. Severity - Priority






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






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






41. Component - Integration - System - Acceptance






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






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






44. One defect prevents the detection of another.






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






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






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






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






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






50. Events that occurred during the testing process our investigation.