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. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






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






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






6. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






27. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






45. Testing software in its operational environment






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






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






48. Linear Code Sequence and Jump.






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






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