Skip to content

Commit 67dd73a

Browse files
committed
[doc] The roottest and root repos have been merged
1 parent ae12944 commit 67dd73a

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

CONTRIBUTING.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -98,13 +98,12 @@ Please ping people :wave: should you not get timely feedback, for instance with
9898
As you contribute code, this code will likely fix an issue or add a feature.
9999
Whatever it is: this requires you to add a new test, or to extend an existing test. Depending on the size and complexity
100100
of this test, it exists either in the `test/` subdirectory of each part of ROOT (see for instance
101-
[`tree/dataframe/test`](https://github.com/root-project/root/tree/master/tree/dataframe/test)), or in
102-
[roottest](https://github.com/root-project/roottest.git). Tests in `test/` subdirectories are unit tests, mostly based on
101+
[`tree/dataframe/test`](https://github.com/root-project/root/tree/master/tree/dataframe/test)), or in the
102+
[roottest](https://github.com/root-project/root/tree/master/roottest) directory.
103+
Tests in `test/` subdirectories are unit tests, mostly based on
103104
[Google Test](https://github.com/google/googletest) and easily extended. Tests in
104-
[roottest](https://github.com/root-project/roottest.git) are more involved (e.g., tests requiring custom dictionaries or
105-
data files). When you create a branch in the main ROOT repository (i.e., this repository) and add a test to `roottest`,
106-
make sure to do this under the same branch name (and open a PR for it). Our CI infrastructure automatically picks up the
107-
changes defined in the `roottest` PR based on this branch name, and uses that for testing your PR here.
105+
[roottest](https://github.com/root-project/root/tree/master/roottest) are more involved (e.g., tests requiring custom dictionaries or
106+
data files).
108107
109108
## Continuous Integration
110109

0 commit comments

Comments
 (0)