All Projects → mablhq → github-run-tests-action

mablhq / github-run-tests-action

Licence: MIT License
mabl Github Actions implementation

Programming Languages

typescript
32286 projects
HTML
75241 projects
javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to github-run-tests-action

setup-jdk
(DEPRECATED) Set up your GitHub Actions workflow with a specific version of AdoptOpenJDK
Stars: ✭ 32 (-17.95%)
Mutual labels:  actions, action, github-actions, github-action
ssh2actions
Connect to GitHub Actions VM via SSH for interactive debugging
Stars: ✭ 62 (+58.97%)
Mutual labels:  actions, action, github-actions, github-action
clojure-dependency-update-action
A simple GitHub Actions job to create Pull Requests for outdated dependencies in clojure projects
Stars: ✭ 37 (-5.13%)
Mutual labels:  actions, action, github-actions, github-action
assign-one-project-github-action
Automatically add an issue or pull request to specific GitHub Project(s) when you create and/or label them.
Stars: ✭ 140 (+258.97%)
Mutual labels:  actions, action, github-actions, github-action
action-sync-node-meta
GitHub Action that syncs package.json with the repository metadata.
Stars: ✭ 25 (-35.9%)
Mutual labels:  actions, action, github-actions, github-action
action-netlify-deploy
🙌 Netlify deployments via GitHub actions
Stars: ✭ 32 (-17.95%)
Mutual labels:  actions, github-actions, github-action
rubocop-linter-action
Rubocop Linter Action: A GitHub Action to run Rubocop against your code!
Stars: ✭ 86 (+120.51%)
Mutual labels:  actions, action, github-actions
actions
Collection of repetitive GitHub Actions
Stars: ✭ 12 (-69.23%)
Mutual labels:  actions, action, github-actions
qodana-action
⚙️ Scan your Java, Kotlin, PHP, Python, JavaScript, TypeScript projects at GitHub with Qodana
Stars: ✭ 112 (+187.18%)
Mutual labels:  actions, github-actions, github-action
actions
Set of actions for implementing CI/CD with werf and GitHub Actions
Stars: ✭ 67 (+71.79%)
Mutual labels:  actions, action, github-actions
nrwl-nx-action
A GitHub Action to wrap Nrwl Nx commands in your workflows.
Stars: ✭ 163 (+317.95%)
Mutual labels:  actions, github-actions, github-action
action-autotag
Automatically generate a new tag when the manifest file (package.json, Dockerfile, custom file, etc) version changes.
Stars: ✭ 45 (+15.38%)
Mutual labels:  actions, action, github-actions
dart-package-publisher
Action to Publish Dart / Flutter Package To https://pub.dev When you need to publish a package, just bump the version in pubspec.yaml
Stars: ✭ 45 (+15.38%)
Mutual labels:  actions, action, github-actions
overview
Automate your workflows with GitHub actions for MATLAB.
Stars: ✭ 40 (+2.56%)
Mutual labels:  actions, github-actions, github-action
changed-files
Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories.
Stars: ✭ 733 (+1779.49%)
Mutual labels:  actions, github-actions, github-action
jest-github-action
Jest action adding checks with annotations to your pull requests and coverage table as comments
Stars: ✭ 134 (+243.59%)
Mutual labels:  actions, action, github-actions
recent-activity
Add your recent activity to your profile readme!
Stars: ✭ 87 (+123.08%)
Mutual labels:  actions, github-actions, github-action
setup-bats
GitHub Action to setup BATS testing framework
Stars: ✭ 25 (-35.9%)
Mutual labels:  action, github-actions, github-action
hugo-action
Commands to help with building Hugo based static sites
Stars: ✭ 65 (+66.67%)
Mutual labels:  action, github-actions, github-action
git-actions
A GitHub Action to run arbitrary git commands
Stars: ✭ 72 (+84.62%)
Mutual labels:  action, github-actions, github-action

mabl logo

mabl GitHub Run Tests Deployment Action

This GitHub Action creates a mabl deployment event, triggering cloud test runs associated with that deployment and waiting for their results.

For more complex use cases, see the setup-mabl-cli Action to access the CLI directly.

Example workflow: Simple

on: [push]

name: mabl Simple Example

jobs:
  test:
    name: mabl Test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2

      - name: Functional test deployment
        id: mabl-test-deployment
        uses: mablhq/github-run-tests-action@v1
        env:
          MABL_API_KEY: ${{ secrets.MABL_API_KEY }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          application-id: <your-application-id-a>
          environment-id: <your-environment-id-e>

Example workflow: Complete

Using all available flags.

on: [push]

name: mabl Complex Example

jobs:
  test:
    name: mabl Test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2

      - name: Functional test deployment
        id: mabl-test-deployment
        uses: mablhq/github-run-tests-action@v1
        env:
          MABL_API_KEY: ${{ secrets.MABL_API_KEY }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          application-id: <your-application-id-a>
          environment-id: <your-environment-id-e>
          uri: <your-override-url>
          mabl-branch: <your-mabl-branch-name>
          # Runs for both browsers
          browser-types: |
            chrome
            firefox
          # Runs plans matching ANY of the following labels AND the environment/application IDs above
          plan-labels: |
            canary
            smoke-test
          http-headers: |
            My-Header:the-value
            My-Other-Header:the-second-value
          continue-on-failure: true
          rebaseline-images: true
          set-static-baseline: true
          event-time: <your-event-time-epoch-milliseconds>

Environment variables

  • MABL_API_KEY {string} - Your mabl API key available here This should be installed as a secret in your github repository.
  • GITHUB_TOKEN {string} (optional) - The Github token for your repository. If provided, the mabl action will associate a pull request with the deployment if the commit being built is associated with any pull requests. This token is automatically available as a secret in your repo but must be passed in explicitly in order for the action to be able to access it.

Inputs

Note: Either application-id or environment-id must be supplied.

  • application-id {string} (optional) - mabl id for the deployed application. Use the curl builder to find the id.
  • environment-id {string} (optional) - mabl id for the deployed environment. Use the curl builder to find the id.
  • browser-types {string} (optional): comma or new line separated override for browser types to test e.g. chrome, firefox, safari, internet_explorer. If not provided, mabl will test the browsers configured on the triggered test.
  • plan-labels {string} (optional): comma or new line separated plan labels to test. Plans matching any label will be run. e.g. smoke-test, beta-feature. Note: additional selection criteria must also be met like application-id or environment-id, if supplied.
  • uri {string} (optional) the base uri to test against. If provided, this will override the default uri associated with the environment in mabl
  • mabl-branch {string} (optional) run tests on the mabl branch of tests with this name. Defaults to master.
  • http-headers {string} (optional) Headers to add to all requests e.g. "My-Header:the-value" (comma or new line delimited).
  • rebaseline-images {boolean} (optional) - Set true to reset the visual baseline to the current deployment
  • set-static-baseline {boolean} (optional) - Set true to use current deployment as an exact static baseline. If set, mabl will not model dynamic areas and will use the current deployment as the pixel-exact visual baseline.
  • continue-on-failure {boolean} (optional) - Set to true to continue the build even if there are test failures
  • event-time {int64} (optional) - Event time the deployment occurred in UTC epoch milliseconds. Defaults to now.

outputs:

  • mabl-deployment-id {string} - mabl id of the deployment
  • plans_run {int32} - number of mabl plans run against this deployment. A mabl plan is a collection of similarly configured tests.
  • plans_passed {int32} - number of mabl plans that passed against this deployment. A mabl plan is a collection of similarly configured tests.
  • plans_failed {int32} - number of mabl plans that failed against this deployment. A mabl plan is a collection of similarly configured tests.
  • tests_run {int32} - total number of mabl tests run against this deployment.
  • tests_passed {int32} - number of mabl tests that passed against this deployment.
  • tests_failed {int32} - number of mabl tests that failed against this deployment.

Contributing

See here for details on contributing to this action.

License

The Dockerfile and associated scripts and documentation in this project are released under the MIT License.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].