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 which covers all combinations of input values and preconditions for an element of the software under test






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






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






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






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






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






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






8. Kind of unit testing - internal working of software






9. A test that exercises a feature of a product in full detail.






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






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






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






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






14. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






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






21. Depends on the schedule and risk based - business impact follow the 20-80 rules






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






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






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






25. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






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






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






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






36. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]






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






38. Provide critical information during project






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






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






41. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices






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






43. Testing concerned with the accuracy of documentation.






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






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






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






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






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






49. executing the software






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