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. Checks for memory leaks or other problems that may occur with prolonged execution






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






17. Testing software through executing it.






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






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






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






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






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






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






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






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






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






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






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






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






31. Provide critical information during project






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






33. The testing of individual software components.






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






35. Stakeholder stakeholder satisfaction with test results report






36. A white box testing technique that exercises program loops






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






38. executing the software






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






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






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






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






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






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






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






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






47. Kind of unit testing - internal working of software






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






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






50. Testing concerned with the accuracy of documentation.







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