QASource Newsletter

QASource Blog Autocast: Summer 2017

Autocast: Summer 2017

Latest news on software tools and technologies from the Experts!

Updates

Autocast: Summer 2017
  • Selenium v3.4.0 has been released with a new Interactions framework for creating advanced user interactions in .NET bindings. View More

  • TestComplete has added Java 9 and JavaFX 9 support in its latest version 12.31. View More

  • An inbuilt test data generator utility has been released by UFT in its latest version 14. View More

  • Maven 3.5.0 has been released, with changes like more interactive console logs, no need to set JAVA_HOME and many more. View More

  • Now, you can trigger Jenkins builds on Git push or merge events using new 'Coding Webhook' plugin. View More

 

Continuous Integration/Delivery/Deployment

Faster time to market and increased focus on quality, are the 2 major keys which can make any software development organization successful in today's competitive world and now, to support these standards most of the organizations are heading towards the implementation of CI/CD process in their SDLC. This brings the need to understand Continuous Integration, Delivery & Deployment and the benefits of implementing these processes.

So, here is the brief description of these terms:

 
Continuous Integration
This part is mainly related to the development team. This is a process of continuous merging of new code pushed by developers, into the main/master branch of the product. During CI, whenever code is pushed by developers to version control, it is automatically unit tested and once all the unit tests pass, the code gets merged in master branch.
Continuous Delivery
This is the extension of Continuous Integration. In this process, once the developer's code is merged in the main/master branch, a new build is created with the latest code of main branch and deployed on staging/testing environment for the automation testing. Once the build is deployed, automated tests (Web/API/Mobile) are triggered. After the execution of automated tests is complete, the results are published for all the stake-holders.
Continuous Deployment
This is the last stage of CI/CD process, in which if a build passes in the lower environment (QA/Staging), then it is promoted and automatically deployed to higher environment (Staging/Production).

Benefits of implementing CI/CD

  • No manual intervention for build deployment and acceptance
  • Increased confidence in Production readiness
  • Less post-deployment issues due to continuous & reliable automated tests at early stages
  • Immediate feedback to developers
  • Enhanced productivity
  • Faster time to market with continuous testing
  • Increased collaboration within engineering teams with a unified pipeline

High-level workflow of CI/CD implemented in QASource

High-level workflow of CI/CD implemented in QASource
Reliability Monitor

Have Suggestions?

We would love to hear your feedback, questions, comments and suggestions. This will help us to make us better and more useful next time.
Share your thoughts and ideas at knowledgecenter@qasource.com

Disclaimer

The information contained in this newsletter is for general information purposes only. All the information have been collected from blogs, tools' websites, forums, through our research etc. and we have made utmost effort to keep the information up to date and relevant.

New Call-to-action

Written by QA Experts

QASource Blog, for executives and engineers, shares QA strategies, methodologies, and new ideas to inform and help effectively deliver quality products, websites, and applications.

Contact Us

Authors

Our bloggers are the test management experts at QASource. They are executives, QA managers, team leads, and testing practitioners. Their combined experience exceeds 100 years and they know how to optimize QA efforts in a variety of industries, domains, tools, and technologies.