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 process of testing to determine the efficiency of a software product






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






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






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






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






6. Kind of unit testing - internal working of software






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






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






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






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






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






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






13. The testing of individual software components.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






30. Computer Aided Software Testing






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






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






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






34. Test case design






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






36. executing the software






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






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






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






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






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






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






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






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






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






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






48. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.






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






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