Saturday, April 28, 2012

Testing during production deployment:

Last week we had a major production deployment for our existing website.Project team came up with an eight hour estimate whereas testing covered with 2 hours time period. So we are in a position to plan our self to complete the entire testing activities within the scheduled time period.

For this initially, we have prepared some smoke and sanity test cases for existing application and the new enhancements. Also we have included some test cases from regression test suite to this. We executed this smoke and sanity suite as part of our daily testing activities five days prior to deployment, with the intention of getting some hands on experience in execution to reduce the time period during production deployment.

After completing the successful deployment we came up with some checklists for testing the application during production deployment. They are listed below,

1) Get the test login id’s for production server
2) Ask the data team to insert some test data to the test user login or account
3) Check for the “Website Maintenance / Offline messages displayed while accessing the website at the time of        deployment
4) Execute the sanity and smoke test cases which you have prepared to ensure all the major functionalities are working fine
5) Check for any broken links
6) Check for any images missing throughout the application
7) If the website has different group of users, test by using the default user in every group
8) Ensure with the browser you are testing with the project team
9) If there are any configuration or environmental issues during deployment , convey them to the project team immediately
10) Sign off email from QA team to ensure the website is working fine after the deployment

If you want to add some more points to this post please add them in the comments section.

Also please correct me if anything wrong.

Wednesday, December 1, 2010

Quality Center (9.2)

Important notes about Quality Center (9.2):


Modules:

Releases
Requirements
Test Plan
Test Lab
Defects

Priority:

Resolve immediately,
High,
Normal,
Low.

Severity:

Critical,
High,
Medium,
Low

Status:

Assigned,
Closed,
Deferred,
Fixed,
New,
Open,
Ready for retest,
Rejected,
Reopen,
Request for deferral,
Requirement Evaluation,
Unassigned

New Defect:

Mandatory Fields while posting a defect:

Summary
Application Area,
Defect Type,
Detected in version,
Environment
Priority
Status
Customer Issue
Detected By
Detected on date
Focus Area
Reproducible
Description
Screenshot

Non Mandatory fields:

Cost estimate in dollars
Customer name
Detected in Release
Estimated fix time
Severity
Target release
Assigned to
Current production issue
Detected in cycle
Escalation
Resolved by
Target cycle


Attachment options:

File attachment
Camera capture 9snapshot)
Attach URL
Attach system info
Attach clip content

Monday, June 14, 2010

Roles of QA in Requirement Analysis Phase of SDLC

Requirement Analysis:

It is the first phase of Software Development Life Cycle and so important too, since defects can be found early through this phase.Generally it will be done by both dev team and the qa team. Both teams will analyze the requirements documents from the client.
This document will be prepared by Business Analyst who is having thorough rapport with the client regarding their requirements.

Documents

This Requirement document contains the following files,

1) Functional Specification
2) Mock ups
3) Data Layouts

Roles of QA

1) Take the FS as a baseline document and analyze each and every page of it
2) If any clarification needed on any particular functionality or any suggestions to implement the features or any logical issues, then raise a defect or clarification against the Functional Specification document
3) Track the defect or clarification raised against the FS
4) If it is addressed, check whether it is updated in the base line document
5) Check whether the updated functional specification is available for all stake holders with the latest version
6) Check whether the version history is updated with change date and the author name who made changes in the document
7) Sign off from RA phase