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. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.






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






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






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






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






6. Testing whether the system meets its specified objectives for maintainability.






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






8. Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields & Cookie security and Lockout testing . permitting unauthorised access.






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






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






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






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






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






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






15. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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






17. It is a whole - is the whole process form review to plans strategy and whole thing






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






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






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






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






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






24. A white box test case design techniques that uses the algorithmic flow of the program to design tests






25. Testing in which test cases are designed based on variable usage within the code.






26. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.






27. Application Under Test






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






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






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






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






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






33. Provide critical information during project






34. Testing one particular module - functionality heavily






35. Kind of unit testing - internal working of software






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






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






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






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






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






41. Stakeholder stakeholder satisfaction with test results report






42. The testing of individual software components.






43. A white box testing technique that exercises program loops






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






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






46. The process of testing to determine the efficiency of a software product






47. Testing whether the system is compatible with other systems with which it should communicate.






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






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






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