Skip to main content

Continuous Integration vs Version Control

Most of new techies have a doubt on What is Continuous Integration? and What is Version Control? What's the relation between them? 
I want to explore and discuss something about this topic here.


Actually Continuous Integration(CI) is more than Version Control (VC). Version control is simply for maintaining different version of docs or files while users committing changes to common repository. But CI is far more than that. CI is fully related to automation  o application build and deployment activities.


Continuous Integration:
CI is a system which is used t automate our building and deployment process. At any time, the executable are ready (to test or to production) with workable condition. It includes,

1. Maintain a code repository
Common shared repository to maintain code. Actually its Version Control system.


2. Automate the build
Using available code in common repository, system will do building process to generate executable. This building process will be done automatically.


3. Make the build self-testing
While doing building process, system itself will check for errors and warnings in build process.


4. Everyone commits to the baseline every day
All available stakeholders will commit their part of code changes every day or as soon as possible after doing changes so that it will not affect the full application. Also if your changes are conflict with repository copy, then it wont allow you to commit unless you get latest, do changes and commit.


5. Every commit (to baseline) should be built
For each and every committing done by users, the build process will be triggered.


6. Keep the build fast
Building process will be fast enough as every day code changes are committed and no major changes will not be there. This will avoid unnecessary ambiguities in code.

7. Test in a clone of the production environment
As we have working software deliverable ready all the times, we can test using the clone of latest executable. This will ensure quality confidence on changes made in new build.


8. Everyone can see the results of the latest build
Everyone can know the status of latest build. If any errors or warnings while building, system will report the errors to all stake holders.


9. Automate Installation / Deployment
As we have latest build for each day, we can automate the deploying processes. This will ensure the latest application build is up for testing on each day.


Version Control:
VC is a system which provides a shared repository to your code and maintains the changes by keeping the different version of file.


CruiseControl, Hudson, teamcity, Bamboo, etc. are CI tools.
SVN, Visual SourceSafe, Git, etc are Version Control tools.
Maven, ant are build tools.


Hope this will you some ideas about CI and VC.

Comments

  1. Thanks for sharing great information in your blog. Got to learn new things from your Blog . It was very nice blog to learn about Selenium

    ReplyDelete

Post a Comment

Popular posts from this blog

QTP - Object Identification - Prerequesties

While starting a new project or proof of concept or after new QTP installation, we would face the issue in identifying objects as QTP built objects like WinList, WebEdit, etc.; instead everything will be identified as WinObject.

Here are some steps to ensure you did the environment setup RIGHT before start automating.
Did you enabled required Add-ins only while launchingDid you selected "Record >> Record and Run Settings" - This should be based on what type of application you are working with
Windows app - Windows >> Record and run test on any windows applications. Web app - Web >> Record and run test on any open browser.
Did you tried to launch UFT/QTP and then AUT.If its web, ensure browser zoom level set to 100%Try disabling the protected mode in IE for web.Launch UFT and AUT using RUN AS ADMINISTRATORAlso see the Object Identification Methods if you are interested.

Change IE Browser ZOOM settings

Lot of UI automation testers could have faced this problem as we could change the zoom settings while operating manually for our convenience and forgot to reset to 100%.
But our QTP and some other related tools would operate the browser perfectly if browser zoom is 100%. So wee need to change the zoom before start to run the scripts. Its better to have a code snippet in our framework to change this zoom setting right?
Here we go...

1. We can simply change the Registry values before Invoking IE
Function ChangeRegistry Dim objShell Set objShell = CreateObject("WScript.Shell")  objShell.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Zoom\ZoomFactor", "100000", "REG_DWORD" Set objShell = Nothing EndFunction This option is very useful. But in real time, lot of customers could have restricted write access to windows registry. So we can try other options.

2. Use IE COM object and Change Settings
Function ChangeIEZoom Dim intZoomLevel, objIE  intZoo…

QTP - Common error messages

Always I am seeing  many of my friends asking for help if any error occurs while running script in QTP without googling for help. How much troubleshooting you guys are doing will directly reflect your knowledge on the tool. I agree, no one knows each and every error occurs in the software. But we can improve our knowledge by googling and doing workarounds...
Whenever the question "How much level you know QTP?" arrows me, always I am comfortable with the answer "below 10%". But after answered, my mind will have an inner thought like, What are the things I have to learn to fulfill the answer I have told because I never used lot of features in QTP.

Here I am listing out some of the errors, situations and what might be the original issue things etc. I hope this will give you some ideas to improve your debug ability and to solve your errors. Kindly correct me If I am wrong in any point.

Type mismatch:
- Mostly doing operations with different data types without doing type co…