vscode-cmake-tools/test/helpers
Garrett Campbell 46f2d16e31
Refactor and improve test infrastructure, starting with automated version validation tests (#4126)
* renamed to end-to-end-tests and moved backend unit tests to unit-tests folder

* create folder for kits code, refactor imports to use @cmt and @test

* move variants into the kits folder

* refactor into better folder structure, still more to go

* Initial refactor making presets validation unit testing possible.

This seems to work well so far, I have v1-v3 presets tested, with some
more refactors regarding error reporting to come. However, the
design/infrastructure refactor seems to be allowing us to unit test
validation.

* implemented Presets version validation automated testing

* Added version testing for presets v1-9.

This adds testing for our version validation for all Presets versions
currently supported.
It creates presets on the fly and ensures that we correctly get errors,
or don't, depending on the setup and what fields are present with what
versions.

* fix workflows

* Ensure that we correctly initialize the presetsParser class

* refactor imports

* refactor imports

* more import fixes

* imports in projectStatus

* missed one

* workflow imports

* added comment about definite assignment

* add comments

* fix launch file to make sure breakpoints happen

* fix syntax error
2024-10-21 11:02:35 -07:00
..
cmake Refactor and improve test infrastructure, starting with automated version validation tests (#4126) 2024-10-21 11:02:35 -07:00
test Calling build targets from CMake Project Outline always builds default target if useTasks option is set (#2780) 2023-01-10 17:23:04 +00:00
testprogram Preset file expansion on open/save and expansion validation (#3905) 2024-07-24 15:52:00 +00:00
vscodefake Calling build targets from CMake Project Outline always builds default target if useTasks option is set (#2780) 2023-01-10 17:23:04 +00:00