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 that exercises a feature of a product in full detail.






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






3. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases






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






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






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






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






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






9. executing the software






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






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






12. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






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






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






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






26. Test case design






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






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






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






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






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






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






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






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






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






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






37. A white box testing technique that exercises program loops






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






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






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






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






42. Testing software through executing it.






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






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






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






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






47. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






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






49. The testing of individual software components.






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