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 black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






3. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






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






6. Special-purpose software used to simulate a component called by the component under test






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






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






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






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






11. Used to replace a component that calls another component.






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






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






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






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






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






17. Testing software in its operational environment






18. Tools used to store and manage incidents return phone defects failures or anomalies.






19. Waterfall iterative-incremental "V"






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






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






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






23. A unique identifier for each incident report generated during test execution.






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






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






26. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






29. Integration approach components or subsystems are combined all at once rather than in stages.






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






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






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






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






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






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






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






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






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






39. Record details of test cases executed Record order of execution record results






40. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






41. Occurrences that happen before and after an unexpected event






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






43. Testing an integrated system to validate it meets requirements






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






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






46. Severity - Priority






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






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






49. Special-purpose software used to simulate a component that calls the component under test






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