Move unit configs to another config file

letalboy / testrium

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.

0 stars 1 forks source link

Move unit configs to another config file #9

Open letalboy opened 1 week ago

letalboy commented 1 week ago

Configuration File:
- Define and configure individual units.
Unit-Specific Tests and Behaviors:
- Each unit has its own set of tests and behaviors for strict validation.
Completed Steps Mechanism:
- Implemented to check and validate completed steps in each unit's configuration.
Future Enhancements:
- Add behaviors such as disabling units.
- Create links between units.
Goal:
- Facilitate testing of complex features and behaviors easily.

letalboy commented 3 days ago

Units should look something like this:

["Unit Name"]
init = 0
events = ["event1", "event2", "event3"]
use_setup = false
in-except = "Resume-ALL"
unity_depencies = ["Host", ]

letalboy commented 3 days ago

And configs:

["Configs"]
units = ["unit1", "unit2"]
debug-modes = ["DEBUG", "INFO", "WARNING", "EXCEPT"]
test-modes = ["DEBUG"]
repeat = 0
use-ai = false
diagnostics = true
detect-bad-behavior = true
save-resume = true
gen-metrics = true
save-metrics = true
save-scores = true

Were analitics = true becomes gen-metrics and save-analitics = true becomes save-metrics = true which is better to read and makes more sense. We can also change ´save-performance´ to ´save-scores´ while it still being a boolean in this case.

But further enhacements can be done if required.

letalboy commented 2 days ago

@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.