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 functional testing approach in which test cases are designed based on business processes.






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






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






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






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






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






7. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






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






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






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






11. Response of the application to an input






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






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






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






15. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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. A set of conditions that a system needs to meet in order to be accepted by end users






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






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






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






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






30. Calculates the number of executed branch outcomes in code.






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






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






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






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






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






36. Informal testing technique in which test planning and execution run in parallel






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






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






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






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






41. Linear Code Sequence and Jump.






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






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






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






45. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






46. Actual inputs required to execute a test case






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






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






49. Human action that generates an incorrect result.






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