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






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






3. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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






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






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






14. A review not based on a formal documented procedure






15. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






16. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






23. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






33. Human action that generates an incorrect result.






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






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






36. Actual inputs required to execute a test case






37. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






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






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






40. Severity - Priority






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






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






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






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






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






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






47. One defect prevents the detection of another.






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






49. Response of the application to an input






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