A blurb from my internship report
Just a portion ripped off from technical journal. For those of you interested in technical stuff, read on....
Environments
After a week of fiddling with the products, my job scope became more defined. Since I was working in the Quality Assurance (QA) Department of which my supervisor Geneva was manager of, it was only natural that I my initial responsibilities would be testing.
I learnt that for most software products, there would be at least 3 different working environments: Development where the developers / programmers continuously work on new code; QA where the testers validate the quality and functionality; and the Production, which was the live working product. All 3 were to coexists simultaneously and independently – while we the testers are testing in the QA environment, the developers could continue to write new codes and the customer beta users can continue to use the live product. When the developers had written substantially enough new code, it will be grouped together as a “build” and will be “pushed” to the QA environment, meaning the QA environment will be updated with all the latest changes from Development. Once the testers have finished testing and validated that it works, it will be “pushed” again to Production (now the live version will be updated from QA). Anytime there are major issues with a push, the build will have to be "unrolled" or reverted to an older build.
No wonder software development is so complicated :-)
Environments
After a week of fiddling with the products, my job scope became more defined. Since I was working in the Quality Assurance (QA) Department of which my supervisor Geneva was manager of, it was only natural that I my initial responsibilities would be testing.
I learnt that for most software products, there would be at least 3 different working environments: Development where the developers / programmers continuously work on new code; QA where the testers validate the quality and functionality; and the Production, which was the live working product. All 3 were to coexists simultaneously and independently – while we the testers are testing in the QA environment, the developers could continue to write new codes and the customer beta users can continue to use the live product. When the developers had written substantially enough new code, it will be grouped together as a “build” and will be “pushed” to the QA environment, meaning the QA environment will be updated with all the latest changes from Development. Once the testers have finished testing and validated that it works, it will be “pushed” again to Production (now the live version will be updated from QA). Anytime there are major issues with a push, the build will have to be "unrolled" or reverted to an older build.
No wonder software development is so complicated :-)
posted by Wayne at
4:19 PM
0 Comments:
Post a Comment
<< Home