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. Testing the changes to an operational system or the impact of a changed environment to an operational system






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






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






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






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






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






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






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






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






10. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm






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






12. Application Under Test






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






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






15. Testing one particular module - functionality heavily






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






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






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






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






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






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






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






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






25. A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point - each possible branch be executed at least once.






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






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






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






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






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






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






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






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






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






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






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






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






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






39. Kind of unit testing - internal working of software






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






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






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






43. The testing of individual software components.






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






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






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






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






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






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






50. Testing software through executing it.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests