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






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






3. Application Under Test






4. Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields & Cookie security and Lockout testing . permitting unauthorised access.






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






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






7. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






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. Similar to black box testing - structure of test cases in order to find defects and its strutured






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






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






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






20. Provide critical information during project






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






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






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






24. executing the software






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






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






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






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






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






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






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






32. Computer Aided Software Testing






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






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






35. Testing software through executing it.






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






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






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






39. Testing one particular module - functionality heavily






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






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






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






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






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






45. Kind of unit testing - internal working of software






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






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






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






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






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