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. It is a whole - is the whole process form review to plans strategy and whole thing






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






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






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






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






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






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






8. The testing of individual software components.






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






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






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






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






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






14. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






34. Computer Aided Software Testing






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






36. executing the software






37. Testing one particular module - functionality heavily






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






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






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






41. A white box testing technique that exercises program loops






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






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






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






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






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






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






48. Kind of unit testing - internal working of software






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






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