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. This term refers to making software specifically designed for a specific locality






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






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






5. The testing of individual software components.






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






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






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






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






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






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






12. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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






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






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






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






24. executing the software






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






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






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






28. Computer Aided Software Testing






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






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






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






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






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






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






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






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






37. Testing software through executing it.






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






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






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






41. Application Under Test






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






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






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






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






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






47. Test case design






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






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






50. A white box testing technique that exercises program loops