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
Add optional overrides for warning settings that will be used when running tests. After some experimentation, I believe these settings can be applied in GutRunner before any other gut scripts or test scripts are loaded. This would help resolve confilicts with users' desired settings and settings that make GUT and GutTest scripts, runnable/less noisy.
Config File Changes
The config file would get an optional "gdscript_warnings" section. Any settings specified in this section will override the settings used by the project prior to loading the rest of GUT. The values for the warnings should be either the numeric value (0/1/2) or a string ("ignore"/"warn"/"error", case insensitive).
The GutPanel should have a section, or possibly a popup dialog, that allows you to set these values. All settings will be displayed, and the default value is to not override. The current project settings should be displayed next to a drop down for the override value. Through the gui, you would have 4 possible values: do no override, ignore, warn, error. If a popup is used to set the values, then it would be good to display the number of settings that are overridden in the settings panel.
A popup might be required, since I'm not sure if we can detect when project settings are changed. If we cannot, then we will end up stale data in the panel. A popup can refresh values when it is shown.
Technically we could display AND set project settings from the panel/popup. This is probably a bad idea as it might lead to accidental changes or confusion. These values shouldn't be changing a lot so it doesn't add much to be able to change these project settings from the GutPanel.
Command Line Changes
No parameters will be added to the command line, I don't think it adds any value. You'll have to set the values in a gut_config.json file.
The text was updated successfully, but these errors were encountered:
Versions
Probably both Godot 3 and 4, at least 4.
The Feature
Add optional overrides for warning settings that will be used when running tests. After some experimentation, I believe these settings can be applied in
GutRunner
before any other gut scripts or test scripts are loaded. This would help resolve confilicts with users' desired settings and settings that make GUT andGutTest
scripts, runnable/less noisy.Config File Changes
The config file would get an optional "gdscript_warnings" section. Any settings specified in this section will override the settings used by the project prior to loading the rest of GUT. The values for the warnings should be either the numeric value (0/1/2) or a string ("ignore"/"warn"/"error", case insensitive).
Example:
GUI Changes
The GutPanel should have a section, or possibly a popup dialog, that allows you to set these values. All settings will be displayed, and the default value is to not override. The current project settings should be displayed next to a drop down for the override value. Through the gui, you would have 4 possible values: do no override, ignore, warn, error. If a popup is used to set the values, then it would be good to display the number of settings that are overridden in the settings panel.
A popup might be required, since I'm not sure if we can detect when project settings are changed. If we cannot, then we will end up stale data in the panel. A popup can refresh values when it is shown.
Technically we could display AND set project settings from the panel/popup. This is probably a bad idea as it might lead to accidental changes or confusion. These values shouldn't be changing a lot so it doesn't add much to be able to change these project settings from the GutPanel.
Command Line Changes
No parameters will be added to the command line, I don't think it adds any value. You'll have to set the values in a
gut_config.json
file.The text was updated successfully, but these errors were encountered: