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 whether the system is compatible with other systems with which it should communicate.






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






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






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






5. Provide critical information during project






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






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






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






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






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






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






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






13. Computer Aided Software Testing






14. Kind of unit testing - internal working of software






15. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.






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






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






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






19. Test case design






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






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






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






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






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






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






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






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






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






29. executing the software






30. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






37. Application Under Test






38. A white box testing technique that exercises program loops






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






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






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






42. The testing of individual software components.






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






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






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






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






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






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






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






50. Stakeholder stakeholder satisfaction with test results report