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. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.






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






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






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






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






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






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






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






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






10. executing the software






11. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






20. Testing one particular module - functionality heavily






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






22. Application Under Test






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






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






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






26. Can't see - test the functional testing - no access to code and testing is done on UI






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






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






29. Testing software through executing it.






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






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






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






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






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






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






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






37. Stakeholder stakeholder satisfaction with test results report






38. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






46. Computer Aided Software Testing






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






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






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






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