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 approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






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






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






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






5. Testing software through executing it.






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






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






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






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






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






11. Application Under Test






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






30. Computer Aided Software Testing






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






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






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






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






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






37. Kind of unit testing - internal working of software






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






39. Testing concerned with the accuracy of documentation.






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






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






42. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database






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






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






45. The testing of individual software components.






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






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






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






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






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






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