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. 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).
Black Box Testing / Functional Testing
Acceptance Testing/User Acceptance Testing
Design based Testing
Integration Testing

2. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Invalid testing
GUI Testing
quality assurance process improvement
Alpha Testing

3. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
Acceptance criteria
backend testing/database testing
Development testing

4. 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
Decision condition testing
Coverage Testing
Context Driven Testing

5. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Testing best practice
Decision condition testing
End-to-end Testing
Dependency Testing

6. 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+.
Monkey Testing
QA
N+ Testing
Conformance Testing / Compliance Testing / Standards Testing

7. Testing whether the system is compatible with other systems with which it should communicate.
exploratory testing
architecure of SOA
Integration Testing
Compatibility Testing

8. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Maintainability Testing / Serviceability Testing
Big Bang Testing
Efficiency testing
Equivalence Partitioning

9. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Testing best practice
Dependency Testing
Accessibility Testing
enough of testing

10. 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.
Model Based Testing
Authorization Testing
Gorilla Testing
quality assurance process improvement

11. Similar to black box testing - structure of test cases in order to find defects and its strutured
functional testing
Defect
Breadth Testing
CAST

12. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
QA
Defect
Development testing
Data-Driven Testing

13. 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 - metric
Monkey Testing
Maintainability Testing / Serviceability Testing
High order tests

14. Kind of unit testing - internal working of software
Interoperability testing
Acceptance criteria
Equivalence partition Testing
structural testing

15. 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.
Code coverage
Black Box Testing / Functional Testing
Decision testing
functional testing

16. Can't see - test the functional testing - no access to code and testing is done on UI
Gorilla Testing
Business process-based testing
Black Box Testing / Functional Testing
black box testing

17. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Localization Testing
backend testing/database testing
QA
Interface Testing

18. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Fuzz Testing
white box testing
Interface Testing
Incremental testing

19. 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
white box testing
test coverage
Data-Driven Testing
Branch

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.
Fault
Conformance Testing / Compliance Testing / Standards Testing
Breadth Testing
Equivalence Partitioning

21. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Decision condition testing
Beta Testing / Field Testing
Design based Testing
Depth Testing

22. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Exploratory Testing
Grey Box Testing
Accessibility Testing
Black Box Testing / Functional Testing

23. Testing using input values that should be rejected by the component or system
Fuzz Testing
Invalid testing
Quality
exploratory testing

24. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
GUI Testing
Heuristic evaluations
Component Testing
Bugs

25. 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
Fault
Defect density
Mutation testing
Quality

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
End-to-end Testing
Branch
Isolation Testing
quality assurance process improvement

27. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
Acceptance Testing/User Acceptance Testing
enough of testing
Depth Testing

28. 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.
Boundary value analysis/ testing
Back-to-back testing
Quality
Exhaustive Testing

29. The process of testing to determine the efficiency of a software product
organisation structure
Exploratory Testing
Branch testing
Efficiency testing

30. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Grey Box Testing
Benchmark Testing
providing information Objective
Code coverage

31. Root cause analyst - base of the problem - customer satisfaction report
Fault
quality assurance process improvement
Dynamic Testing
Dependency Testing

32. Checks for memory leaks or other problems that may occur with prolonged execution
Endurance Testing
Localization Testing
Quality
enough of testing

33. 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.
enough of testing
Compatibility Testing
Arc Testing / Branch Testing
Decision table testing

34. 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
providing information Objective
Big Bang Testing
Integration Testing
Dynamic Testing

35. It is a whole - is the whole process form review to plans strategy and whole thing
Dependency Testing
Load Testing
QA
Decision table testing

36. The expected results or performance characteristics that define whether the test cases passed or failed
enough of testing
Acceptance criteria
stop testing timing
Benchmark Testing

37. 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 condition testing
Model Based Testing
Logic coverage Testing / Logic driven Testing / Structural
Concurrency Testing

38. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Fault
Business process-based testing
Depth Testing
End-to-end Testing

39. 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
Basis Path Testing
N+ Testing
Endurance Testing

40. 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.
Branch testing
Business process-based testing
Defect
providing information Objective

41. 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
Arc Testing / Branch Testing
Decision table testing
best practice
backend testing/database testing

42. This term refers to making software specifically designed for a specific locality
Localization Testing
structural testing
Black Box Testing / Functional Testing
Monkey Testing

43. 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
Incremental testing
Mutation testing
End-to-end Testing
Keyword driven Testing

44. executing the software
software testing
AUT
Basis Path Testing
Breadth Testing

45. 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
Concurrency Testing
black box testing
AUT
Load Testing

46. 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.
Data flow Testing
Integration Testing
Business process-based testing
Keyword driven Testing

47. Provide critical information during project
providing information Objective
Conversion Testing / Migration Testing
Decision testing
Dependency Testing

48. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Branch coverage
Ad-hoc Testing
Documentation Testing
Benchmark Testing

49. Testing whether the system meets its specified objectives for maintainability.
Statement coverage
Depth Testing
Maintainability Testing / Serviceability Testing
Decision testing

50. Approach to doing something that generally give good results when applied appropriately and thoughfully
Acceptance criteria
white box testing
best practice
structural testing