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. Software products or applications designed to automate manual testing tasks.






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






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






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






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






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






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






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






9. Response of the application to an input






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






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






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






13. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






29. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






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






43. Waterfall iterative-incremental "V"






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






45. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






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






50. Conditions required to begin testing activities.