Monday, March 29, 2010

Test scenarios for testing a web site

As a Tester you should test GUI of the website,test whether the page layout and design elements are consistent through out the site,Whether all the links provided in the website are working properly,What are the expected loads on the server? performance of the website (check for webserver response time and database query time)under heavy loads.

The key things are:
1. UI testing
2. Session
3. Basic functionality
4. Negative testing
5. Penetration testing
5. Broken links
6. URL testing
7. Orphan page testing

TESTCASE :
. A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly.At this stage, the Tester has clarity on how the application is to be tested. It now, becomes necessary to aid the actual test action with test cases. Test cases are written based on the test conditions. It is the phrased form of test conditions, which becomes readable and understandable by all.

A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results.

Description: Here the details of the test on a specification or condition are written

Data and Pre-requirements: Here either the data for the test or specification is mentioned. Pre-requirements for the test to be executed should also be clearly mentioned.

Expected Results: The expected result on execution of the instruction in the description is mentioned. In general, it should reflect, in detail the result of the test execution.

Example
Description: Click on the hyperlink 'New Deposit' at the top left hand corner of the Main
Menu Screen
Expected Result: New Time deposit Screen should be displayed .Customer contact date should be prefilled with the system date

Pre-Requirements
Test cases cannot generally be executed with normal state of the application. Below is a list of possible pre-requirements that could be attached to the test case:

1. Enable or disable external interfaces
Example,
Reuters, a Foreign exchange rate information service organization server to be connected
to the application

Data definition
Data for executing the test cases should be clearly defined in the test cases. They should indicate the values that will be entered into the fields and also indicate the default values of the field.
Example:
Description: Enter client's name
Data: John Smith

(Note that the process of developing test cases can help find problems in the requirements or design of an application, since it requires completely thinking through the operation of the application. For this reason, it's useful to prepare test cases early in the development cycle if possible. )

What is Bug : If the sofware does not meet the below criteria then it is bug.

  1. Any thing which is not defined by the client
  2. If Excess Things are added in the software
  3. software does not produce a expected result
  4. it is not userfriendly

What is the diffence between bug and error:
Error is a programitical mistake , if the function is not responding with expected result then it is error,Bug is any thing which is not added or excess added in to software or it is functionally not well defined and it is not a user friendly software.Then errors are also comes under bug.

Life cycle of a defect is explained diagrammatically below:

1. New:When bug raises then it is in the New State.
2.Open : Developer Check the Bug Then it is in the Open state
3.Fixed : Developer Fixes the Bug , Then State is Fixed
4 Close :Tester Checks again ,if bug is not raised then it is Closed State.
5.Reopen: Again It is raised then it is in Reopen State.

No comments: