You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/developers.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,9 @@
11
11
-[Code Formatting style](#code-formatting-style)
12
12
[back to main page](../README.md)
13
13
14
-
## Raising issues on GitHub
14
+
## Creating issues on GitHub
15
15
16
-
Raising issues on GitHub is a convernient way to notify the develper team about bugs and feature requests of the ABACUS code. We provide a few templates for issues.
16
+
Creating issues on GitHub is a convernient way to notify the develper team about bugs and feature requests of the ABACUS code. We provide a few templates for issues.
17
17
18
18
[back to top](#for-developers)
19
19
@@ -23,7 +23,7 @@ The ABACUS code is refactored to several self-contained modules. A description o
23
23
24
24
### Add a unit test
25
25
26
-
If there are currently no unit tests provided for the module, do as follows. `module_base` provides a simple demonstration.
26
+
We use GoogleTest as our test framework. Write your test under the corresponding module folder at `abacus-develop/tests`, then append the test to `tests/CMakeLists.txt`. If there are currently no unit tests provided for the module, do as follows. `module_base` provides a simple demonstration.
27
27
28
28
- Add a folder named `test` under the module.
29
29
- Append the content below to `CMakeLists.txt` of the module:
@@ -106,9 +106,6 @@ After your pull request is merged, you can safely delete your branch and pull th
106
106
git pull --ff upstream develop
107
107
```
108
108
109
-
### Providing unit tests
110
-
111
-
We use GoogleTest as our test framework. Write your test under the corresponding module folder at `abacus-develop/tests`, then append the test to `tests/CMakeLists.txt`. To build tests for abacus, set`BUILD_TESTING=1` when configuring with CMake. Executables of test programs will be under `build/tests`.
Copy file name to clipboardExpand all lines: doc/install.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,7 @@ If Libxc is not installed in standard path (i.e. installed with a custom prefix
124
124
cmake -B build -DLibxc_DIR=~/libxc
125
125
```
126
126
127
-
To build tests for abacus, define `BUILD_TESTING` flag.
127
+
To build tests for abacus, define `BUILD_TESTING` flag. You can also specify path to local installation of [Googletest](https://github.com/google/googletest) by setting `GTEST_DIR` flags. If not found in local, the configuration process will try to download it automatically.
128
128
129
129
```bash
130
130
cmake -B build -DBUILD_TESTING=1
@@ -139,6 +139,8 @@ cmake --build build -j9
139
139
cmake --install build
140
140
```
141
141
142
+
`-j9` specifies the number of jobs to run simultaneously. You can change the number on your need: set to the number of CPU cores to gain the best performance.
0 commit comments