Skip to content
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

Use bats-core instead of bats #135

Open
extsoft opened this issue Jun 24, 2019 · 0 comments
Open

Use bats-core instead of bats #135

extsoft opened this issue Jun 24, 2019 · 0 comments
Labels
chore next release This issue will be released in the next release.

Comments

@extsoft
Copy link
Contributor

extsoft commented Jun 24, 2019

We have to switch to https://github.com/bats-core/bats-core as this fork of original bats is under maintenance now.

@extsoft extsoft added the chore label Sep 1, 2019
extsoft added a commit that referenced this issue Jun 10, 2020
There is a separate Docker worker that allows running Bats tests based
on version 1.2.0 of `bats-core` project. This modification allows
receiving updates to the test runner.

All testing procedure is reworked in a way that `workflows` file is
responsible for running Docker workers for testing while scripts,
located at `.workflows` directory, just run the needed workflows without
pointing to an environment.

`tests/git-elegant.bats` was updated as in Bash 3.x (which is used in
the Bats worker) is not possible to get the last element of the array.
So, `show-commands` in the tests is replaced with `prune-repository` as
the last command produces the same amount of lines comparing to the fact
that adding or removing of command will affect the output of
`show-commands`.

#135
extsoft added a commit that referenced this issue Jun 10, 2020
There is a separate Docker worker that allows running Bats tests based
on version 1.2.0 of `bats-core` project. This modification allows
receiving updates to the test runner.

All testing procedure is reworked in a way that `workflows` file is
responsible for running Docker workers for testing while scripts,
located at `.workflows` directory, just run the needed workflows without
pointing to an environment.

`tests/git-elegant.bats` was updated as in Bash 3.x (which is used in
the Bats worker) is not possible to get the last element of the array.
So, `show-commands` in the tests is replaced with `prune-repository` as
the last command produces the same amount of lines comparing to the fact
that adding or removing of command will affect the output of
`show-commands`.

#135
extsoft added a commit that referenced this issue Jun 10, 2020
There is a separate Docker worker that allows running Bats tests based
on version 1.2.0 of `bats-core` project. This modification allows
receiving updates to the test runner.

All testing procedure is reworked in a way that `workflows` file is
responsible for running Docker workers for testing while scripts,
located at `.workflows` directory, just run the needed workflows without
pointing to an environment.

`tests/git-elegant.bats` was updated as in Bash 3.x (which is used in
the Bats worker) is not possible to get the last element of the array.
So, `show-commands` in the tests is replaced with `prune-repository` as
the last command produces the same amount of lines comparing to the fact
that adding or removing of command will affect the output of
`show-commands`.

#135
@extsoft extsoft added the next release This issue will be released in the next release. label Jun 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore next release This issue will be released in the next release.
Projects
None yet
Development

No branches or pull requests

1 participant