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 suite that exercises the full functionality of a product but does not test features in detail






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






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






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






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






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






7. Provide critical information during project






8. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






23. Testing software through executing it.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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