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

AET Docker client #26

Merged
merged 1 commit into from
Aug 20, 2020
Merged

AET Docker client #26

merged 1 commit into from
Aug 20, 2020

Conversation

malaskowski
Copy link
Owner

Introducing new way to run AET suites with no extra dependencies but Docker.

You may use an image that embeds AET Bash client together with its dependencies by running:

docker run --rm -v "$(pwd)/suite:/aet/suite" -v "$(pwd)/report:/aet/report" skejven/aet_client AET_INSTANCE_IP /aet/suite/SUITE_YOU_WANT_TO_RUN

E.g. when you run AET on Docker for Mac/Win and have following setup:

.
├── custom
│   └── my-suite.xml

and want to run my-suite.xml file, simply run:
docker run --rm -v "$(pwd)/custom:/aet/suite" -v "$(pwd)/report:/aet/report" skejven/aet_client http://host.docker.internal /aet/suite/my-suite.xml

The results will be saved to the report directory:

.
├── report
│   ├── redirect.html
│   └── xUnit.xml

Notice that we are using here host.docker.internal as the address of AET instance - that works only for Docker for Mac/Win with local AET setup. In other cases, use the AET server's IP/domain.

@malaskowski malaskowski force-pushed the feature/aet-docker-client branch from 15f54d8 to c2cec7d Compare August 17, 2020 18:18
@malaskowski malaskowski merged commit 25ecc7b into master Aug 20, 2020
@malaskowski malaskowski deleted the feature/aet-docker-client branch August 20, 2020 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant