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 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
Back-to-back testing
Incremental testing
Breadth Testing
Conversion Testing / Migration Testing

2. A white box test design technique in which test cases are designed to execute decision outcomes
Loop Testing
Conformance Testing / Compliance Testing / Standards Testing
Maintainability Testing / Serviceability Testing
Decision testing

3. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Logic coverage Testing / Logic driven Testing / Structural
Branch coverage
Loop Testing
Fuzz Testing

4. Similar to black box testing - structure of test cases in order to find defects and its strutured
Mutation testing
Black Box Testing / Functional Testing
AUT
functional testing

5. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Interface Testing
Breadth Testing
Basis Path Testing
best practice

6. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
quality assurance process improvement
Equivalence Class
GUI Testing
Branch coverage

7. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Load Testing
Maintenance testing
Endurance Testing
Design based Testing

8. Black-box tests conducted once the software has been integrated
Design based Testing
Fuzz Testing
Mutation testing
High order tests

9. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
white box testing
Gamma testing
software testing
CAST

10. Testing in which test cases are designed based on variable usage within the code.
Maintenance testing
Arc Testing / Branch Testing
Data flow Testing
Concurrency Testing

11. Kind of unit testing - internal working of software
Loop Testing
N+ Testing
Efficiency testing
structural testing

12. The process of testing to determine the interoperability of a software product
Branch testing
Interoperability testing
Defect density
Data flow Testing

13. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Isolation Testing
Equivalence Partitioning
Dynamic Testing
Branch coverage

14. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Alpha Testing
Data-Driven Testing
Interface Testing
Basis Path Testing

15. 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
Black Box Testing / Functional Testing
quality assurance process improvement
N+ Testing
Endurance Testing

16. 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.
Decision table testing
Data-Driven Testing
quality assurance process improvement
Model Based Testing

17. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Fuzz Testing
Isolation Testing
Incremental testing
providing information - metric

18. 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.
Fault
Fuzz Testing
Design based Testing
Incremental testing

19. 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.
Quality
Context Driven Testing
Defect density
Model Based Testing

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.
providing information - metric
Data-Driven Testing
Bottom-up Testing
providing information Objective

21. The process of testing to determine the efficiency of a software product
Business process-based testing
Decision table testing
Efficiency testing
test coverage

22. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
High order tests
Benchmark Testing
Authorization Testing
Isolation Testing

23. Can't see - test the functional testing - no access to code and testing is done on UI
Black Box Testing / Functional Testing
Quality
Arc Testing / Branch Testing
black box testing

24. Checks for memory leaks or other problems that may occur with prolonged execution
Exhaustive Testing
Loop Testing
Endurance Testing
Authorization Testing

25. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
SOA
Breadth Testing
Equivalence partition Testing
Maintenance testing

26. 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
Gamma testing
structural testing
Branch
Defect

27. A test that exercises a feature of a product in full detail.
Interoperability testing
Depth Testing
Branch coverage
test coverage

28. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Development testing
Testing best practice
Dependency Testing
Ad-hoc Testing

29. It is a whole - is the whole process form review to plans strategy and whole thing
Loop Testing
QA
Boundary value analysis/ testing
architecure of SOA

30. 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
Acceptance Testing/User Acceptance Testing
Statement coverage
Branch coverage
Accessibility Testing

31. Knows about the software and test - no proper plan
functional testing
QA
Quality
exploratory testing

32. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
AUT
Documentation Testing
Dynamic Testing
Agile Testing

33. 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.
Fuzz Testing
Dynamic Testing
Heuristic evaluations
Keyword driven Testing

34. Stakeholder stakeholder satisfaction with test results report
Exploratory Testing
providing information - metric
Component Testing
Beta Testing / Field Testing

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
Acceptance criteria
providing information Objective
SOA
Gamma testing

36. This term refers to making software specifically designed for a specific locality
Localization Testing
Efficiency testing
Conversion Testing / Migration Testing
white box testing

37. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
backend testing/database testing
Breadth Testing
Dynamic Testing
Decision table testing

38. 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.
architecure of SOA
Mutation testing
Authorization Testing
organisation structure

39. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Boundary value analysis/ testing
Incremental testing
Equivalence Class
Monkey Testing

40. 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.
Load Testing
Code coverage
organisation structure
Equivalence Class

41. Provide critical information during project
providing information Objective
Decision table testing
Context Driven Testing
Logic coverage Testing / Logic driven Testing / Structural

42. 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.
Exploratory Testing
Maintenance testing
End-to-end Testing
Ad-hoc Testing

43. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Efficiency testing
Depth Testing
white box testing
Endurance Testing

44. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Concurrency Testing
Decision condition testing
Localization Testing
Statement coverage

45. 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
Monkey Testing
Statement coverage
Loop Testing
Interface Testing

46. A white box testing technique that exercises program loops
black box testing
providing information - metric
Fuzz Testing
Loop Testing

47. 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
Integration Testing
QA
Depth Testing
Decision table testing

48. 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
Boundary value analysis/ testing
Fault
Authorization Testing

49. 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
AUT
Decision table testing
white box testing
Interface Testing

50. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Maintenance testing
Breadth Testing
providing information - metric
Ad-hoc Testing