Utilizing ChatOps for your Automated Test Results

Lightning talk on 8/15 for the Austin Cloud meetup.

Transcript

1. Utilizing ChatOps for your Automated Test Results eniedojadlo evanniedojadlo
2. What’s our current test automation stack?
3. • Test results were scattered all over various platforms so a central location was ideal (immediate feedback across different levels of testing) • Stakeholders have access to all of the results this includes non-technical roles (we are a small company so everyone plays a part) • Having failed SauceLabs URLs in one location is easier than sifting through all tests Why did we need ChatOps?
4. Slack integration
5. Slack integration
6. • Indicates that the problem has been addressed or was due to a page timeout (we are working on improving our staging environment) • Indicates that this is a reviewed and confirmed problem and needs to be resolved (brittle test, bug, integration failure, etc.) ChatOps workflow
7. Questions? eniedojadlo evanniedojadlo