save-cli
save-cli copied to clipboard
saveourtool
Universal test framework for cli tools [mainly for code analyzers and compilers]
The save gives warnings for warnings from the expected file in FixAndWarn plugin in diktat smoke test It is possible that the warn plugin is being run on an expected...
Probably we will need to delete all tests and simply test real scenarios on the executable save-cli
Currently, `save-cli` can only fail a test if there're unmatched warnings (`ExecutionResult.code` is preserved but never read). Yet, we currently cannot differentiate between: - the case when the number of...
Seems, that Sarif supports two options for identify the place of warning/fixes via Region object: 1) By indicating the lines and columns 2) By indicating the byteOffset and byteLength For...
For `warn-plugin` we calculate and store count of matched, expected and other warnings. Based on this data we can calculate various scores and use them in save-cloud. For `fix-plugin` a...
Evaluated tool can return a full path to tested file, need to be able to handle it. Right now, a workaround for regex for file name can be applied: `.*[\\\\\\/](.*)`,...
We need to provide a common template for `execCmd`: ``` java -jar ktlint -R diktat -F %%Test%% --debug ``` SO we won't need `execFlags` anymore.
We have `com.saveourtool.save.core.config.TestConfigSections` in `save-cli`, which stores in common module. We store a simple name of class of plugin in `pluginName` in `com.saveourtool.save.entities.Test`. We don't have access to plugin classes...
`GenericConfig` looks like a common class for all plugins. We can move all properties form `GenericConfig` to `*PluginConfigs` and use them during executing a specific plugin instead of fetching 2...
Currently we create Plugin for all PluginConfig and then discover test files to exclude plugin config for hierarchy. This logic is common for all plugins and can be extracted to...
Metadata
Owner
Metadata
Universal test framework for cli tools [mainly for code analyzers and compilers]