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

Update the testing documentation with system tests. #3470

Merged
merged 1 commit into from
Jul 11, 2019

Conversation

QazerLab
Copy link
Contributor

@QazerLab QazerLab commented Jul 1, 2019

I had some hard time figuring out why system tests do not run well on my machine. It torn out that some people (and distros) still use the legacy version of Bats, which is incompatible with Podman tests, because its last released version has a fatal flaw, rendering half of the tests red.

Updating the testing documentation with link to the correct Bats repository to provide some clue for occasional users of old Bats.

Add Bats installation procedure.

Signed-off-by: Danila Kiver <danila.kiver@mail.ru>
@openshift-ci-robot
Copy link
Collaborator

Hi @QazerLab. Thanks for your PR.

I'm waiting for a containers or openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 1, 2019
@rh-atomic-bot
Copy link
Collaborator

Can one of the admins verify this patch?
I understand the following commands:

  • bot, add author to whitelist
  • bot, test pull request
  • bot, test pull request once

@mheon
Copy link
Member

mheon commented Jul 2, 2019

/ok-to-test
/approve

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mheon, QazerLab

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 2, 2019
@mheon
Copy link
Member

mheon commented Jul 2, 2019

@edsantiago PTAL

@rhatdan
Copy link
Member

rhatdan commented Jul 2, 2019

LGTM
@TomSweeneyRedHat PTAL

@TomSweeneyRedHat
Copy link
Member

This probably has a merge dance with #3377.
Changes LGTM, but want a head nod from @edsantiago

@QazerLab
Copy link
Contributor Author

#3377 is merged, but there is no conflict, as it modifies different md file (test/system/README.md). I think it would be a good idea to merge stuff from current PR to the section added by #3377 and replace the same section in test/README.md with the link to test/system/README.md.

@edsantiago, @TomSweeneyRedHat, WDYT?

@rhatdan
Copy link
Member

rhatdan commented Jul 11, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 11, 2019
@openshift-merge-robot openshift-merge-robot merged commit 24409da into containers:master Jul 11, 2019
@QazerLab QazerLab deleted the docs/system-tests branch July 11, 2019 21:11
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. ok-to-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants