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






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






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






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






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






6. The testing of individual software components.






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






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






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






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






11. Testing software through executing it.






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






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






14. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






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






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






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






25. executing the software






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






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






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






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






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






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






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






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






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. It is a whole - is the whole process form review to plans strategy and whole thing






36. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






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






47. Provide critical information during project






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






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






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






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