-
Notifications
You must be signed in to change notification settings - Fork 5
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
API stability testing #23
Comments
harvey0100
added a commit
to harvey0100/autils
that referenced
this issue
Oct 18, 2024
Autils code is fetched from the pull request using the github.event.pull_request.head.sha. The tests are fetched from the master branch by running git fetch origin master and checking out only the tests/ directory from the master branch. Reference: avocado-framework#23 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/autils
that referenced
this issue
Oct 18, 2024
Autils code is fetched from the pull request using the github.event.pull_request.head.sha. The tests are fetched from the master branch by running git fetch origin master and checking out only the tests/ directory from the master branch. Reference: avocado-framework#23 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
Merged
harvey0100
added a commit
to harvey0100/autils
that referenced
this issue
Nov 1, 2024
Autils code is fetched from the pull request using the github.event.pull_request.head.sha. The tests are fetched from the master branch by running git fetch origin master and checking out only the tests/ directory from the master branch. Reference: avocado-framework#23 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
Solved in #25 |
github-project-automation
bot
moved this from Short Term (Current Q) Backlog
to Done 109
in Default project
Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
We need to ensure that autils API is stable over different versions. Since the autils will be used through different projects, we must avoid changes to the API of utilities until it is really necessary. This proposal is about possibilities how to ensure that.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Add PR and release testing which will run the patch or new version against the tests from master of older version to ensure there is no regression in the API.
Additional information
Add any additional information or screenshots about the feature request here.
If the API change is necessary we need to come up with suitable deprecating process for everybody to have time to adapt to such change.
Part of #1
The text was updated successfully, but these errors were encountered: