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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






31. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






32. Find defects in code while the software application being tested is running.






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






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






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






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






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






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






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






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






41. Testing software in its operational environment






42. Occurrences that happen before and after an unexpected event






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






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






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






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






47. Linear Code Sequence and Jump.






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






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






50. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.