Feature Requests & Ideas

For bug reports and questions, please use the in-app chat or support@mabl.com.

Journeys - Provide failure reason as comment

When running my plans sometimes a journey fails and I will look through the output to discover why it failed. However if someone else on my team also wanted to figure out why they'd have to do the same, wasting the same time. (Plus sometimes the same person has to look again because they can't remember why every journey fails)

 

Instead I'd like the ability to add a comment to a journey when it fails, giving a reason to it's failure. Here I could mention why it failed or if I've raised a bug for it with the bug ID etc. Anyone else who wanted to know the reason for failure could then easily understand from the comment left. This comment would also show next to the journey on the plan history section.

  • Harry Wigman
  • May 16 2019
  • Shipped
  • Dec 11, 2020

    Admin response

    You and your team can now add comments to test failures so that you can keep everyone in the know and work together on debugging issues. You can also use the comments to add links to related tests, Pull Requests, or Jira tickets. Release notes.

  • Attach files
  • David Alexandre Belair Paulo commented
    23 Oct, 2020 02:34pm

    A comment field would also be important for us.

    Then a plan fails, it takes a moment to analyse and understand, it's important to be able to document the situation more than with only a category, it will save time to anybody who visits the failed run and needs to understand that fail too.

  • Anton Hristov commented
    23 Jan, 2020 07:29pm

    There's now an option to classify test (former journey) failures based on several predefined categories (learn more). We will consider adding an option for comments and update this request accordingly.  

  • +4
Copyright © 2021 mabl Inc. All rights reserved.