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. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Fuzz Testing
Conversion Testing / Migration Testing
white box testing
Logic coverage Testing / Logic driven Testing / Structural

2. 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
organisation structure
Incremental testing
Equivalence Class
Documentation Testing

3. Root cause analyst - base of the problem - customer satisfaction report
Agile Testing
High order tests
quality assurance process improvement
Documentation Testing

4. A white box test design technique in which test cases are designed to execute branches.
Bottom-up Testing
enough of testing
Branch testing
Ad-hoc Testing

5. 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+.
Isolation Testing
N+ Testing
Model Based Testing
Compatibility Testing

6. 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
Mutation testing
Exhaustive Testing
Development testing

7. 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
Incremental testing
structural testing
N+ Testing
Concurrency Testing

8. Testing which covers all combinations of input values and preconditions for an element of the software under test
Monkey Testing
Fuzz Testing
Decision coverage
Exhaustive Testing

9. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Breadth Testing
Isolation Testing
Defect density
Data flow Testing

10. Testing whether the system is compatible with other systems with which it should communicate.
Alpha Testing
Compatibility Testing
Decision coverage
Isolation Testing

11. The expected results or performance characteristics that define whether the test cases passed or failed
N+ Testing
SOA
Defect density
Acceptance criteria

12. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Boundary value analysis/ testing
Equivalence Partitioning
Equivalence Class
Maintainability Testing / Serviceability Testing

13. Computer Aided Software Testing
Component Testing
SOA
CAST
Data flow Testing

14. 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
Maintenance testing
Black Box Testing / Functional Testing
architecure of SOA
Heuristic evaluations

15. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Branch testing
Endurance Testing
Alpha Testing
providing information Objective

16. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Business process-based testing
Decision table testing
Conversion Testing / Migration Testing
Dependency Testing

17. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Equivalence Class
enough of testing
Dynamic Testing
Code coverage

18. Testing using input values that should be rejected by the component or system
AUT
Invalid testing
Equivalence Class
Breadth Testing

19. The percentage of executable statements that have been exercised by a test suite.
Heuristic evaluations
Statement coverage
High order tests
Equivalence partition Testing

20. 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.
enough of testing
Fault
Dynamic Testing
Authorization Testing

21. The percentage of decision outcomes that have been exercised by a test suite.
Dynamic Testing
Decision coverage
Business process-based testing
Branch

22. Testing one particular module - functionality heavily
Beta Testing / Field Testing
Business process-based testing
Loop Testing
Gorilla Testing

23. 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).
Maintainability Testing / Serviceability Testing
Boundary value analysis/ testing
Quality
Design based Testing

24. Testing whether the system meets its specified objectives for maintainability.
Decision table testing
Maintainability Testing / Serviceability Testing
Back-to-back testing
Interoperability testing

25. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
SOA
Acceptance criteria
Maintainability Testing / Serviceability Testing
Equivalence partition Testing

26. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Statement coverage
Gamma testing
N+ Testing
Bugs

27. 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
Decision table testing
Equivalence partition Testing
quality assurance process improvement
Testing best practice

28. Testing software through executing it.
Invalid testing
Context Driven Testing
Dynamic Testing
Dependency Testing

29. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
white box testing
Model Based Testing
Bottom-up Testing
Grey Box Testing

30. Testing concerned with the accuracy of documentation.
Component Testing
Decision condition testing
Installation Testing
Documentation Testing

31. The process of testing to determine the interoperability of a software product
providing information Objective
Loop Testing
Alpha Testing
Interoperability testing

32. executing the software
software testing
Bugs
Boundary value analysis/ testing
Incremental testing

33. 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
Decision condition testing
organisation structure

34. 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.
Invalid testing
Loop Testing
Boundary value analysis/ testing
providing information - metric

35. 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.
Fuzz Testing
Code coverage
Quality
Basis Path Testing

36. Kind of unit testing - internal working of software
structural testing
Fault
Concurrency Testing
Beta Testing / Field Testing

37. Provide critical information during project
Decision coverage
providing information Objective
Heuristic evaluations
black box testing

38. 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
Isolation Testing
Monkey Testing
Data-Driven Testing
SOA

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

40. 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
Isolation Testing
SOA
N+ Testing
Acceptance Testing/User Acceptance Testing

41. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.
Statement coverage
Fuzz Testing
backend testing/database testing
providing information - metric

42. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Data flow Testing
Basis Path Testing
Invalid testing
Installation Testing

43. 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
Coverage Testing
Invalid testing
Quality
Decision testing

44. 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
Defect density
stop testing timing
Bottom-up Testing
Mutation testing

45. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
backend testing/database testing
best practice
Gorilla Testing
Heuristic evaluations

46. 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
best practice
architecure of SOA
Beta Testing / Field Testing
Data flow Testing

47. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Monkey Testing
Development testing
Back-to-back testing
architecure of SOA

48. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
Maintainability Testing / Serviceability Testing
stop testing timing
Depth Testing

49. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Decision table testing
Ad-hoc Testing
Endurance Testing
Decision testing

50. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
CAST
Conformance Testing / Compliance Testing / Standards Testing
Big Bang Testing
black box testing