Release, Build And Test Cycle ~ Tumblia Test Solution

Release

Starting from gathering the requirement followed by developing the software and testing the software for many cycles and deployed software into the production server is called as release or one release.

When to release software to the customer

When customer requested features are ready means all the modules like (A-Z).
Once the product is functionally stable (Good Quality).
Once after software is tested in testing server similar to production server.
Once after functional testing, integration testing and system testing is completes.
Once after all the end-to-end scenarios are throughly tested.
When there are no blocker / critical defects.
We can have some minor defects and these defect should not effect customer business workflow and these defect should meet acceptance limit set by the customer.
When we are about to meet deadline / release date given by the customer.

How many days will you take to test the project

Depends on complexity of the project.
Depends on size of the project (means number of modules).
Depends on number of test engineer working on the project.

Build

Developers will write the code, compile the code and compress the code into a file this compressed file is called as build. We get the build in below mentioned formats.

Note

One project can have only one release if the project is very small, short and simple.
One project can have 'N' number of release if the project is long term and complex project.
One release can consists of 'N' number of builds.

Test Cycle

Time taken to completely test 1 build or software is called as test cycle.

Test Cycle Duration

Time period to completely test 1 build or software is called test cycle duration.
Test cycle duration depends on complexity or the project.
Depends on size of the project.
Depends on number of test engineer working on the project.

Note

1 Release can consist of 'N' number of builds.
1 Release can consist of 'N' number of test cycle.
Time taken to do functional testing, integration testing and system testing will not be same.

Who will be involved in installing build or software into the testing server

Any body from testing team (Senior test engineer, junior test engineer and freshers).
Any body from development team (Senior developer, junior developer and freshers).
Release Engineer / Build Engineer.

How test engineer will be involved in installing build or software into the server

Customer will give requirement for both developer and test engineer, all developers will write the code compile the code compress the code, prepare the build and store the build in development server in zip format in the below mentioned path.

D:/ Build / B01.zip

Development lead will send a mail to test lead or test engineer stating that build B01.zip is ready for testing.

Test lead or Test engineer will connect to development server copy paste the build into testing server, unzip and install the build. If test lead installs the build then test lead will give url, user name(UN) and password(PWD) to testing team and testing team will start testing the assigned features.

How developer will install the build into testing server

D:/ Build / B01.zip

Development lead will connect to testing server(QA) copy paste the build ,unzip the build and install the build into the testing server. Development lead will send mail to test lead stating that build is installed successfully.

Test engineer will assign all the features to test engineers for testing with url, user name (UN) and password (PWD). Test engineer will first change the password and then start testing.

How Release engineer or Build engineer involved in installing build or software into testing server

Release engineer will install version control tool (GitHub) in the server and create folder in the tool this folder can be locked and released.
All developers working in different locations push the code into the folder and commit (save) the code.
Once after folder is locked release engineer will compile compress and prepare the build and release engineer will connect to testing server copy paste the build unzip and install the build and give the url, user name(UN) and password(PWD) to test lead or test engineer.

Who is Release Engineer

Release Engineer is a person who manages source code written by the developer by using version control tool (GitHub, Sun(sun version), VSS(visual source safe), CVS(concurrent versioning system)).

What is Release Engineer management or what is configuration management

The process of preparing the build, install the build into different server and uninstalling the build from different server and deploying the build into the production server this process is called release or configuration management.