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 whether the system is compatible with other systems with which it should communicate.
Maintenance testing
End-to-end Testing
Compatibility Testing
Integration Testing

2. Testing using input values that should be rejected by the component or system
Basis Path Testing
Invalid testing
Arc Testing / Branch Testing
Exhaustive Testing

3. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
black box testing
Incremental testing
Breadth Testing
Development testing

4. Depends on the schedule and risk based - business impact follow the 20-80 rules
Branch coverage
stop testing timing
Design based Testing
Ad-hoc Testing

5. Determine whether a system meets some specified standard. external organization as complying with the standard
structural testing
Context Driven Testing
Gamma testing
Conformance Testing / Compliance Testing / Standards Testing

6. 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
Loop Testing
Model Based Testing
Decision table testing
Endurance Testing

7. 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
Gamma testing
Data-Driven Testing
Incremental testing
structural testing

8. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Branch testing
functional testing
Benchmark Testing
Authorization Testing

9. The testing of individual software components.
Component Testing
Boundary value analysis/ testing
Defect density
providing information Objective

10. Approach to doing something that generally give good results when applied appropriately and thoughfully
Exhaustive Testing
best practice
test coverage
Data-Driven Testing

11. Testing one particular module - functionality heavily
Gorilla Testing
architecure of SOA
Efficiency testing
Maintainability Testing / Serviceability Testing

12. 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.
Breadth Testing
Interface Testing
Arc Testing / Branch Testing
Mutation testing

13. 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).
Acceptance Testing/User Acceptance Testing
Branch testing
providing information - metric
Design based Testing

14. Kind of unit testing - internal working of software
Fault
structural testing
Acceptance criteria
black box testing

15. Testing in which test cases are designed based on variable usage within the code.
Agile Testing
Data flow Testing
Statement coverage
Acceptance Testing/User Acceptance Testing

16. 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
Interface Testing
Defect density
Equivalence Class
Bottom-up Testing

17. A test that exercises a feature of a product in full detail.
Depth Testing
SOA
Breadth Testing
Data flow Testing

18. 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
Mutation testing
quality assurance process improvement
Business process-based testing
Data flow Testing

19. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Interoperability testing
Beta Testing / Field Testing
Conversion Testing / Migration Testing
Decision table testing

20. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Agile Testing
Dynamic Testing
Load Testing
Accessibility Testing

21. Provide critical information during project
CAST
Big Bang Testing
Context Driven Testing
providing information Objective

22. This term refers to making software specifically designed for a specific locality
End-to-end Testing
Alpha Testing
Acceptance Testing/User Acceptance Testing
Localization Testing

23. Testing the changes to an operational system or the impact of a changed environment to an operational system
Conversion Testing / Migration Testing
Basis Path Testing
Maintenance testing
Data flow Testing

24. 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
software testing
Concurrency Testing
enough of testing
Decision table testing

25. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Equivalence Class
Alpha Testing
Exploratory Testing
Breadth Testing

26. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Component Testing
Monkey Testing
Quality
Load Testing

27. 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
quality assurance process improvement
Back-to-back testing
Maintenance testing
Decision testing

28. The totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs." defined by ISO 8402 1986
Bottom-up Testing
Conversion Testing / Migration Testing
Quality
Concurrency Testing

29. 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.
functional testing
Branch testing
Code coverage
Fault

30. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Fuzz Testing
Quality
Alpha Testing
Model Based Testing

31. Computer Aided Software Testing
Fault
Dependency Testing
CAST
providing information - metric

32. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Breadth Testing
enough of testing
Documentation Testing
Maintenance 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.
Keyword driven Testing
Statement coverage
Basis Path Testing
quality assurance process improvement

34. 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
white box testing
stop testing timing
SOA
Development testing

35. 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
Installation Testing
Design based Testing
black box testing
AUT

36. 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.
Gorilla Testing
Testing best practice
Defect
Efficiency testing

37. 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+.
Documentation Testing
Component Testing
N+ Testing
SOA

38. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Endurance Testing
Conformance Testing / Compliance Testing / Standards Testing
Depth Testing
white box testing

39. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
backend testing/database testing
Black Box Testing / Functional Testing
Model Based Testing
CAST

40. executing the software
Maintainability Testing / Serviceability Testing
best practice
software testing
stop testing timing

41. Test case design
backend testing/database testing
Monkey Testing
Equivalence Class
Logic coverage Testing / Logic driven Testing / Structural

42. Can't see - test the functional testing - no access to code and testing is done on UI
Invalid testing
Endurance Testing
black box testing
CAST

43. A white box testing technique that exercises program loops
Bottom-up Testing
Interoperability testing
Gamma testing
Loop Testing

44. 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.
Conformance Testing / Compliance Testing / Standards Testing
Logic coverage Testing / Logic driven Testing / Structural
Model Based Testing
Compatibility Testing

45. 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.
GUI Testing
Decision coverage
Context Driven Testing
Back-to-back testing

46. Black-box tests conducted once the software has been integrated
Data flow Testing
Development testing
Defect
High order tests

47. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Gorilla Testing
Equivalence partition Testing
Monkey Testing
Authorization Testing

48. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Ad-hoc Testing
Endurance Testing
Isolation Testing
Heuristic evaluations

49. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Exhaustive Testing
Accessibility Testing
Fuzz Testing
GUI Testing

50. A test suite that exercises the full functionality of a product but does not test features in detail
providing information - metric
GUI Testing
Accessibility Testing
Breadth Testing