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






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






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






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






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






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






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






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






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






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






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






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






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






15. The percentage of executable statements that have been exercised by a test suite.






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






17. executing the software






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






19. Computer Aided Software Testing






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






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






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






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






24. Testing software through executing it.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






43. Testing one particular module - functionality heavily






44. The testing of individual software components.






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






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






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






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






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






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