Test your basic knowledge |

Software Testing And Qa

Subject : it-skills
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. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.






2. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases






3. Multi-user testing geared towards determining the effects of accessing the same application code - module or database records. Identifies and measures the level of locking - deadlocking and use of single-threaded code and locking semaphores






4. Once the alpha phase is complete development enters the beta phase. Versions of the software known as beta-versions are released to a limited audience outside of the company to ensure that the product has few faults or bugs. black box






5. An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.






6. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent






7. A white box testing technique that exercises program loops






8. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration






9. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).






10. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules






11. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.






12. An accidental condition that causes the failure of a component in the implementation model to perform its required behavior. A fault is the root cause of one or more defects identified by observing one or more failures.






13. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.






14. Testing in which the action of a test case is parameterized by externally defined data values - maintained as a file or spreadsheet. A common technique in Automated Testing






15. executing the software






16. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared and analyzed in cases of discrepancies






17. Testing one particular module - functionality heavily






18. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.






19. The totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs." defined by ISO 8402 1986






20. Testing software through executing it.






21. Approach to doing something that generally give good results when applied appropriately and thoughfully






22. Similar to black box testing - structure of test cases in order to find defects and its strutured






23. Designing tests based on objectives derived from the architectural or detail design of the software (e.g. - tests that execute specific invocation paths or probe the worst case behaviour of algorithms).






24. Defined as any testing that occurs outside of the development environment. installed on. simply appear to be to run a setup program - can be used with confidence






25. Informal method of usability inspection in the field of human-computer interaction. identifying the usability problems . involves evaluators examining the interface and judging its compliance






26. A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+.






27. The expected results or performance characteristics that define whether the test cases passed or failed






28. A black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table






29. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.






30. Stakeholder stakeholder satisfaction with test results report






31. Testing which covers all combinations of input values and preconditions for an element of the software under test






32. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes






33. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)






34. Computer Aided Software Testing






35. The process of testing to determine the interoperability of a software product






36. A basic block that can be selected for execution based on a program construct in which one of two or more alternative program path is available






37. Black-box tests conducted once the software has been integrated






38. Testing using input values that should be rejected by the component or system






39. Determine whether a system meets some specified standard. external organization as complying with the standard






40. Model-based testing refers to software testing where test cases are derived in whole or in part from a model that describes some (usually functional) aspects of the system under test.






41. Root cause analyst - base of the problem - customer satisfaction report






42. An anomaly or flaw in a delivered work product. found during early lifecycle phases A defect can be any kind of issue you want tracked and resolved.






43. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.






44. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers






45. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.






46. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database






47. A scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested.






48. A test case design technique for a component in which test cases are designed which include representatives of boundary values - the defined limits of an output domain.






49. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.






50. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned