Some work is in progress to make it more general, but it is still fully usable under two usage param.

You can send the cypress report created from mochawesome as stringified JSON as a param e.g.

test: # make sure the action works on a clean machine without building
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - id: test_result
        uses: ./
        with: 
          jsonInput:  "json string"

test and action for stringified JSON value: test.yaml

  test: # make sure the action works on a clean machine without building
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
        with: 
          path: './'
      - uses: ./
        name: run test
        with:
          jsonArtifact: "./__tests__/ouput.json"

jobs:
  test: # make sure the action works on a clean machine without building
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
        with: 
          path: './'
      - uses: actions/upload-artifact@v3
        with: 
          name: output.json
          path: "./__tests__/output.json"   
  download:
    runs-on: ubuntu-latest
    needs: test
    steps:
      - uses: actions/checkout@v2
        with: 
          path: './'
      - uses: actions/download-artifact@v3
        with: 
          name: output.json
          path: "./"
      - uses: ./
        name: run test
        with:
          jsonArtifact: '/home/runner/work/cypress-test-summary/cypress-test-summary/ouput.json'

Currently when providing jsonArtifact, it is hardcoded to be picked from __tests__/output.json, so you can move your json file here in this folder once generated.

First, you'll need to have a reasonably modern version of node handy. This won't work with versions older than 9, for instance.

Install the dependencies

$ npm install

Build the typescript and package it for distribution

$ npm run build && npm run package

Run the tests ✔️

$ npm test

 PASS  ./index.test.js
  ✓ throws invalid number (3ms)
  ✓ wait 500 ms (504ms)
  ✓ test runs (95ms)

...

The action.yml defines the inputs and output for your action.

Update the action.yml with your name, description, inputs and outputs for your action.

See the documentation

Most toolkit and CI/CD operations involve async operations so the action is run in an async function.

import * as core from '@actions/core';
...

async function run() {
  try { 
      ...
  } 
  catch (error) {
    core.setFailed(error.message);
  }
}

run()

See the toolkit documentation for the various packages.

Actions are run from GitHub repos so we will checkin the packed dist folder.

Then run ncc and push the results:

$ npm run package
$ git add dist
$ git commit -a -m "prod dependencies"
$ git push origin releases/v1

Note: We recommend using the --license option for ncc, which will create a license file for all of the production node modules used in your project.

Your action is now published! 🚀

See the versioning documentation

You can now validate the action by referencing ./ in a workflow in your repo (see test.yml)

uses: ./
with:
  milliseconds: 1000

See the actions tab for runs of this action! 🚀

After testing you can create a v1 tag to reference the stable and latest V1 action