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






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






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






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






5. Provide critical information during project






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






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






8. Application Under Test






9. Test case design






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






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






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






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






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






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






16. Testing in which the action of a test case is parameterized by externally defined data values - maintained as a file or spreadsheet. A common technique in Automated Testing






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






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






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






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






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






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






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






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






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






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






27. A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification






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






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






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






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






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






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






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






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






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






37. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






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






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






40. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests