What do you mean by Deploying code into QA and out to productions using Bladelogic, Site Server, and Putty?
Deploying a code, is it related to White box testing or comes under black box testing?
Printable View
What do you mean by Deploying code into QA and out to productions using Bladelogic, Site Server, and Putty?
Deploying a code, is it related to White box testing or comes under black box testing?
Hi,
Generally every system would have 3 teams - Development Team, Testing team and a Production Support Team.
A development team generally works on a Development build. Based on the SRS and FRS, a system is developed. Once development is complete, the build is given a Build number and this is deployed or released to QA team for testing.
This procedure of deploying the code into the QA environment is called as Deploying code to QA. Incase we are specifically keen on looking into the procedure of the code being deployed, we are covering a part of White Box testing. Else Code deployment is a seperate activity which would not fall under Black / White Box testing.
Once testing is complete and a Release note certifying testing completion is sent out by the QA team, the tested build is then deployed to Production. This could be achieved using SiteServer or Putty. Once it is into Production, we call it also as "Going Live". The product is in actual use at the Customer end.
Generally there is also a team which takes care of this Build preparation and Deployment activites. It is called as Build and Deployment activity team.
Cheers.
Bizzzzzare
Thank You.....your post was of great help.
[QUOTE=bizzzzzare;21049]Hi,
Generally every system would have 3 teams - Development Team, Testing team and a Production Support Team.
A development team generally works on a Development build. Based on the SRS and FRS, a system is developed. Once development is complete, the build is given a Build number and this is deployed or released to QA team for testing.
This procedure of deploying the code into the QA environment is called as Deploying code to QA. Incase we are specifically keen on looking into the procedure of the code being deployed, we are covering a part of White Box testing. Else Code deployment is a seperate activity which would not fall under Black / White Box testing.
Once testing is complete and a Release note certifying testing completion is sent out by the QA team, the tested build is then deployed to Production. This could be achieved using SiteServer or Putty. Once it is into Production, we call it also as "Going Live". The product is in actual use at the Customer end.
Generally there is also a team which takes care of this Build preparation and Deployment activites. It is called as Build and Deployment activity team.
Cheers.
Bizzzzzare[/QUOTE]