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 which covers all combinations of input values and preconditions for an element of the software under test
Exhaustive Testing
End-to-end Testing
Invalid testing
Decision condition testing

2. Provide critical information during project
Invalid testing
providing information Objective
Endurance Testing
Dynamic Testing

3. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
GUI Testing
Installation Testing
Concurrency Testing

4. 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.
white box testing
Monkey Testing
Integration Testing
Context Driven Testing

5. The expected results or performance characteristics that define whether the test cases passed or failed
Efficiency testing
black box testing
Heuristic evaluations
Acceptance criteria

6. This term refers to making software specifically designed for a specific locality
Localization Testing
Authorization Testing
Exploratory Testing
Fault

7. It is a whole - is the whole process form review to plans strategy and whole thing
QA
Exploratory Testing
Integration Testing
GUI Testing

8. 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.
Grey Box Testing
architecure of SOA
Benchmark Testing
Code coverage

9. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
structural testing
functional testing
Big Bang Testing
Context Driven Testing

10. 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.
Defect
Acceptance Testing/User Acceptance Testing
Isolation Testing
Data flow Testing

11. The percentage of executable statements that have been exercised by a test suite.
Arc Testing / Branch Testing
Installation Testing
Statement coverage
Interoperability testing

12. 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
organisation structure
Depth Testing
Installation Testing
Integration Testing

13. 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)
test coverage
Defect density
Branch
Grey Box Testing

14. Root cause analyst - base of the problem - customer satisfaction report
stop testing timing
quality assurance process improvement
Installation Testing
Statement coverage

15. 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).
Agile Testing
best practice
Design based Testing
Big Bang Testing

16. Depends on the schedule and risk based - business impact follow the 20-80 rules
Component Testing
stop testing timing
Keyword driven Testing
Exhaustive Testing

17. 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
Grey Box Testing
Branch
Loop Testing
Logic coverage Testing / Logic driven Testing / Structural

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
Decision condition testing
Incremental testing
Concurrency Testing
Dynamic Testing

19. 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
Context Driven Testing
Heuristic evaluations
Breadth Testing
Exploratory Testing

20. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Basis Path Testing
Endurance Testing
best practice
Acceptance Testing/User Acceptance Testing

21. Approach to doing something that generally give good results when applied appropriately and thoughfully
best practice
Loop Testing
Load Testing
exploratory testing

22. 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
Maintainability Testing / Serviceability Testing
Monkey Testing
Interface Testing
Design based Testing

23. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Coverage Testing
Isolation Testing
Accessibility Testing
Dynamic Testing

24. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Decision coverage
Incremental testing
Black Box Testing / Functional Testing
Branch coverage

25. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
QA
Exploratory Testing
Gamma testing
Component Testing

26. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
backend testing/database testing
Beta Testing / Field Testing
providing information - metric

27. Testing concerned with the accuracy of documentation.
backend testing/database testing
Equivalence Partitioning
best practice
Documentation Testing

28. 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
Incremental testing
AUT
Acceptance Testing/User Acceptance Testing
organisation structure

29. Testing whether the system is compatible with other systems with which it should communicate.
Compatibility Testing
Design based Testing
Isolation Testing
backend testing/database testing

30. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Back-to-back testing
Equivalence partition Testing
Maintainability Testing / Serviceability Testing
Development testing

31. The process of testing to determine the interoperability of a software product
High order tests
Interoperability testing
Beta Testing / Field Testing
N+ Testing

32. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
N+ Testing
enough of testing
quality assurance process improvement
providing information Objective

33. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Invalid testing
Acceptance Testing/User Acceptance Testing
Dependency Testing
quality assurance process improvement

34. Kind of unit testing - internal working of software
Equivalence partition Testing
structural testing
stop testing timing
Logic coverage Testing / Logic driven Testing / Structural

35. 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+.
N+ Testing
Basis Path Testing
Branch testing
Context Driven Testing

36. 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
Mutation testing
Integration Testing
test coverage
High order tests

37. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Arc Testing / Branch Testing
Equivalence partition Testing
Alpha Testing
best practice

38. 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.
Logic coverage Testing / Logic driven Testing / Structural
Fault
Back-to-back testing
Coverage Testing

39. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Decision testing
Branch
CAST
white box testing

40. 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.
Bottom-up Testing
Authorization Testing
Accessibility Testing
organisation structure

41. Testing whether the system meets its specified objectives for maintainability.
Maintainability Testing / Serviceability Testing
exploratory testing
Invalid testing
Statement coverage

42. 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
Decision table testing
Conformance Testing / Compliance Testing / Standards Testing
Endurance Testing
Mutation testing

43. The testing of individual software components.
Gorilla Testing
Maintainability Testing / Serviceability Testing
Component Testing
Fault

44. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Interface Testing
Quality
Model Based Testing
Ad-hoc Testing

45. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Equivalence partition Testing
Decision condition testing
software testing
GUI Testing

46. A test that exercises a feature of a product in full detail.
Installation Testing
High order tests
Depth Testing
Bottom-up Testing

47. Stakeholder stakeholder satisfaction with test results report
software testing
Equivalence partition Testing
providing information - metric
Alpha Testing

48. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Maintainability Testing / Serviceability Testing
Branch testing
Invalid testing
Business process-based testing

49. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Keyword driven Testing
Equivalence partition Testing
Testing best practice
Boundary value analysis/ testing

50. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
structural testing
Black Box Testing / Functional Testing
Benchmark Testing
Equivalence Partitioning