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






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






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






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






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. This term refers to making software specifically designed for a specific locality






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






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






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






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






11. A test that exercises a feature of a product in full detail.






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






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






14. Application Under Test






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






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






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






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






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






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






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






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






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






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






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






26. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






34. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






35. Stakeholder stakeholder satisfaction with test results report






36. Computer Aided Software Testing






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






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






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






40. Testing software through executing it.






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






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






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






44. Test case design






45. executing the software






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






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






48. Testing one particular module - functionality heavily






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






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