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. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent






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






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






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






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






6. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or






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






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






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






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






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






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






13. Computer Aided Software Testing






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






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






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






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






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






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






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






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






22. Testing one particular module - functionality heavily






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






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






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






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






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






28. Testing software through executing it.






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






30. Testing concerned with the accuracy of documentation.






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






32. executing the software






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






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






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






36. Kind of unit testing - internal working of software






37. Provide critical information during project






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






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






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






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






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






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






44. A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations






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






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






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






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






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






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