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

Add some notes on how to run tests against a real Artifactory #7697

merged 5 commits into from Sep 14, 2020


Copy link

@czoido czoido commented Sep 10, 2020

Changelog: Feature: Instructions on how to run conan tests against a real Artifactory server.
Docs: omit

  • Refer to the issue that supports this Pull Request.
  • If the issue has missing info, explain the purpose/use case/pain/need that covers this Pull Request.
  • I've read the Contributing guide.
  • I've followed the PEP8 style guides for Python code.
  • I've opened another PR in the Conan docs repo to the develop branch, documenting this one.

Note: By default this PR will skip the slower tests and will use a limited set of python versions. Check here how to increase the testing level by writing some tags in the current PR body text.

@memsharded memsharded added this to the 1.30 milestone Sep 10, 2020
README.rst Show resolved Hide resolved
@@ -208,6 +208,21 @@ To run specific tests, you can specify the test name too, something like:

The ``--nocapture`` argument can be useful to see some output that otherwise is captured by nosetests.

Also, you can run tests against an instance of Artifactory. Those tests should add the attribute
Copy link

@memsharded memsharded Sep 10, 2020

Choose a reason for hiding this comment

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

Maybe it would be good to actually add a command line example like nosetests . -A "artifactory_ready"?

@memsharded memsharded merged commit c829789 into conan-io:develop Sep 14, 2020
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

2 participants