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. Integration approach components or subsystems are combined all at once rather than in stages.






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






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






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






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






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






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






8. Requirements that determine the functionality of a software system.






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






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






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






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






13. Testing an integrated system to validate it meets requirements






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






15. A review not based on a formal documented procedure






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






17. The ratio between the number of defects found and the size of the component/system tested.






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






19. Response of the application to an input






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






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






22. One defect prevents the detection of another.






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






24. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






45. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






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






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