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. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Equivalence Partitioning
Decision coverage
Black Box Testing / Functional Testing
backend testing/database testing

2. Testing the changes to an operational system or the impact of a changed environment to an operational system
backend testing/database testing
Integration Testing
Agile Testing
Maintenance testing

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.
Keyword driven Testing
Testing best practice
Conformance Testing / Compliance Testing / Standards Testing
test coverage

4. This term refers to making software specifically designed for a specific locality
Localization Testing
Endurance Testing
Maintainability Testing / Serviceability Testing
architecure of SOA

5. executing the software
Defect
Gamma testing
Alpha Testing
software testing

6. Root cause analyst - base of the problem - customer satisfaction report
Compatibility Testing
Equivalence Class
quality assurance process improvement
Heuristic evaluations

7. 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.
N+ Testing
Component Testing
best practice
Bottom-up Testing

8. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)
Efficiency testing
enough of testing
Maintenance testing
Defect density

9. Similar to black box testing - structure of test cases in order to find defects and its strutured
functional testing
Statement coverage
Equivalence Partitioning
quality assurance process improvement

10. 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
Branch coverage
Component Testing
Basis Path Testing
Acceptance Testing/User Acceptance Testing

11. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Decision condition testing
Gamma testing
Maintenance testing
Black Box Testing / Functional Testing

12. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
End-to-end Testing
Back-to-back testing
Documentation Testing

13. 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
Statement coverage
CAST
Accessibility Testing
Bugs

14. Knows about the software and test - no proper plan
Basis Path Testing
Branch coverage
Decision coverage
exploratory testing

15. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
architecure of SOA
Basis Path Testing
Interface Testing
Black Box Testing / Functional Testing

16. 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+.
GUI Testing
test coverage
N+ Testing
Acceptance criteria

17. Testing concerned with the accuracy of documentation.
Branch
Conformance Testing / Compliance Testing / Standards Testing
Maintainability Testing / Serviceability Testing
Documentation Testing

18. 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
Equivalence partition Testing
Concurrency Testing
Ad-hoc Testing
Black Box Testing / Functional Testing

19. 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
Data-Driven Testing
Acceptance Testing/User Acceptance Testing
Coverage Testing
Efficiency testing

20. Determine whether a system meets some specified standard. external organization as complying with the standard
Equivalence Partitioning
Conformance Testing / Compliance Testing / Standards Testing
Accessibility Testing
Branch coverage

21. Checks for memory leaks or other problems that may occur with prolonged execution
Depth Testing
Breadth Testing
SOA
Endurance Testing

22. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Efficiency testing
Keyword driven Testing
Testing best practice
High order tests

23. A white box testing technique that exercises program loops
Development testing
Loop Testing
Load Testing
Branch testing

24. The testing of individual software components.
structural testing
organisation structure
Component Testing
Dependency Testing

25. 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.
Maintainability Testing / Serviceability Testing
Code coverage
architecure of SOA
stop testing timing

26. 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
Ad-hoc Testing
Equivalence Class
Mutation testing
Beta Testing / Field Testing

27. 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
Branch
Back-to-back testing
Mutation testing
Model Based Testing

28. The percentage of decision outcomes that have been exercised by a test suite.
CAST
Decision coverage
providing information - metric
Acceptance Testing/User Acceptance Testing

29. 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
Maintainability Testing / Serviceability Testing
Back-to-back testing
Data-Driven Testing
black box testing

30. 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.
Ad-hoc Testing
structural testing
Fault
Bottom-up Testing

31. 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).
Heuristic evaluations
Monkey Testing
Design based Testing
Acceptance criteria

32. The process of testing to determine the efficiency of a software product
Equivalence Partitioning
Design based Testing
Branch testing
Efficiency testing

33. 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
providing information Objective
organisation structure
functional testing
Monkey Testing

34. 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
Back-to-back testing
Exhaustive Testing
Branch
software testing

35. 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
Heuristic evaluations
Efficiency testing
Arc Testing / Branch Testing
Monkey Testing

36. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Model Based Testing
best practice
Equivalence partition Testing
black box testing

37. 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
High order tests
Localization Testing
stop testing timing
Back-to-back testing

38. A test suite that exercises the full functionality of a product but does not test features in detail
Basis Path Testing
Breadth Testing
exploratory testing
Coverage Testing

39. Computer Aided Software Testing
Fault
Loop Testing
CAST
Mutation testing

40. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Exploratory Testing
Data flow Testing
Dependency Testing
Endurance Testing

41. 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
Boundary value analysis/ testing
SOA
Maintainability Testing / Serviceability Testing
Business process-based testing

42. Black-box tests conducted once the software has been integrated
organisation structure
High order tests
Incremental testing
enough of testing

43. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Quality
Breadth Testing
Development testing
Arc Testing / Branch Testing

44. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Branch coverage
SOA
Development testing
Load Testing

45. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
best practice
CAST
Big Bang Testing
Component Testing

46. 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.
Development testing
CAST
Authorization Testing
Branch coverage

47. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Mutation testing
white box testing
Coverage Testing
providing information Objective

48. 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.
Arc Testing / Branch Testing
Benchmark Testing
Context Driven Testing
Keyword driven Testing

49. 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
exploratory testing
AUT
black box testing
Black Box Testing / Functional Testing

50. 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.
Model Based Testing
High order tests
stop testing timing
Exploratory Testing