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 concerned with the accuracy of documentation.






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






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






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






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






6. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






15. Testing software through executing it.






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






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






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






19. executing the software






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






21. Computer Aided Software Testing






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






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






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






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






26. Test case design






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






28. Coverage testing is concerned with the degree to which test cases exercise or cover the logic (source code) of the software module or unit. It is also a measure of coverage of code lines & code branches and code branch combinations






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






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






31. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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






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






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






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






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






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






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






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






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






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






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






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






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






45. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm






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






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






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






49. A white box testing technique that exercises program loops






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