-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BDD: Configure CI to run BDD tests #43
Comments
See #30 (comment) Here's what I think would work:
As a developer, the local environment should have Grakn server and features available already. Then, doing |
Perhaps we can use this here: https://github.com/marketplace/actions/github-action-for-bash |
I created a GitHub Action here: https://github.com/Humans-of-Julia/GraknRunner Not sure yet, if we can do it all in one, but would be ideal I think. It can be easily included in a workflow file like: name: Grakn BDD runner
on: [push]
jobs:
hello_world_job:
runs-on: ubuntu-latest
name: A job to pull feature files, install Grakn, and execute the tests
steps:
- uses: actions/checkout@v2
- id: foo
uses: Humans-of-Julia/GraknRunner@0.1.0
with:
who-to-greet: 'Mark'
- run: echo random-number ${{ steps.foo.outputs.random-number }}
shell: bash |
I'm curious here, would that mean the test has to run locally? Wouldn't it be cool to let it all run in the virtual machine in the GitHub Action runner? |
Configure CI to run BDD process (pull feature files, install Grakn, and execute the tests)
The text was updated successfully, but these errors were encountered: