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 whether the system meets its specified objectives for maintainability.






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






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






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






5. The testing of individual software components.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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. The percentage of decision outcomes that have been exercised by a test suite.






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






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






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






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






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






29. Application Under Test






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






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






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






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






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






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. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






37. Testing software through executing it.






38. Provide critical information during project






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






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






41. Test case design






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






43. A white box testing technique that exercises program loops






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






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






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






47. Testing concerned with the accuracy of documentation.






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






49. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.






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