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 organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]






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






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






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






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






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






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






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






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






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






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






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






13. The testing of individual software components.






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






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






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






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






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






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






20. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent






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






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






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






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






25. Kind of unit testing - internal working of software






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






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






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






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






30. Application Under Test






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






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






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






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






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






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






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






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. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






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






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






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






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. A white box test design technique in which test cases are designed to execute decision outcomes






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






46. Testing one particular module - functionality heavily






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






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






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






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







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