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. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






3. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






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






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






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






7. A document that provides the structure for writing test cases.






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






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






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






11. Human action that generates an incorrect result.






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






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






14. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






16. Testing software components that are separately testable. Also module program and unit testing.






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






18. Based on analysis of functional specifications of a system.






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






20. Actual inputs required to execute a test case






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






22. Tests interfaces between components and between integrated components and systems.






23. Occurrences that happen before and after an unexpected event






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






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






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






27. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






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






30. Waterfall iterative-incremental "V"






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






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






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






34. Linear Code Sequence and Jump.






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






36. A review not based on a formal documented procedure






37. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






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






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






40. Response of the application to an input






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






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






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






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






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






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






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






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






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






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