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. 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.
Authorization Testing
Heuristic evaluations
Concurrency Testing
End-to-end Testing

2. Computer Aided Software Testing
Equivalence Class
CAST
Dynamic Testing
Bugs

3. 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.
Branch coverage
Context Driven Testing
Keyword driven Testing
Component Testing

4. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Localization Testing
Fault
Big Bang Testing
Authorization Testing

5. Test case design
functional testing
Logic coverage Testing / Logic driven Testing / Structural
Localization Testing
Decision table testing

6. They arise from mistakes and errors made by people in either a program's source code or its design that prevents it from working correctly or produces an incorrect result
Bugs
Testing best practice
Dependency Testing
Benchmark Testing

7. A white box test design technique in which test cases are designed to execute branches.
Branch testing
black box testing
Integration Testing
Coverage Testing

8. 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
Statement coverage
Data-Driven Testing
SOA
Equivalence Partitioning

9. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Authorization Testing
Gamma testing
Equivalence partition Testing
Bugs

10. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Data-Driven Testing
black box testing
Incremental testing
Business process-based testing

11. A white box testing technique that exercises program loops
Loop Testing
test coverage
Equivalence partition Testing
Integration Testing

12. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Conformance Testing / Compliance Testing / Standards Testing
Interface Testing
software testing
Black Box Testing / Functional Testing

13. Determine whether a system meets some specified standard. external organization as complying with the standard
Accessibility Testing
Conformance Testing / Compliance Testing / Standards Testing
enough of testing
Equivalence partition Testing

14. 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.
Compatibility Testing
Equivalence partition Testing
Isolation Testing
Boundary value analysis/ testing

15. Testing one particular module - functionality heavily
white box testing
Gorilla Testing
Beta Testing / Field Testing
Branch testing

16. The process of testing to determine the interoperability of a software product
Maintenance testing
Decision testing
Interoperability testing
Fault

17. 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
Logic coverage Testing / Logic driven Testing / Structural
Load Testing
exploratory testing
Mutation testing

18. 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.
Equivalence Class
Bottom-up Testing
Grey Box Testing
Defect

19. 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.
Exploratory Testing
Quality
white box testing
Model Based Testing

20. 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
Statement coverage
Authorization Testing
test coverage
organisation structure

21. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Decision table testing
GUI Testing
Benchmark Testing
Exhaustive Testing

22. Similar to black box testing - structure of test cases in order to find defects and its strutured
Ad-hoc Testing
Code coverage
functional testing
Equivalence Partitioning

23. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Quality
Ad-hoc Testing
Code coverage
Interface Testing

24. It is a whole - is the whole process form review to plans strategy and whole thing
Ad-hoc Testing
Integration Testing
QA
Endurance Testing

25. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.
black box testing
Context Driven Testing
GUI Testing
software testing

26. Kind of unit testing - internal working of software
structural testing
Isolation Testing
Back-to-back testing
Dynamic Testing

27. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Acceptance criteria
Data flow Testing
Load Testing
Acceptance Testing/User Acceptance Testing

28. Testing software through executing it.
Code coverage
Benchmark Testing
High order tests
Dynamic Testing

29. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Benchmark Testing
Documentation Testing
organisation structure
software testing

30. 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
enough of testing
quality assurance process improvement
Branch
Basis Path Testing

31. 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
Compatibility Testing
Defect density
Back-to-back testing
Black Box Testing / Functional Testing

32. Can't see - test the functional testing - no access to code and testing is done on UI
End-to-end Testing
Documentation Testing
black box testing
Boundary value analysis/ testing

33. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Conformance Testing / Compliance Testing / Standards Testing
white box testing
software testing
Decision condition testing

34. Testing concerned with the accuracy of documentation.
Documentation Testing
Fuzz Testing
Endurance Testing
Mutation testing

35. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Integration Testing
Decision condition testing
Component Testing
black box testing

36. The process of testing to determine the efficiency of a software product
Maintainability Testing / Serviceability Testing
Efficiency testing
Beta Testing / Field Testing
Exhaustive Testing

37. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Dynamic Testing
Branch testing
Keyword driven Testing
Benchmark Testing

38. This term refers to making software specifically designed for a specific locality
Code coverage
Decision condition testing
Localization Testing
Model Based Testing

39. 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
Component Testing
Isolation Testing
quality assurance process improvement
Monkey Testing

40. Testing which covers all combinations of input values and preconditions for an element of the software under test
Boundary value analysis/ testing
Exhaustive Testing
Interface Testing
Logic coverage Testing / Logic driven Testing / Structural

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.
Exploratory Testing
providing information - metric
Beta Testing / Field Testing
Bottom-up Testing

42. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Basis Path Testing
Authorization Testing
Conformance Testing / Compliance Testing / Standards Testing
Ad-hoc Testing

43. Stakeholder stakeholder satisfaction with test results report
Statement coverage
Big Bang Testing
Black Box Testing / Functional Testing
providing information - metric

44. 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
Gorilla Testing
SOA
Quality
organisation structure

45. 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
Ad-hoc Testing
Loop Testing
Coverage Testing
Statement coverage

46. 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.
N+ Testing
Arc Testing / Branch Testing
Gorilla Testing
QA

47. Testing whether the system is compatible with other systems with which it should communicate.
Interface Testing
Compatibility Testing
Installation Testing
Integration Testing

48. Testing whether the system meets its specified objectives for maintainability.
Maintainability Testing / Serviceability Testing
Branch testing
Interoperability testing
Fuzz Testing

49. 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
Data flow Testing
Integration Testing
Keyword driven Testing
Testing best practice

50. 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
Concurrency Testing
Equivalence Partitioning
Maintainability Testing / Serviceability Testing
Exhaustive Testing