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. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






2. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






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






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






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






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






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






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






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






11. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






30. Component - Integration - System - Acceptance






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






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






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






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






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






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






37. Severity - Priority






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






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






40. Conditions required to begin testing activities.






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






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






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






44. Response of the application to an input






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






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






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






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






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






50. Linear Code Sequence and Jump.