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. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database






2. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]






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






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






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






6. Computer Aided Software Testing






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






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






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






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






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






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






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






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






15. Testing which covers all combinations of input values and preconditions for an element of the software under test






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






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






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






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






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






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






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






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






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






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






26. The testing of individual software components.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






41. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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