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. Response of the application to an input






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






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






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 combined and tested in the order in which basic functionalities start working






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






7. Conditions required to begin testing activities.






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






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






10. Linear Code Sequence and Jump.






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






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






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






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






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






16. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






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






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






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






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






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






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






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






26. Ability of software to provide appropriate performance relative to amount of resources used.






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






28. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






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






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






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






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






34. Occurrences that happen before and after an unexpected event






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






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






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






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






39. The process of finding analyzing and removing causes of failure in a software product.






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






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






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






43. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






50. Testing software in its operational environment