forked from dev-cafe/cmake-cookbook
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
36 additions
and
4 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# Deploying tests to the CDash dashboard | ||
|
||
Abstract to be written ... | ||
In this recipe, we will extend the test example of | ||
[chapter 4, recipe 1](../../chapter-04/recipe-01), | ||
and deploy the test result to | ||
https://my.cdash.org/index.php?project=cmake-cookbook. | ||
|
||
|
||
- [cxx-example](cxx-example/) |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
In this recipe, we will extend the test example of | ||
[chapter 4, recipe 1](../../chapter-04/recipe-01), | ||
and deploy the test result to | ||
https://my.cdash.org/index.php?project=cmake-cookbook. |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,8 @@ | ||
# Reporting test coverage to the CDash dashboard | ||
|
||
Abstract to be written ... | ||
In this recipe, we measure the test coverage and report it to the CDash | ||
dashboard, where we will be able to browse the test coverage analysis | ||
line-by-line, in order to identify untested or unused code. | ||
|
||
|
||
- [cxx-example](cxx-example/) |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
In this recipe, we measure the test coverage and report it to the CDash | ||
dashboard, where we will be able to browse the test coverage analysis | ||
line-by-line, in order to identify untested or unused code. |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,11 @@ | ||
# Using the AddressSanitizer and reporting memory defects to CDash | ||
|
||
Abstract to be written ... | ||
In this recipe, we fabricate two bugs in our code, which may go undetected in a | ||
normal test run. To detect these bugs, we couple CTest with dynamic analysis by | ||
using | ||
[AddressSanitizer](https://github.com/google/sanitizers/wiki/AddressSanitizer), | ||
and report the defects to CDash. | ||
|
||
|
||
- [cxx-example](cxx-example/) | ||
- [fortran-example](fortran-example/) |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
In this recipe, we fabricate two bugs in our code, which may go undetected in a | ||
normal test run. To detect these bugs, we couple CTest with dynamic analysis by | ||
using | ||
[AddressSanitizer](https://github.com/google/sanitizers/wiki/AddressSanitizer), | ||
and report the defects to CDash. |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# Using the ThreadSanitizer and reporting data races to CDash | ||
|
||
Abstract to be written ... | ||
In this recipe, we reuse the approach from the previous example, but use | ||
[ThreadSanitizer](https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual) | ||
in combination with CTest and CDash, to identify data races and | ||
report these to a CDash dashboard. | ||
|
||
|
||
- [cxx-example](cxx-example/) |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
In this recipe, we reuse the approach from the previous example, but use | ||
[ThreadSanitizer](https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual) | ||
in combination with CTest and CDash, to identify data races and | ||
report these to a CDash dashboard. |