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. Testing software in its operational environment






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






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






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






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






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






7. Response of the application to an input






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. Informal testing technique in which test planning and execution run in parallel






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






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






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






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






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






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






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






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






18. An analysis that determines the portion of code on software executed by a set of test cases






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






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






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






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






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






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






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






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






27. Used to replace a component that calls another component.






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






29. A review not based on a formal documented procedure






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






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






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






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






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






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






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






37. Severity - Priority






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






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






40. Occurrences that happen before and after an unexpected event






41. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






42. Linear Code Sequence and Jump.






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






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






45. The capability of a software product to provide agreed and correct output with the required degree of precision






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






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






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






49. Waterfall iterative-incremental "V"






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