Saturday, December 7, 2013

Test Scenario

Test scenarios are hypothetical stories which the tester uses to predict the user behavior, problems and system complexities. Scenarios can have multiple steps whereas Test cases have Single step. Hence Test scenarios are different from test cases.

The flow of documentation is as follows:

  • Use Case can be written using Functional Specification.
  • Test Scenario document can be written using Use Case or Functional specification or wire frame.
  • Test Cases document can be written using Test Scenario or Use Cases document.


|   Introduction to Software Testing   |   Roles and Responsibilities of a Software Tester   |   What is a Test Case   |   Software Testing types and Methods   |   STLC Process   |   Hierarchy Chart   |   Differences between Desktop application testing, Client Server application testing, and Web Based application testing   |   Most Common Interview Questions   |   Resume Preparation Tips   |   SDLC Models   |   Blog Index   |   Software Testing FAQs   |

Thursday, January 31, 2013

Severity and Priority Differences

Differences between severity and priority
Differences between Severity and Priority

Whenever tester(s) report bugs to developers they assign "Severity" and "Priority" to a bug, so that developers can understand the seriousness of the bug and they can schedule bug fixes.

Severity: of a bug decides the risk factor/impact of a bug on the application tested. Severity of a bug may be classified in to different types.

 Severity Types:

1) Blocker: bug that prevents further testing or developing of software.
2) Critical: A bug that causes AUT to hang, or causes you to lose data.
3) Major: A major functionality is not working or is broken.
4) Normal: Bug that can be taken care of and it should be fixed.
5) Minor: A bug which causes loss of function, and involves an easy patch work around.
6) Trivial: A cosmetic problem, such as a typo error or UI Issue.
7) Enhancement: A Request for new functionality or suggestions.

Priority: helps in deciding the seriousness of a bug. It is the main factor which helps in scheduling bug fixes. A bug which has high severity may have low priority.

 Priority Types:

1) Blocker: the product cannot be developed further unless this bug is fixed.
2) Immediate: This bug Should be fixed ASAP or else it may ruin the
3) High: Fix it so that it should not cause shipping to be delayed.
4) Normal: Fix it immediately after all the other higher priority bugs are done.
5) Low: Fix it so that the product is perfect and finished properly.


Monday, January 28, 2013

Desktop, Client Server, and Web Applications

What is the difference between Desktop application testing, Client Server application testing, and Web Based application testing?

In Desktop application testing application runs on personal computers or work stations and main focus is on a particular OS / environment. In this test approach application is altogether tested on sections like functionality, GUI, Load, Performance and back-end.

In client server application asymmetrical components have to be tested. Application itself is loaded on a single server machine whereas the application ".exe" is installed on every client machine. In Client Server application based testing, testers usually have to test on classifications like, GUI on both the sides, functionality, client - server integration, back-end, Load and performance. This environment is generally used in intranet networks.

Web based application is quite different and complicated to test as testers won't be having control over the application. Application is loaded on a web server whose location may or may not be known and no exe is installed on the client machine. Tests are carried out on different web browsers and OS platforms. In brief, web application is mainly tested on categories like browser compatibility and operating system compatibility, error handling, functionality, static pages, links, risk factors, back-end testing and load testing.


Google Search