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. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






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






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






4. Testing software through executing it.






5. Testing one particular module - functionality heavily






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






21. A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point - each possible branch be executed at least once.






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






23. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






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






32. executing the software






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






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






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






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






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






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






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






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






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






42. Testing concerned with the accuracy of documentation.






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






44. Kind of unit testing - internal working of software






45. Application Under Test






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






47. Test case design






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests