Integrating testing at every step of the DevOps pipeline helps us deliver the high-quality user experience we all strive for. We refer to this practice as DevTestOps, and, in this post, I will share some improvements we've made to mabl to provide you with more control over testing your Journeys on deployment using the Deployment Events API, which we also use as part of our Codeship build process.
Having automated tests that trigger on deployment helps developers to quickly validate that new code didn't cause any regressions as it makes its way across environments such as staging and production. It also gives peace of mind to QA engineers, product managers, and other business stakeholders that any issues are proactively resolved and everything continues to operate as expected. Some issues may only become evident in a production environment, so it's great when our tests can run on every deployment.
from DZone.com Feed http://bit.ly/2GQLJV8
No comments:
Post a Comment