Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Testing and monitoring and broken things

22 views

Published on

There’s an old wives tale (referred to as the “Evolution of QA to GA: The Sensu Go Crucible”) that tells the story of how the Sensu engineering team redefined release engineering and quality assurance at Sensu. Failure after failure, they would gut through a far from perfect release strategy which involved hours of painstaking manual testing, in order to stamp a green checkmark of approval to ship our product. To optimize this process, they implemented a full automated test infrastructure for staging and end to end testing, which later became known as the QA Crucible . This automation pattern was (and still is) great, but Sensu Software Engineer Nikki Attea couldn’t help but wonder if there was a well-known and loved product which could decipher JSON test results and instrument them in an event pipeline. She believes Sensu can encompass monitoring _and_ testing in a CI/CD pipeline, and shows everyone how in this Sensu Summit 2019 talk.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Testing and monitoring and broken things

  1. 1. Sensu Summit 2019 Nikki Attea Software Engineer Sensu Inc. Testing and monitoring and broken things
  2. 2. Hi, I’m Nikki. - 🏐🏖 - 🍷🍺 - 🐶🐶 nikki.dev @nikkixdev
  3. 3. nikki.dev @nikkixdev
  4. 4. nikki.dev @nikkixdev #1: Eliminate bias by adding instruction. #2: Define acceptance criteria. #3: Automate, but don’t over-automate. #4: Implement test case management. #5: Hire employees with diverse experience.
  5. 5. nikki.dev @nikkixdev
  6. 6. nikki.dev @nikkixdev
  7. 7. nikki.dev @nikkixdev TESTING, MONITORING, -NIKKI ATTEA
  8. 8. nikki.dev @nikkixdev Tests fail when an assertion in our code breaks.
  9. 9. Tests fail when an assertion in our code breaks. Monitoring detects and alerts us when our system breaks. nikki.dev @nikkixdev
  10. 10. nikki.dev @nikkixdev monitoring testing breakage
  11. 11. nikki.dev @nikkixdev monitoring testing breakage systems/infrastructure code/product
  12. 12. nikki.dev @nikkixdev monitoring testing breakage systems/infrastructure code/product
  13. 13. nikki.dev @nikkixdev monitoring testing breakage systems/infrastructure code/product state
  14. 14. nikki.dev @nikkixdev
  15. 15. bonsai.sensu.io/assets/nikkixdev/sensu-serverspec-events github.com/nikkixdev/sensu-serverspec-events nikki.dev @nikkixdev
  16. 16. nikki.dev @nikkixdev Stop! Demo time!
  17. 17. nikki.dev @nikkixdev What’s next?
  18. 18. nikki.dev @nikkixdev What does this mean for your workflow?
  19. 19. nikki.dev @nikkixdev What does this mean for your org?
  20. 20. nikki.dev @nikkixdev What does this mean for my org?
  21. 21. nikki.dev @nikkixdev What does this mean for CD?
  22. 22. nikki.dev @nikkixdev Fin.

×