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






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






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






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






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






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






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






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






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






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






11. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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. The process of testing to determine the efficiency of a software product






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






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






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






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






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






27. A test that exercises a feature of a product in full detail.






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






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






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






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






32. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm






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






34. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






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






41. Provide critical information during project






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






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






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






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






46. A white box testing technique that exercises program loops






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






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






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