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






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






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






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






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






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






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






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






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






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






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






12. A scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested.






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






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






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






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






17. The testing of individual software components.






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






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






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






21. A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification






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






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






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






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






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






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






28. Testing one particular module - functionality heavily






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






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






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






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






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






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






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






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






37. Stakeholder stakeholder satisfaction with test results report






38. Test case design






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






40. Computer Aided Software Testing






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






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






43. Kind of unit testing - internal working of software






44. It is a whole - is the whole process form review to plans strategy and whole thing






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






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






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests