2020-06-19 21:48:32 +02:00
|
|
|
|
2022-05-29 05:38:45 +02:00
|
|
|
# PULL REQUEST DESCRIPTION
|
2020-06-19 21:48:32 +02:00
|
|
|
|
2022-03-19 07:43:35 +01:00
|
|
|
`ADD CONTENT HERE TO DESCRIBE THE PURPOSE OF THE PULL REQUEST`
|
2020-06-19 21:48:32 +02:00
|
|
|
|
2022-05-29 05:38:45 +02:00
|
|
|
# Testing
|
|
|
|
|
|
2022-05-29 12:24:55 +02:00
|
|
|
- [ ] This new/modified code was covered by unit tests.
|
2022-05-29 05:38:45 +02:00
|
|
|
|
2022-05-29 12:24:55 +02:00
|
|
|
- [ ] (insight) Was all tests written using TDD (Test Driven Development) style?
|
2022-05-29 05:38:45 +02:00
|
|
|
|
2022-05-29 12:24:55 +02:00
|
|
|
- [ ] The CI (Windows, Linux, OSX) are working without issues.
|
2022-05-29 05:38:45 +02:00
|
|
|
|
2022-05-29 12:24:55 +02:00
|
|
|
- [ ] Was new functionality documented?
|
2022-05-29 05:38:45 +02:00
|
|
|
|
2022-05-29 12:24:55 +02:00
|
|
|
- [ ] The testing steps 1 - 2 below were followed
|
2020-06-19 20:02:48 +02:00
|
|
|
|
2022-03-19 07:43:35 +01:00
|
|
|
_step 1_
|
2020-06-19 20:02:48 +02:00
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
mkdir build; cd build; cmake -DADD_G3LOG_UNIT_TEST=ON ..
|
2022-03-19 07:43:35 +01:00
|
|
|
|
|
|
|
|
// linux/osx alternative, simply run: ./scripts/buildAndRunTests.sh
|
2020-06-19 20:02:48 +02:00
|
|
|
```
|
|
|
|
|
|
2022-03-19 07:43:35 +01:00
|
|
|
_step 2: use one of these alternatives to run tests:_
|
|
|
|
|
|
2020-06-19 20:02:48 +02:00
|
|
|
- Cross-Platform: `ctest`
|
|
|
|
|
- or `ctest -V` for verbose output
|
2022-05-29 12:24:55 +02:00
|
|
|
- Linux: `make test`
|
