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






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






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






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






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






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






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






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






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






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






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






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






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






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






15. Testing software through executing it.






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






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






18. Kind of unit testing - internal working of software






19. Provide critical information during project






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






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






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






23. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






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






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. Similar to black box testing - structure of test cases in order to find defects and its strutured






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






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






38. A white box testing technique that exercises program loops






39. The expected results or performance characteristics that define whether the test cases passed or failed






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






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






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






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






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






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






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






47. Testing concerned with the accuracy of documentation.






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






49. The testing of individual software components.






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