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. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality






2. executing the software






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






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






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






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






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






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






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






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






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






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






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






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






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






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






17. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






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






19. Test case design






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






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






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






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






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






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






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






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






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






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






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






31. Testing one particular module - functionality heavily






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






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






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






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






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






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






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






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






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






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






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






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






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






45. Provide critical information during project






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






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






48. The testing of individual software components.






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






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