update integration testing doc #3073
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@orndorffgrant @lucasmoura
Please feel free to leave comments for specific changes if these sections have to be updated. Thanks! |
lucasmoura
approved these changes
Apr 22, 2024
dev-docs/howtoguides/testing.md
Outdated
| As can be seen, this will run behave tests only for release 22.04 (Jammy Jellyfish). We are currently | ||
| supporting 7 distinct releases: | ||
|
|
||
| * 23.10 (Mantic Minotaur) |
There was a problem hiding this comment.
We no longer run tests for Lunar and Kinetic, we can remove those entries
There was a problem hiding this comment.
Please avoid specifying the releases, unless if giving an example. Specify the rule:
- all supported releases
- LTS releases, including those under ESM
- devel release, at some point in the development cycle
Otherwise this is going to go stale often and we need to update it every 3 months or so during the interim cycles
There was a problem hiding this comment.
Updated to mention the rule instead of specific releases
dheyay
force-pushed
the
update-testing-doc
branch
4 times, most recently
from
ad88972
to
43cfb03
Compare
orndorffgrant
approved these changes
May 7, 2024
dev-docs/howtoguides/testing.md
Outdated
| @@ -57,36 +57,33 @@ The testing can be overridden to install ubuntu-advantage-tools from other sourc | |||
| > **Note** | |||
| > Note that we cache the source when running with `UACLIENT_BEHAVE_INSTALL_FROM=local` based on a hash, calculated from the repository state. If you change the python code locally and run the behave tests against your new version, there will be new debs in the cache source with the new repo state hash. | |||
|
|
|||
| To run the tests, you can use `tox`: | |||
| To run the integration tests, use the `tox` command as shown below. | |||
| Please note that this command will execute all the integration tests sequentially and may take a significant amount of time to complete, depending on the number and complexity of the tests. | |||
There was a problem hiding this comment.
This command as written will always take a long time - no "depending..." :)
Suggested change
| Please note that this command will execute all the integration tests sequentially and may take a significant amount of time to complete, depending on the number and complexity of the tests. | |
| Please note that, as shown here without arguments, this command would execute all the integration tests sequentially and would take an inordinate amount of time to complete. Always pass arguments to this command to specify a subset of tests to run, as demonstrated next. |
dheyay
force-pushed
the
update-testing-doc
branch
from
8014ec1
to
6c0fd5f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why is this needed?
This PR updates the integration testing document to current commands for testing the pro client.
Test Steps
Checklist
Does this PR require extra reviews?