mablhq / github-run-tests-action Goto Github PK

Hi,

After a successful execution of a plan with 6 journeys running on two browsers(chrome, firefox). the results include the following details

##[set-output name=plans_run;]1
##[set-output name=plans_passed;]1
##[set-output name=plans_failed;]0
**##[set-output name=journeys_run;]1
##[set-output name=journeys_passed;]1**
##[set-output name=journeys_failed;]0

This should be either 12 (including the total number of journeys) or 6 (the total number of journeys/browser). Maybe the output is truncated?
Please note, that the execution API reports the following result

_journey_execution_metrics": {
		"total": 12,
		"passed": 12,
		"failed": 0
	},_

Many thanks in advance,
Elena

In Mabl's CLI and API support a lot of options that are missing in this action. We're unable to specify labels, plan IDs.

Please expose all the features your CLI and API provide in this workflow.

https://github.com/github-actions-x/commit

Hello, we're using mablhq/github-run-tests-action@v1 in some of our CI/CD workflows.

Most of the time, it works great! Occasionally, maybe 1 out of 10 times, we are seeing an issue where the action hangs on Await completion of tests, and it thinks there is still a test plan running, even if the test plan appears to be complete in the Mabl web UI. We've seen the action get stuck indefinitely, requiring a manual cancellation, or it gets killed when Github's default 6 hour max duration for a step is exceeded.

We know we can add a timeout to the test step, but it still requires manual intervention to follow up on the real test result. We'd love to keep things automated as much as possible!

Hi,

First of all, many thanks for providing an implementation for GitHub Actions!
We are currently evaluating mabl for our testing purposes and CI/CD integration is a basic requirement from our side.

I gave it a try and the README you are providing does not refer to the action someone in his/her own repository would include.
The correct format would be

jobs:
  test:
    name: mabl Test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@master
      - name: Functional test deployment
        id: mabl-test-deployment
        **uses: mablhq/[email protected]**
        env:
          MABL_API_KEY: ${{ secrets.MABL_API_KEY }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          application-id: 12345678
          environment-id: 9012344

instead of

**uses: ./deploy-and-test/**

Many thanks in advance,
Elena

We get the following warning when using this action:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: mablhq/github-run-tests-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

What's your timeline for upgrading to node 20?

Hi,

I'm trying to use this action in our workflows to get PR checks and detailed information on runs for each commit, however I can't seem to get this work.

I get this from the logs:

Gathering inputs
  Using git revision [SHA]

However that SHA is not the last commit SHA on my PR, but rather a SHA of a "detached HEAD state", which I can confirm if I try to visit the url of that SHA in github.com, I get a warning saying "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository".

Am I doing something fundamentally wrong? I am using the action as in the example in the README.