A Continuous Integration and Deployment framework (CI/CD) allows automatic build compilations, test runs and deployments after each software check-in. A CI/CD system can be used to stage a production build, run corresponding tests and allow a check-in after all tests have run successfully. This can ensure that the Application under test is functional and meets all the requirements as incremental changes are made.
A CI/CD Framework can enable Continuous Testing for your project and move your projects to a Agile model. A CI/CD framework is highly customizable and can be setup for any type of Software Development – web, mobile apps, REST APIs, enterprise apps or embedded/IOT apps. We can customize your CI/CD solution using Jenkins, Travis, Bamboo or Gitlab CI.
Take a look at our resources section to understand basics of CI/CD and few common examples and demonstrations of a CI/CD framework.
We recommend Jenkins as it suits most customer needs and has a vibrant support community. Jenkins is completely open-source and can be setup on an intranet infrastructure or on a AWS or other cloud provider. Jenkins has plugins to talk to Github, Gitlab, JIRA and supports Pipelines to provide branch-specific versioning for CI framework itself. Jenkins also has many great plug-ins for beautiful test reporting – whether your test cases are Junit based or BDD based.
In many cases, other CI frameworks may be more efficient for your project. For example, web-apps might benefit from Travis CI or Gitlabs CI with a Docker registry deployment – this can make sure that both code and CI runs are located in the same place. Contact us to get a free evaluation on the right CI/CD setup for your organization.
Absolutely! Think about a CI/CD system as a way to run a set of commands on a group of distributed computers. If you have an embedded C++ library which uses a Makefile for build, it also be integrated into Jenkins CI system for continuous testing.
One of the main reasons for using a CI/CD system is the integrated test reports that are generated on each job run. The CI system thus allows us to view “trends” in how many test cases are passing/failing on a long term basis. View some sample reports and open-source projects that provide more information on the CI system in our resources section.
If you don’t use a CI system in your organization today – you should stop all your project work and implement a CI system today. Even a simple CI system which does builds is a tremendous time-saver for developers. We have worked on several CI framework projects and the feedback we get is always the same – this thing saves us tremendous time and has simplified our development process.
I have few anecdotal examples of past projects where we implemented CI/CD system and got feedback that it was saving them about an hour every day. The CI framework itself was implemented in maybe a week or two. Assuming these numbers – this could mean a total savings of 2080 developer hours every year. With an investment of 80 hours – this ROI turns out to be 2600%. Again, this is based on anecdotal evidence, but I feel these numbers provide a good estimate on the value a CI/CD system can bring to an organization.
Like any other system – a CI/CD system does require some upkeep. Primarily managing the various compute nodes if something goes down, keeping the CI system up-to-date with the latest test cases and reports for various features etc. But compared to the test case updates, the CI/CD framework updates are less predominant and fewer in numbers.
Whatever CI system you use – the primary functions that the CI system should provide – are the key aspects of our work. We create a robust process for managing job triggers, staging environments, test reporting, code pipelines and deployments.
Our typical hourly rates are between $60-$80 per hour. This rate depends upon the automation engineer experience, test framework language, framework complexity and whether the resource is offshore or onsite. The rates mentioned above is a average hourly rate considering all these factors.
Our goal is to make sure that you are 100% satisfied with our project delivery and will re-engage with us in future for further projects. That’s why we provide complete and immediate support after the project is complete. Our support turnaround is within 24 hours.
We also offer Managed QA Services SLA, which support not only to fix any test framework related issues – but also to keep adding new test scenarios, test cases and work on improving test automation process enhancements on a continuous basis.
Our CI/CD frameworks are usually integrated with our Test Automation Framework development packages. Based on your needs, we can design a custom CI/CD solution that can enable continuous testing for your project.
Our Team worked with the client to create a web-application and corresponding QA Automation Framework for an embedded sensors device. The web-app was developed with Angular5, HTML/BootStrap; and corresponding QA Automation Framework was developed using Python, Selenium and BDD. More.
MCN Healthcare provides medical policy management services. Our team to develop an QA automation framework for their primary product – Policy Manager. As part of this effort, we implemented an end-to-end Test Automation and a CI/CD Framework, allowing MCN to reduce QA time substantially. More.
ZFyre is a Longmont based startup providing enterprise cloud data storage solutions. Our team designed, developed and published their secure MVP app. This app included data compression using ZStd, custom security encryptions and RackSpace API integrations. This web application was developed in Angular and BootStrap on Front End. Backend was developed using NodeJS and MongoDB. More.
MVP Finance is a Longmont based startup providing educational software in Finance field to different colleges. Our team developed the entire mobile application prototype for Finance training. This project was developed with React Native Framework initially for Android platform and then extended to support iOS platform as well. More.