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. Kind of unit testing - internal working of software






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






3. Testing software through executing it.






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






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






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






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






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






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






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






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






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






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






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






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






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






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. A test that exercises a feature of a product in full detail.






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






20. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.






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






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






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






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






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






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






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






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






29. Application Under Test






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






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






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






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






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






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






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






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






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






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






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






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






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






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






44. Computer Aided Software Testing






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






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






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






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






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






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