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






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






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






4. Testing software through executing it.






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






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






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






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






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






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






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






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






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






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






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






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






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






18. Determine whether a system meets some specified standard. external organization as complying with the standard






19. The testing of individual software components.






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






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






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






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






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






25. executing the software






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






27. Computer Aided Software Testing






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






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






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






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






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






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






34. Kind of unit testing - internal working of software






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






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






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






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






39. A white box testing technique that exercises program loops






40. Test case design






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






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






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






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






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






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






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






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