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. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).






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






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






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






5. The testing of individual software components.






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






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






8. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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. The expected results or performance characteristics that define whether the test cases passed or failed






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






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






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






21. Test case design






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






40. The percentage of decision outcomes that have been exercised by a test suite.






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






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






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






44. A white box testing technique that exercises program loops






45. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices






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






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






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






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






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