RSS

Monthly Archives: May 2012

Weekly Status Report



Writing effective status report is as important as the actual work you did! How to write a effective status report of your weekly work at the end of each week?

Here I am going to give some tips. Weekly report is important to track the important project issues, accomplishments of the projects, pending work and milestone analysis. Even using these reports you can track the team performance to some extent. From this report prepare future actionables items according to the priorities and make the list of next weeks actionable.

So how to write weekly status report?

Follow the below template:
Prepared By:
Project:
Date of preparation:
Status:
A) Issues:

kevalshah.in

Read the rest of this entry »

Advertisements
 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Test summary Report


  1. Test summary Report Identifier

<Unique ID here for the report here>

  1. Summary

<Summarize the evaluation of the test items>

<Identify the items tested, indicating their version/revision level>

<Indicate the environment in which the testing activities took place>

<For each test item, supply references to the following documents if they exist: test plan, , test breakdown or test cases, test item transmittal reports, test logs, and test incident reports.>

  1. Variances

<Report any variances of the test items from their design specifications>

<Indicate any variances from the test plan, test breakdown or test cases>

<Specify the reason for each variance>

  1. Comprehensive Assessment

<Evaluate the comprehensiveness of the testing process against the comprehensiveness criteria specified in the Test Plan>

<Identify features or combinations that were not sufficiently tested and explain the reasons>

  1. Summary of Results

<Summarize the results of testing. Identify all resolved bugs and summarize their resolutions. Identify all unresolved bugs>

  1. Evaluation

<Provide an overall evaluation of each test item including its limitations. This evaluation shall be based upon the test results and the item level pass/fail criteria as stated in the Test Plan.>

<Include acceptable failures details; ID, Summary, Approver>

<An estimate of risk related to deploying to live may be included> Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Test Strategy


Document Detail

Title: <Formal name for the Strategy with reference to the area it covers>
Version: <Current Version>
Date: <Date of issue of current version>
Electronic File Name: <Document file name.doc>
Electronic File Location: <SharePoint URL>
Author: <Your Name>
Contributors: <Add names of anyone reviewing or providing information>

Change Control

Issue Date Version Details Author
<Issues date> v0.1d Working Draft, not yet for review <Your Name>
kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

test case format style


unique-test-case-id: Test Case Title

Purpose:

Short sentence or two about the aspect of the system is being tested. If this gets too long, break the test case up or put more information into the feature descriptions.

Prereq:

Assumptions that must be met before the test case can be run. E.g., “logged in”, “guest login allowed”, “user testuser exists”.

Test Data:

List of variables and their possible values used in the test case. You can list specific values or describe value ranges. The test case should be performed once for each combinationof values. These values are written in set notation, one per line. E.g.:loginID = {Valid loginID, invalid loginID, valid email, invalid email, empty}password = {valid, invalid, empty}

Steps:

Steps to carry out the test. See step formating rules below.

  1. visit LoginPage
  2. enter userID
  3. enter password
  4. click login
  5. see the terms of use page
  6. click agree radio button at page bottom
  7. click submit button
  8. see PersonalPage
  9. verify that welcome message is correct username

Notes and Questions:

  • NOTE
  • QUESTION
kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Minimum require to bug report


1.Bug id
2.Test case id
3.Test case name
4.Priority and severity
5.Status
6.Email of devloper
7.Attachments if any
8.Assign to(Decided by Test lead)

kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Bug report templete


Bug Template

I’m a staunch advocate of keeping a small text file template on your desktop to paste bugs into just so that you can easily fill out all pertinent information. The following is similar to the one I use, but broader so that you can alter it for your own specific project.

Server Config:

Platform: <List Windows, Unix, and so on.>

Build: <Give the build number.>

Test Bed: <Give a test bed identification or topology name.>

Client Config:

OS: <List Windows 2000, Macintosh, and so on.>

Browser: <List browser and version IE 5.5, NN 4.76, and so on.>

Description:

<Brief description of the problem, more than the title, but not too much>

kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

SQA Topics


Why SQA

There are so many reasons why a company should consider SQA. It is all about business survival and SQA is just one of the many tools the company should effectively use. And just like a tool, it has to be effectively used to its maximum. If the tool is not used to its full extent, the tool will just be a financial burden to the company. SQA should also be utilized at the same way – to its full extent.

Sponsored Links

One of the reasons why businesses and companies opt out in using SQA is their inability to realize who effective an SQA when properly used.  The following are the reasons why SQA should be used by any company before releasing their application to their intended users:

Traceability of Errors

Without using SQA, developers can still locate the errors of the application. Since their familiarity with the application is impeccable, they will have the ability to find a remedy to the problem. SQA on the other hand does not just look for answers to their problems.

SQA looks for the reason why the error occurred. Looking for errors is really easy but tracing the roots of the problem is another thing. The SQA team should be able to tell which practice has started the problem. Most of the time, the errors is not rooted on the execution of the coding but it could be found in the philosophy in developing the application.

kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

 
%d bloggers like this: