Feature Requests & Ideas

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

From the results have direct CLI command available

After a deployment, when I look at a failed test.
Having a way to quickly get the CLI command to edit the specific test would help save the time going to the test to get the local edit CLI command and then going back to the results to work on fixing the test.

It could be a third option named "Copy CLI command" in the "Edit test" drop down.

The command line would contain all params to trigger the exact same test in the same branch etc etc.
This would prevent the mistake of modding Master when actually working on a branch (happens all of the time)
Having the exact CLI command would assure i'm working on the right version of the test

  • David Alexandre Belair Paulo
  • Jun 18 2020
  • For Consideration
  • Attach files
  • David Alexandre Belair Paulo commented
    19 Jun 01:34pm

    Wow thank you Michael, it's exactly what I needed !!
    I wasn't looking in the right place, a thing that important should be in the "edit test" and not hidded in the "..."

  • Michael Bartucca commented
    19 Jun 01:20pm

    Great idea and I think we might have what you're looking for already. Next to the "Edit test" dropdown there is another dropdown menu with a "CLI info" option. If you open that you'll find an "Edit the test with same configuration" CLI command that you can copy and paste into your terminal to open an edit session under the same branch, environment, credentials, and url configuration that was used for that test run. I hope this helps you achieve your desired workflow.

Copyright © 2020 mabl Inc. All rights reserved.