Skip to content
This repository was archived by the owner on Sep 17, 2025. It is now read-only.

Run integration tests with different permutations of dependencies.#202

Open
brianquinlan wants to merge 2 commits intocensus-instrumentation:masterfrom
brianquinlan:master
Open

Run integration tests with different permutations of dependencies.#202
brianquinlan wants to merge 2 commits intocensus-instrumentation:masterfrom
brianquinlan:master

Conversation

@brianquinlan
Copy link
Copy Markdown
Contributor

I'm not sure if this is a good idea or not.

session.interpreter = 'python{}'.format(py)

# Install all test dependencies, then install this package in-place.
session.install('google-cloud-trace')
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are we going to run unit tests against the latest version of google-cloud-trace? While this can make sure our library works well with the latest release version of it, but it would be confusing whether the tests failed because of the version incompatibility issue or the tested code itself.

I would suggest we pin the version used for tests and add tooling for ensuring we work well with the latest release when the tools is built.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Should we pin the version or test with the versions matching setup.py i.e.
google-cloud-trace=0.17.0, google-cloud-trace<0.20
google-api-core = 0.1.1, google-api-color < 2.0.0
?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants