srinivas.v

• Sep 16th, 2005

 

we can get the build from central repository Ex: VSS 6.0 through ur configuration manager

subha

• Sep 16th, 2005

 

in test plan we r going to have all the details about who should test which tests in a team which is given by team leader.according to that all the group will do their testing .

mchauhan

 Profile Answers by mchauhan 

• Oct 22nd, 2005

 

When Test Manager/Test planner will write it software requirement plan report that contain his test cases and type of testing etc. to be conducted on build software or following the software requirement specifications. Later tester will follows those test cases from test plan report as per as schedule and distribution mentioned in that.

By Mukesh Chauhan Bangalore

sireesha

• Dec 20th, 2005

 

actually test process starts in this manner

testinitiation------quality manager

testplanning------project manager/testlead

test design,test execution -------testing team

testreports /defetreports--------by testing team to developmentteam if any

test closer---------testlead

inthis process QM decides the project ,its required environment,softwares,hardwares,company status to make that project.

testplanning by PM desides what to test ,how to test,who to test,when to test.

from this PM conducts meeting with all decided team and informs about

the build on which testing is to be done.

Gangadhar Nidudavolu

• Dec 29th, 2005

 

In our organization we follos seperate template called QA relse notes which describes which functionality to be testded and what are known issues. This template will be released from the Dev team PL. So based on the QA release notes we start performing the functionality testing.

Thanks

Gangadhar.N

Team Lead

shravaa

 Profile Answers by shravaa 

• Jul 12th, 2007

 

When the development is done with the build, it is sent to the configuration management team which certifies the build. Post-certificaiton, the build is available for installation.

The build is never moved directly to the QA env, instead it wud be moved to a staging env where someone from the testing team does a Smoke test on it to see there arent any showshoppers and also the features mentioned in the release notes are present and accessible.

When the build passes the smoke test, the build is moved to QA servers and the whole QA team can play around and screw it up :-)

sailaja.ragampudy

• Nov 5th, 2007

 

An intimation is sent to the testing team via mail from the development team,before a build is released.

ramesh.natarajanm

 Profile Answers by ramesh.natarajanm 

• Jul 3rd, 2008

 

Hello,

1. It will be mentioned in the Testplan at the time of preparation.

2. Dev team will send the Release notes doc to Test Lead,in that doc it will be mentioned.

Ur's
Ram~

StevenPace

 Profile Answers by StevenPace 

• Jul 12th, 2008

 

correct build numbers should be built into the binary, and also appear in the documents, and they should agree.  If they do not, this is a serious problem.  You do not want to waste time reporting bugs against a build, if the build number is ambigious or unknown.
programs have a command such as    > build or the build number might appear in the help menu after the product is installed.

The external verification would be on the folder that the build appears in, on the disk, or in some other way.