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






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






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






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






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






6. Stakeholder stakeholder satisfaction with test results report






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






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






9. Provide critical information during project






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






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






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






13. An anomaly or flaw in a delivered work product. found during early lifecycle phases A defect can be any kind of issue you want tracked and resolved.






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






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






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






17. Multi-user testing geared towards determining the effects of accessing the same application code - module or database records. Identifies and measures the level of locking - deadlocking and use of single-threaded code and locking semaphores






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






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






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






21. Testing one particular module - functionality heavily






22. A black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table






23. executing the software






24. A test suite that exercises the full functionality of a product but does not test features in detail






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






44. Application Under Test






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






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






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






48. Test case design






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






50. Computer Aided Software Testing