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






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






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






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






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






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






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






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






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






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






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






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






13. Test case design






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






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






16. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






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






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






24. Provide critical information during project






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






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






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






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






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






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






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






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






33. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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






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






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






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






47. executing the software






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






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






50. Testing software through executing it.