Document how to run unit and integration tests #329
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
stamhankar999
commented
Dec 15, 2016
stamhankar999
commented
- Update docs.yaml to exclude an appveyor url from external link checking. The link is good, but documentor erroneously thinks the link is bad.
* Update docs.yaml to exclude an appveyor url from external link checking. The link is good, but documentor erroneously thinks the link is bad.
mikefero
changed the title
mikefero
suggested changes
Dec 16, 2016
Contributor
mikefero
left a comment
mikefero
left a comment
There was a problem hiding this comment.
Looks good, but have a couple comments/thoughts for discussion.
topics/testing/README.md
Outdated
| # Testing | ||
| Before proceeding ensure the tests were built using the [build procedures]. | ||
|
|
||
| Both unit and integration tests use [Boost.Test](http://www.boost.org/doc/libs/1_62_0/libs/test/doc/html/index.html) |
Contributor
There was a problem hiding this comment.
+1 on the description; however should we also indicate how to launch them in Windows?
| # Run a particular suite | ||
| test/unit_tests/cassandra_unit_tests -t blacklist_lb | ||
| ``` | ||
|
|
Contributor
There was a problem hiding this comment.
- There is also a configuration file (that is being deprecated) in favor of command line driven options, we might also want to include information about the config.txt file until it is fully removed and that it should be located in the working directory (integration tests only as the unit tests do not require any additional configuration elements to run). I don't think we should document the defaults as we update them during release to use the latest Cassandra version at the time.
- CCM information is also missing as a dependency (this is required for the integration tests to run properly)
mpenick
pushed a commit
that referenced
this pull request
Dec 10, 2019
CPP-833 - Port named parameters tests to Google test framework
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.