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






2. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






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






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






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






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






16. Testing software in its operational environment






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






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






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






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






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






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






23. A review not based on a formal documented procedure






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






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






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






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






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






29. Linear Code Sequence and Jump.






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






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






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






33. Informal testing technique in which test planning and execution run in parallel






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






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






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






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






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






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






40. Tools used to store and manage incidents return phone defects failures or anomalies.






41. Calculates the number of executed branch outcomes in code.






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






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






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






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






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






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests