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






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






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






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






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






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






7. Test case design






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






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






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






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






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






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






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






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






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






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






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






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






20. Testing concerned with the accuracy of documentation.






21. Testing one particular module - functionality heavily






22. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared and analyzed in cases of discrepancies






23. executing the software






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






25. The testing of individual software components.






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






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






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






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






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






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






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






33. Testing software through executing it.






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






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






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






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






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






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






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






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






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






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






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






45. Computer Aided Software Testing






46. Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing






47. A white box testing technique that exercises program loops






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






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






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