What is the fastest possible way to run a Julia test suite (and also get test coverage)? Normally I call julia --startup-file=no --code-coverage=user --project=. -e 'using Pkg; Pkg.test(coverage=true)' julia --startup-file=no coverage.jl ▶ where coverage.jl is: However, this takes 4 minutes in to…

Thanks! Okay I think I got everything working. Thanks to everyone for your help. Here’s my new workflow for getting rapid-fire code coverage updates: Start Julia with --code-coverage=@ to only track the current package you are developing. julia \ --code-coverage=@ \ --code-coverage=lcov…

Have you seen the TestItems.jl and TestItemRunner.jl packages? [image] Prerelease of new testing framework and test run UI in VS Code VS Code I just pushed out a new release of the Julia VS Code extension (1.7.6) to everyone that includes a preview of our new …

[image] mkitti: TestItems.jl I hadn’t, thanks. At the moment there are two ways to run @testitems: with the integrated test UI in the Julia VS Code extension, or with this package TestItemRunner.jl. In both cases test item detection is based on syntactic analysis, i.e. no code from your pac…

See the following thread? [image] Code coverage with Coverage.jl in vscode New to Julia I just tried Coverage.LCOV.write(filepath, coverage) does not work. Here is the complete workflow that worked for me Julia line coverage information in VS Code First gene…

That thread is what my coverage.jl file is from actually! (see coverage.jl file on my first post) What I’m wondering is whether you can generate the *.cov files from this new test package or not.

Just to clarify, my main question is: what is the fastest way to re-generate code coverage from my test suite after I make a code change?

That might also depend a bit on how the test suite is set up, that is, for example, how much the tests are modularised – for example with the already mentioned TestItemRunner and VS Code. I try to write tests per feature that are “standalone” in the sense that they also would run via include – or i…

Adding coverage support in the VS Code UI of the test item framework is something I’d love to do, but that is currently blocked by More fine-grained coverage output control · Issue #50215 · JuliaLang/julia · GitHub . One can get coverage with the CI runner, but then one doesn’t get any of the benefi…

Thanks for sharing your workflow. Here’s more context: this is my current test folder, which as you can see, is split up into small files that test a specific feature or module: DynamicExpressions.jl/test at 749385a1183b4ea8cd4145c914b08b6c8d9774c6 · SymbolicML/DynamicExpressions.jl · GitHub I hav…

(Edit: resolved, see next post)

Did some digging on More fine-grained coverage output control · Issue #50215 · JuliaLang/julia · GitHub . Seems like I need to call the C function :jl_write_coverage_data to write the coverage data earlier. Although seems like it is not exported for some reason (?): julia> ccall((:jl_write_coverage…

Workflow for faster testing of Julia packages?

General Usage

mkitti May 4, 2024, 3:52pm 4

See the following thread?

Topic		Replies	Views
Tests with coverage in VSCode General Usage testing , vscode	8	525	August 5, 2024
New stable features for the test item framework VS Code announcement	18	1058	August 25, 2024
Prerelease of new testing framework and test run UI in VS Code VS Code	53	7602	February 9, 2023
Local GUI coverage General Usage question , testing	9	2519	September 13, 2021
No coverage files generated outside project on Julia 1.9 General Usage testing , coverage	1	182	August 30, 2023

Workflow for faster testing of Julia packages?

Related topics