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. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






3. One defect prevents the detection of another.






4. Testing software in its operational environment






5. Sequence in which instructions are executed through a component or system






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






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






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






9. Sequence in which data items are accessed or modified by code.






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






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






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






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






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






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






16. Allows storage of test input and expected results in one or more central data sources or databases.






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






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






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






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






21. Conditions required to begin testing activities.






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






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






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






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






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






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






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






29. Linear Code Sequence and Jump.






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






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






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






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






34. Severity - Priority






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






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






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






38. Waterfall iterative-incremental "V"






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






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






41. Deviation of a software system from its expected delivery services or results






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






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






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






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






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






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






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






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






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