Continuous Integration (CI) and Continuous Deployment (CD) are software development practices that can help to detect problems early and improve productivity. In a typical CI/CD workflow, each time a developer checks in code, the project is automatically built, tested and deployed. If your project relies on APIs, or is an API itself, integrating functional API tests as part of your CI/CD workflow can insure that your web services are fully functional with your latest code push. Likewise, if your project is a web application, including browser tests as a step in your CI/CD pipeline can help to detect UI problems introduced with your last commit.
AWS CI/CD Solution: CodePipeline
We’re excited to announce that we’re integrated into the new AWS CodePipeline product which was made available to customers today at AWS Summit NYC. AWS CodePipeline is a continuous delivery service that enables you to model, visualize and automate the steps required to release your software. Customers of CodePipeline can include Runscope API tests and Ghost Inspector browser tests in their continuous delivery pipelines to catch faults and regressions early in their development processes.
With CodePipeline, you model the full release process for building your code, deploying to pre-production environments, testing your application, and releasing it to production. CodePipeline then builds, tests, and deploys your code as modeled every time there is a code change. You can integrate partner tools and your own custom systems into any stage of the release process to form an end-to-end solution. CodePipeline enables you to rapidly deliver features and updates with high quality through the automation of your build, test, and release process.
Many of you with CI/CD workflows in place have already integrated Runscope tests into their pipeline, like uShip and SendGrid. For those users looking for a CI/CD solution, CodePipeline can streamline those processes even more with direct pipeline integration of your Runscope and Ghost inspector tests.
Easy Test Integration from the AWS Console
The CodePipeline visual configuration makes it easy to visualize your build, test and deploy flow. In the screenshot above, the pipeline has three steps. In the first step (Source), the source code is obtained from an AWS S3 bucket. In the second step (API Testing), a Runscope API test is initiated. In the last step (Browser/UI Testing), a Ghost Inspector browser test runs. Adding a Runscope or Ghost Inspector test to your pipeline is as simple as few clicks.
For more information about AWS CodePipeline, click here. If you have any other questions about Runscope or Ghost Inspector, or how to integrate your tests into your CI/CD workflow, contact our support team. Check out the full announcement for more information about the integration.