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. It is a whole - is the whole process form review to plans strategy and whole thing






2. A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations






3. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality






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






5. Can't see - test the functional testing - no access to code and testing is done on UI






6. They arise from mistakes and errors made by people in either a program's source code or its design that prevents it from working correctly or produces an incorrect result






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






8. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]






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






10. Test case design






11. A white box test design technique in which test cases are designed to execute decision outcomes






12. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.






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






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






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






16. Depends on the schedule and risk based - business impact follow the 20-80 rules






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






18. Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing






19. A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification






20. An approach to integration testing where the lowest level components are tested first - then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.






21. A test suite that exercises the full functionality of a product but does not test features in detail






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






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






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






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






26. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or






27. Checks for memory leaks or other problems that may occur with prolonged execution






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






29. Coverage testing is concerned with the degree to which test cases exercise or cover the logic (source code) of the software module or unit. It is also a measure of coverage of code lines & code branches and code branch combinations






30. Testing concerned with the accuracy of documentation.






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






32. A white box testing technique that exercises program loops






33. executing the software






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






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






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






37. This term refers to making software specifically designed for a specific locality






38. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.






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






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






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






42. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






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






44. Testing the changes to an operational system or the impact of a changed environment to an operational system






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






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






47. Testing a system or an Application on the fly - i.e just few tests here and there to ensure the system or an application does not crash out






48. Computer Aided Software Testing






49. A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point - each possible branch be executed at least once.






50. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs