Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A protocol and a prototype for MBT-core <-> MBT-Rust communication #11

Closed
andrey-kuprianov opened this issue Feb 25, 2021 · 1 comment
Closed

Comments

@andrey-kuprianov
Copy link
Contributor

Following the description outlined in #2 (comment)., we need to split the jobs of generating and executing tests into MBT-core and MBT-Rust plugin. For that we need to devise a simple protocol for the communication of MBT-core and MBT-Rust, and do a prototype implementation of it.

As a testing ground for the protocol, it is proposed to take the work done in IBC-rs#701, and to separate it into MBT-Core and MBT-Rust:

  • MBT-core will have the task of running TLC on the provided spec, and generating tests from it. It will run as a daemon listening for local requests.
  • MBT-Rust will run the given test executor implementation on the tests obtained via communication with MBT-core.

In the first iteration we should not care too much about the particularities of the implementation, but to focus on obtaining a minimal working prototype that has MBT-core and MBT-Rust separated and communicating via a protocol. This will be refactored later for a better code structure.

@andrey-kuprianov andrey-kuprianov changed the title Devise a protocol and a prototype for MBT-core <-> MBT-Rust communication A protocol and a prototype for MBT-core <-> MBT-Rust communication Feb 25, 2021
@danwt
Copy link
Contributor

danwt commented Jan 10, 2022

Closed as outdated. Please reopen if this is a mistake.

@danwt danwt closed this as completed Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants