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. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






18. An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.






19. Testing concerned with the accuracy of documentation.






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






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






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






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






25. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






41. Testing one particular module - functionality heavily






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






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






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






45. A white box testing technique that exercises program loops






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






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






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






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






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