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. Testing software in its operational environment






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






3. A component of the incident report that determines the actual effect of the incident on the software and its users.






4. Severity - Priority






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






6. Linear Code Sequence and Jump.






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






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






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






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






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






12. Testing an integrated system to validate it meets requirements






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






14. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






17. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






18. Actual inputs required to execute a test case






19. Insertion of additional code in the existing program in order to count coverage items.






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






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






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






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






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






25. The ratio between the number of defects found and the size of the component/system tested.






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






27. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






28. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






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






32. All possible combinations of input values and preconditions are tested.






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






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






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






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






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






38. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






45. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






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






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






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






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