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






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






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






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






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






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






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






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






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






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






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






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






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






14. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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






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






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






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 branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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. executing the software






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






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






47. Provide critical information during project






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






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






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