-
Notifications
You must be signed in to change notification settings - Fork 63
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
Move goth integration tests to yagna repo #1235
Conversation
... | ||
): | ||
goth_config = load_yaml(Path("path/to/goth-config.yml", config_overrides) | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This README
is excellent!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed. Much appreciated effort @zakaprov
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
goth_tests/README.md
Outdated
|
||
### Project setup | ||
Below are the steps you need to take in order to prepare your environment for running this integration test suite. | ||
> Please not that currently the only supported platform is **Linux** with **Python 3.8+**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> Please not that currently the only supported platform is **Linux** with **Python 3.8+**. | |
> Please note that currently the only supported platform is **Linux** with **Python 3.8+**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in 31cfad0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Brilliant!
I've only left some minor comments, nothing blocking.
09dfb86
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All my comments have been resolved, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Adds files necessary for running goth tests as part of yagna repository. This also includes moving the VM E2E test from goth to yagna.
Heads up: I'm doing an interactive rebase before merging to get rid of some redundant commits. |
If a test requires custom assets (e.g. VM Blender test) they should be placed in a directory named `assets` alongside the test `.py` file itself. | ||
|
||
### How these tests work | ||
Every `goth` test operates on an isolated, local network of `yagna` nodes which gets created using Docker. Besides the `yagna` containers themselves this network also includes components such as `ya-sb-router` or `ganache` local blockchain. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Every `goth` test operates on an isolated, local network of `yagna` nodes which gets created using Docker. Besides the `yagna` containers themselves this network also includes components such as `ya-sb-router` or `ganache` local blockchain. | |
Every `goth` test operates on an isolated, local network of `yagna` nodes which gets created using Docker. Besides the `yagna` containers themselves this network also includes components such as `ya-sb-router` (used for instantiating owned local yagna networking) or `ganache` local blockchain. |
2. The test runner creates a number of Yagna containers (as defined in `goth-config.yml`) which are connected to the `docker-compose` network. | ||
3. For each Yagna container started a so-called "probe" object is created and made available inside the test via the `Runner` object. | ||
4. The integration test scenario is executed as defined in the function called by `pytest`. | ||
5. Once the test is finished, all previously started Docker containers (both "static" and "dynamic") are removed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd mention "dynamic" within point 2. as you did with "static" in 1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great job!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, once again!
Move goth integration tests to yagna repo
Resolves: golemfactory/goth#401