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

BATS: new tests, and improvements to existing ones #2703

Merged
merged 1 commit into from
Mar 19, 2019

Conversation

edsantiago
Copy link
Member

New:

Improved:

  • help: test "podman NoSuchCommand", and subcommands
  • help: test "podman cmd" without required args
  • pod: start with --infra=false; this allows running rootless
  • log: also run 'logs' after container is run
  • log: test -f with two containers

Also, use helpful descriptions for skip_if_rootless

Tested on f29, root and rootless. As soon as podman-remote
supports rm, I'll start testing that too.

Signed-off-by: Ed Santiago [email protected]

New:
 - podman exec
 - podman load (requires containers#2674)
 - CLI parsing (regression test for containers#2574)

Improved:
 - help: test "podman NoSuchCommand", and subcommands
 - help: test "podman cmd" without required args
 - pod: start with --infra=false; this allows running rootless
 - log: also run 'logs' after container is run
 - log: test -f with two containers

Also, use helpful descriptions for skip_if_rootless

Tested on f29, root and rootless. As soon as podman-remote
supports rm, I'll start testing that too.

Signed-off-by: Ed Santiago <[email protected]>
Copy link
Member

@cevich cevich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a gentle reminder/suggestion: I feel we're near the time to avoid testing individual commands and focus on workflows. I understand some duplication vs the e2e tests is unavoidable. If there are bugs you're finding in system-tests, they should result in new e2e tests being written. Ask for help and/or open issues for new e2e or unit-tests, the team can help write or fix them. My motivation is in the large: getting feedback to engineers as quickly, directly, and as near to the (guilty) change as possible 😁

LGTM

These are great. Very readable, and well thought out. Thanks for taking the initiative to write these and oversee assembly of the system-tests (including bug follow-through). I know first-hand the bug-part is no small feat, sometimes it seems like 90% of the work in writing a new test!

test/system/015-help.bats Show resolved Hide resolved
test/system/035-logs.bats Show resolved Hide resolved
test/system/035-logs.bats Show resolved Hide resolved
test/system/120-load.bats Show resolved Hide resolved
@cevich
Copy link
Member

cevich commented Mar 19, 2019

@rhatdan PTAL I'd ask Brent, but suspect he's reached his 5-lines of bash-quota for the week 😄

@cevich
Copy link
Member

cevich commented Mar 19, 2019

/approve

@rhatdan
Copy link
Member

rhatdan commented Mar 19, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 19, 2019
@haircommander
Copy link
Collaborator

@rhatdan needs an approver to approve it first :)

@rhatdan
Copy link
Member

rhatdan commented Mar 19, 2019

/approve

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cevich, edsantiago, rhatdan

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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 19, 2019
@openshift-merge-robot openshift-merge-robot merged commit 537c382 into containers:master Mar 19, 2019
@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 27, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 27, 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants