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. Approach to doing something that generally give good results when applied appropriately and thoughfully






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






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






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






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






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






7. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.






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






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






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






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






12. Kind of unit testing - internal working of software






13. executing the software






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






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






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






17. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






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






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






20. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing






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






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






23. Knows about the software and test - no proper plan






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






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






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






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






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






29. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.






30. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications






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






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






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






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






35. A white box test design technique in which test cases are designed to execute branches.






36. The percentage of executable statements that have been exercised by a test suite.






37. Application Under Test






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






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






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






41. A service oriented architecture (SOA) is a design model which relies on a collection of loosely coupled self contained services that communicate with each other through the internet and can be called from multiple clients in a standard fashion






42. A test that a user/sponsor and manufacturer/producer jointly perform on a finished - engineered product/system through black-box testing - as functional test & beta test & QA test & application test & confidence test & final test or end user test






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






44. Testing software through executing it.






45. The testing of individual software components.






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






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






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






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






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