1. Continuous Integration
Abstract
Continuous Integration is a software development practice where members of a team
integrate their work frequently; usually each person integrates at least daily – leading to
multiple integrations per day. Each integration is verified by an automated build
(including test) to detect integration errors as quickly as possible.
Overview
At Valsatech Continuous integration is an integral part of octopus framework. It adheres
to the agile as well as waterfall methodology and practices.
What is Continuous Integration?
CI is the practice of merging all developer workspaces several times a day with a shared
mainline. When developers check their code into the mainline, or trunk, the code is
automatically compiled and then automated unit tests are run to provide quality control.
In the same vein, the practice of Continuous Delivery further extends CI by making sure
the software checked in on the mainline is always in a state that can be deployed to users
and is enabled for rapid deployment.

2. Advantage
• Improve Quality of Software: CI helps you improve the quality of your software. It
provides a shorter feedback loop on the quality of the slimmer build, therefore reducing
the risk associated with the newly integrated code.
• Discover Integration issues: CI can discover integration issues earlier and isolate and
resolve defects faster.
• Early detection of Schema or Code changes: Integrating with automated build system
continuous Integration can help validate any schema or code changes early in the testing
process.
• Automated deployment: Automated Deployment is the process of consistently pushing
a product to various environments on a “trigger.” It enables you to quickly learn what to
expect every time you deploy an environment with much faster results. This combined
with Build Automation can save development teams a significant amount of hours.
CI Process and Offering at Valsatech
Continuous Integration
Abstract
Continuous Integration is a software development practice where members of a team
integrate their work frequently; usually each person integrates at least daily – leading to
multiple integrations per day. Each integration is verified by an automated build
(including test) to detect integration errors as quickly as possible.
Overview
At Valsatech Continuous integration is an integral part of octopus framework. It adheres
to the agile as well as waterfall methodology and practices.
What is Continuous Integration?

3. CI is the practice of merging all developer workspaces several times a day with a shared
mainline. When developers check their code into the mainline, or trunk, the code is
automatically compiled and then automated unit tests are run to provide quality control.
In the same vein, the practice of Continuous Delivery further extends CI by making sure
the software checked in on the mainline is always in a state that can be deployed to users
and is enabled for rapid deployment.
Advantage
• Improve Quality of Software: CI helps you improve the quality of your software. It
provides a shorter feedback loop on the quality of the slimmer build, therefore reducing
the risk associated with the newly integrated code.
• Discover Integration issues: CI can discover integration issues earlier and isolate and
resolve defects faster.
• Early detection of Schema or Code changes: Integrating with automated build system
continuous Integration can help validate any schema or code changes early in the testing
process.
• Automated deployment: Automated Deployment is the process of consistently pushing
a product to various environments on a “trigger.” It enables you to quickly learn what to
expect every time you deploy an environment with much faster results. This combined
with Build Automation can save development teams a significant amount of hours.
CI Process and Offering at Valsatech
The CI system at Valsatech is built from Jenkins and it is run in apache container/server.
The test beds are added as slaves called nodes in the Jenkins and there is a Master Slave
relationship between the Jenkins and Test beds.
The CI system can be used for end-to-end Integration testing and unit level automation
testing
Following are few salient features:
1. Ability to cover all the layers and aspects of the AUT: Using Octopus automation
framework Valsatech provides a solution that can test both the GUI layer and the
services/API layer in a single test for web applications, native applications or mobile
applications.
2. Comprehensive Reporting System: Test Results are published in the comprehensive
reports which get archived against the build number the test results executed on using the

4. CI system.
3. Multithreaded Test execution always with latest code: The tests are executed
simultaneously on multiple test beds in a multithreaded environment every time with an
updated code from the subversion system.
4. Zero down time CI Automation system: A pool of test beds to support multiple
execution requests with zero downtime.
5. Automatic test environment creation: automatically simulate the production
environment on the multiple test beds and execute the BATS (basic acceptance tests) to
verify a build for any changes.