Results 1 to 3 of 3

Thread: Deploying code into QA

  1. #1
    Junior Member
    Join Date
    Sep 2007
    Answers
    2

    Deploying code into QA

    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?


  2. #2
    Expert Member
    Join Date
    Oct 2007
    Answers
    375

    Re: Deploying code into QA

    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


  3. #3
    Junior Member
    Join Date
    Sep 2007
    Answers
    2

    Thumbs up Re: Deploying code into QA

    Thank You.....your post was of great help.

    Quote Originally Posted by bizzzzzare View Post
    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



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact