Testrium is the pinnacle of testing libraries, designed to elevate your testing experience to heavenly heights. Seamlessly integrating the power and flexibility of modern testing frameworks, ElysianProbe provides an unparalleled suite of tools to ensure your code is flawless.
The configs file needs to have a structure validation so that we can check if the structure is valid or not, this will prevent misconfigure the test, another thing that we can do is add command to the CLI that allows to generate a template of the configs file, something like:
testrium gen config-template
This will allow to have a better way to create templates for a test config, this will facilitate to users follow the structure required. But never the less we still need to do the verification of the config structure to ensure this follows the requirements for basic tests and add boundaries inside the CLI to ignore when something isn't present that isn't stric relevant for the basic functionality, what will allow for minimal configs file.
To-Do List
Structure Validation
Implement validation for the configuration file structure.
Ensure the structure is checked for validity to prevent misconfiguration.
CLI Command for Template Generation
Add a command to the CLI to generate a template configuration file:
testrium gen config-template
Provide users with a standardized template to follow the required structure.
Config Structure Verification
Verify the configuration file structure to ensure it meets the requirements for basic tests.
Implement checks and validations within the CLI to confirm adherence to the required structure.
Handling Non-Essential Elements
Add boundaries within the CLI to ignore non-essential elements that are not strictly relevant for basic functionality.
Allow for minimal configuration files by ignoring irrelevant parts.
@beqm See if this was already solved in #15 integration; some parts of your progress leaked into the development branch through this PR implementation, so it needs verification.
The configs file needs to have a structure validation so that we can check if the structure is valid or not, this will prevent misconfigure the test, another thing that we can do is add command to the CLI that allows to generate a template of the configs file, something like:
This will allow to have a better way to create templates for a test config, this will facilitate to users follow the structure required. But never the less we still need to do the verification of the config structure to ensure this follows the requirements for basic tests and add boundaries inside the CLI to ignore when something isn't present that isn't stric relevant for the basic functionality, what will allow for minimal configs file.
To-Do List
Structure Validation
CLI Command for Template Generation
Config Structure Verification
Handling Non-Essential Elements