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 documentation #1136

Merged
merged 2 commits into from
Aug 26, 2020
Merged

Conversation

antoninbas
Copy link
Contributor

  • add missing linters
  • emphasize that new test cases should be added as part of new
    contributions and include more details about the different categories
    of tests we support; this is related to
    Obtain "passing" CII Best Practices badge #989

@antrea-bot
Copy link
Collaborator

Thanks for your PR.
Unit tests and code linters are run automatically every time the PR is updated.
E2e, conformance and network policy tests can only be triggered by a member of the vmware-tanzu organization. Regular contributors to the project should join the org.

The following commands are available:

  • /test-e2e: to trigger e2e tests.
  • /skip-e2e: to skip e2e tests.
  • /test-conformance: to trigger conformance tests.
  • /skip-conformance: to skip conformance tests.
  • /test-whole-conformance: to trigger all conformance tests on linux.
  • /skip-whole-conformance: to skip all conformance tests on linux.
  • /test-networkpolicy: to trigger networkpolicy tests.
  • /skip-networkpolicy: to skip networkpolicy tests.
  • /test-windows-conformance: to trigger windows conformance tests.
  • /skip-windows-conformance: to skip windows conformance tests.
  • /test-windows-networkpolicy: to trigger windows networkpolicy tests.
  • /skip-windows-networkpolicy: to skip windows networkpolicy tests.
  • /test-hw-offload: to trigger ovs hardware offload test.
  • /skip-hw-offload: to skip ovs hardware offload test.
  • /test-all: to trigger all tests (except whole conformance).
  • /skip-all: to skip all tests (except whole conformance).

@antoninbas antoninbas force-pushed the documentation-updates branch from 1378881 to 9b70e7c Compare August 22, 2020 00:18
abhiraut
abhiraut previously approved these changes Aug 25, 2020
ci/README.md Outdated

We run 4 different categories of tests as part of CI:
* **unit tests**: most Go packages for Antrea include some unit tests written
using the [Go `testing`] package. Unit tests typically rely on mock testing
Copy link
Contributor

@lzhecheng lzhecheng Aug 25, 2020

Choose a reason for hiding this comment

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

I wonder why [Go testing], not [Go testing] or Go [testing] ? I think it looks strange.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed to Go [testing]

ci/README.md Outdated
* **unit tests**: most Go packages for Antrea include some unit tests written
using the [Go `testing`] package. Unit tests typically rely on mock testing
to isolate the package being tested, and abstract platform-specific
functionality hidden behing interfaces. When adding a new package or
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
functionality hidden behing interfaces. When adding a new package or
functionality hidden behind interfaces. When adding a new package or

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, thanks

ci/README.md Outdated
typically exercise multiple Go packages to ensure that they are working
correctly together. In the case of Antrea, integration tests may create an
actual OVS bridge, which is why they depend on the OVS daemons running, and
are typically run inside a Docker image, even on Linux. Write integrations
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
are typically run inside a Docker image, even on Linux. Write integrations
are typically run inside a Docker image, even on Linux. Write integration

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, thanks

ci/README.md Outdated
also written using the [Go `testing`] package. Unlike the two previous test
categories, these assume that Antrea is running on an actual cluster and
require a kubeconfig file as well as SSH access to the cluster
Nodes. Instructions on how to run these tests, including how to setup a local
Copy link
Member

Choose a reason for hiding this comment

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

These lines seem not wrapped strictly, e.g. the above line has enough space for "Node."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's funny, The auto-wrap in emacs refused to place Nodes on the same line as cluster. I had to do it manually...

 * add missing linters
 * emphasize that new test cases should be added as part of new
   contributions and include more details about the different categories
   of tests we support; this is related to
   antrea-io#989
@antoninbas
Copy link
Contributor Author

Thanks for the reviews, I addressed all comments

@lzhecheng lzhecheng self-requested a review August 26, 2020 01:35
Copy link
Contributor

@lzhecheng lzhecheng left a comment

Choose a reason for hiding this comment

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

LGTM.

Copy link
Member

@tnqn tnqn left a comment

Choose a reason for hiding this comment

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

LGTM

@antoninbas
Copy link
Contributor Author

/skip-all

@antoninbas antoninbas merged commit 4ed2c67 into antrea-io:master Aug 26, 2020
@antoninbas antoninbas deleted the documentation-updates branch August 26, 2020 19:11
GraysonWu pushed a commit to GraysonWu/antrea that referenced this pull request Sep 22, 2020
* Update documentation

 * add missing linters
 * emphasize that new test cases should be added as part of new
   contributions and include more details about the different categories
   of tests we support; this is related to
   antrea-io#989

* Address review comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants