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. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






21. Testing software through executing it.






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






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






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






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






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






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






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






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 white box test design technique in which test cases are designed to execute branches.






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






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






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






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






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






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






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






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






39. Kind of unit testing - internal working of software






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






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






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. A white box test design technique in which test cases are designed to execute decision outcomes






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






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






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






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






49. Application Under Test






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







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