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. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






5. Component - Integration - System - Acceptance






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






7. Occurrences that happen before and after an unexpected event






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






9. Testing performed to determine whether the system meets acceptance criteria






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






11. A review not based on a formal documented procedure






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






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






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






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






16. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






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






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






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






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






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






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






23. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






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






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






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






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






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






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






30. Linear Code Sequence and Jump.






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






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






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






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






35. Human action that generates an incorrect result.






36. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






49. Software products or applications designed to automate manual testing tasks.






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