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 carried out using no recognised test case design technique. It is also known as Exploratory Testing






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






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






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






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






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






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






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






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






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






11. Black-box tests conducted once the software has been integrated






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






13. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






35. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






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






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






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






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






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






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






47. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.






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






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






50. Kind of unit testing - internal working of software