• Liked Pooja Shah
    keyboard_arrow_down

    Release Status Analyser to bring more agility @ work

    Pooja Shah
    Pooja Shah
    schedule 4 months ago
    Sold Out!
    20 mins
    Demonstration
    Advanced

    Problem Statement

    Do you have a lot of automated Tests and so the lot many tests reports to analyse before taking call for release?

    Plot: Any huge impacting micro-service based product/project for which enormous tests have been already automated and your continuous deployment process requires all of those tests in "PASSED" state. Due to high traffic most of the day, releases are deployed at non peak hours. Imagine decided deployment time in production is 5 AM. (The feature and regression testing is done already but there are always some small last minute changes, so it’s better to have a double check on the frozen code to release)

    At 1 am: Final automated sanity checks start executing  

    At 3 am: Get the results, release engineer/ devOps gets notified of the state of the release, she/he looks at CI board and see several green and red builds. He/She now 1 by 1 opens all red builds, clicks on individual reports, console, screenshots....  more red builds- more time to analyse it...

    At 4.30 am: After gathering report on which test failed for what reason & who should be looking at them, she/he calls up respective owners to look out and state the reasons & take a call on the release

    At 5 am: The service owner says "let’s revert my feature to previous version and take the release live"

    Release Engineer again starts searching for files/mails where the last stable version is stored, spending more time again. It’s 6 AM now, she/ he deploys last stable service versions, runs the failed tests -> integration tests ...

    it already 9 AM, wooosh!, time runs really fast. Can't release now, peak traffic time.............

    Do you share the same pain?

    Before giving a +1 for the release, it becomes essential for the QA folks to provide proper feedback as quickly as possible. At the same time assessing n number of reports becomes an additional tedious task. So definitely there should be 1 dashboard which nicely displays the status with transparency and anyone should be able to tell whether release is good to go and if not, then why not. RSA which I have created on top of open-sourced technologies is a small effort towards achieving the same. Will take you through a live demo and discuss on how you can use it to meet your needs.

Sorry, no proposals found under this section.