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
Currently, our tests are executed from the combination of the abstract test description (ITF trace like these, often generated by model checker) and the reactor (like this), specifying how the abstract description is concretized into a test.
Very often, users are hesitant to include different formalisms into their repositories.
I am proposing to add an option to atomkraft to generate tests in the native language of the project.
Concretely, I'd like Atomkraft to generate e2e tests written in Go.
These tests could follow the structure of existing Cosmos-SDK tests (example).
The option could be added to atomkraft test trace, or exist as a separate command e.g. atomkraft trace ...
The text was updated successfully, but these errors were encountered:
Currently, our tests are executed from the combination of the abstract test description (ITF trace like these, often generated by model checker) and the reactor (like this), specifying how the abstract description is concretized into a test.
Very often, users are hesitant to include different formalisms into their repositories.
I am proposing to add an option to atomkraft to generate tests in the native language of the project.
Concretely, I'd like Atomkraft to generate e2e tests written in Go.
These tests could follow the structure of existing Cosmos-SDK tests (example).
The option could be added to
atomkraft test trace
, or exist as a separate command e.g.atomkraft trace ...
The text was updated successfully, but these errors were encountered: