Skip to content

Test aliases don't allow for multiple cucumber tags to be run locally #180

@tasharghyrou

Description

@tasharghyrou

I'm submitting a support/potential bug request

  • bug report

  • feature request

  • support request

The alias for running acceptance tests does not appear to allow for multiple cucumber tags to be run at once anymore, I think it's due to an update in how the tags need to be formatted now with the following error message when trying to run in the comma-separated format that used to work:

Found tags option '@TestCaseKey=E2E-T33,'. '@tag1,@tag2' is no longer supported, use '@tag or @tag2' instead. (RuntimeError)

What is the current behaviour?
When using the command in the now supported format with the acctest alias (have also tried with various formats like putting the tags within '' or "") e.g:
acctest digital-e2e-regression --tags @TestCaseKey=E2E-T33 or @TestCaseKey=E2E-T209

The following error message occurs:
No such file or directory - or. You can use cucumber --init to get started.

When running the full command it will run the multiple tags successfully e.g:
docker-compose run --rm digital-e2e-regression cucumber --color --format pretty --format html --out cucumber-report.html --format json --out test-report.json --tags '@TestCaseKey=E2E-T33 or @TestCaseKey=E2E-T209'

So it's only when using the acctest alias that the error occurs

Example taken from our gitlabs test-common-components/regression/digital-e2e-regression repo but this is also affecting other teams.

What is the expected/proposed behaviour?
To be able to run multiple tags using the acctest alias again.

What is the motivation / use case for changing the behaviour?
Running multiple tags is a common thing for testers to do locally, and using the alias is the standard way to run tests. Right now, testers are running each tag individually and this would save them time and effort having to do multiple runs. We used to be able to run multiple tags locally before the previous comma separated way became unsupported

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions