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. Tools used by developers to identify defects in programs.






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






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






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






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






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






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






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






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






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






11. A technique used to improve testing coverage by deliberately introducing faults in code.






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






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






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






15. Human action that generates an incorrect result.






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






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






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






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






20. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






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






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






25. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






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






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






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






32. Conditions required to begin testing activities.






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






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






35. Used to test the functionality of software as mentioned in software requirement specifications.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






50. Occurrences that happen before and after an unexpected event