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. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






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






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






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






5. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases






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






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






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






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






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






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






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






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






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






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






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






17. The testing of individual software components.






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






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






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






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






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






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






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






25. Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields & Cookie security and Lockout testing . permitting unauthorised access.






26. Testing concerned with the accuracy of documentation.






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






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






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






30. Testing software through executing it.






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






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






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






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






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






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






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






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






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






40. Provide critical information during project






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






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






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






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






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






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






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






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






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






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