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. A white box testing technique that exercises program loops






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






3. The testing of individual software components.






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






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






6. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.






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






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






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






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






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






12. Testing software through executing it.






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






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






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






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






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






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






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






20. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






43. Stakeholder stakeholder satisfaction with test results report






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






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






46. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






47. Application Under Test






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






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






50. Knows about the software and test - no proper plan







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests