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: sharing/index.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,7 +96,7 @@ For interactive testing work, use [TestEnv.jl](https://github.com/JuliaTesting/T
96
96
\vscode{
97
97
98
98
The Julia extension also has its own testing framework, which relies on sprinkling "test items" throughout the code.
99
-
See [TestItemRunner.jl](https://github.com/julia-vscode/TestItemRunner.jl)and [ReTestItems.jl](https://github.com/JuliaTesting/ReTestItems.jl)for indications on how to use them optimally.
99
+
See [TestItemRunner.jl](https://github.com/julia-vscode/TestItemRunner.jl) for indications on how to use them optimally.
100
100
101
101
}
102
102
@@ -108,6 +108,7 @@ If you want to have more control over your tests, you can try
108
108
*[ReTest.jl](https://github.com/JuliaTesting/ReTest.jl) to define tests next to the source code and control their execution.
109
109
*[TestSetExtensions.jl](https://github.com/ssfrr/TestSetExtensions.jl) to make test set outputs more readable.
110
110
*[TestReadme.jl](https://github.com/thchr/TestReadme.jl) to test whatever code samples are in your README.
111
+
*[ReTestItems.jl](https://github.com/JuliaTesting/ReTestItems.jl) for an alternative take on VSCode's test item framework.
0 commit comments