Skip to content

Commit 511ad67

Browse files
committed
Make README easier to read
1 parent 170f31a commit 511ad67

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -62,13 +62,13 @@ environment:
6262
When the DevContainer session is ready, follow these steps to exercise the
6363
environment's C++ development features.
6464

65-
- Configure the build
65+
- **Configure the build**
6666

6767
The CMake Tools extension has a build-kit selector in the VSCode status bar.
6868
Choose GCC 11.4.0. The extension runs the CMake configure step to the
6969
build/build-vscode-cmake-tools directory.
7070

71-
- Build all and use the test explorer
71+
- **Build all and use the test explorer**
7272

7373
Choose the `all` build target (in the status bar selector).
7474
Be careful of a trap...the status bar may have both `default build target`
@@ -85,7 +85,7 @@ environment's C++ development features.
8585
in the screen-shot above, the test explorer is moved to VSCode's secondary
8686
side bar, on the right.
8787

88-
- Try the code editor
88+
- **Try the code editor**
8989

9090
Open src/lib/StatisticsAccumulator.cpp from the file explorer.
9191

@@ -105,7 +105,7 @@ environment's C++ development features.
105105

106106
Ctrl-S auto-formats C++ and CMake files according to the project standards.
107107

108-
- Examine code coverage
108+
- **Examine code coverage**
109109

110110
Switch from `all` to the `statistics_coverage_report` target and build it.
111111

@@ -116,22 +116,22 @@ environment's C++ development features.
116116
to add coverage annotation to the C++ code editor in the form of colored bars
117117
by the line numbers.
118118

119-
- Test the tests
119+
- **Test the tests**
120120

121121
A custom build task provides [mutation testing][2] for the project, helping
122122
find gaps in the tests, even when code coverage is all green.
123123

124124
Select `Run Build Task` from VSCode's `Terminal` menu to create a
125125
[full mutation testing report][3] by applying no diff filter.
126126

127-
- Look for memory leaks
127+
- **Look for memory leaks**
128128

129129
A custom build task runs the unit-test program under valgrind and logs the
130130
results to a [valgrind report][4].
131131

132132
Select `Run Build Task` from VSCode's `Terminal` menu to execute the task.
133133

134-
- Use the code sanitizers
134+
- **Use the code sanitizers**
135135

136136
A custom build task creates a sanitizer testing report using the compiler's
137137
sanitize flag. It has options for the address sanitizer and the

0 commit comments

Comments
 (0)