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 in which test cases are designed based on variable usage within the code.






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






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






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






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






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






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






8. Testing software through executing it.






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






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






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






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






13. Test case design






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






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






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






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






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






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






20. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






30. Kind of unit testing - internal working of software






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






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






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






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






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






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






37. A white box testing technique that exercises program loops






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






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






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






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






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






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






44. A scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested.






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






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






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






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






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






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