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

Create scenario player for the test network #652

Closed
4 tasks
konradkonrad opened this issue Jun 14, 2017 · 2 comments
Closed
4 tasks

Create scenario player for the test network #652

konradkonrad opened this issue Jun 14, 2017 · 2 comments
Assignees

Comments

@konradkonrad
Copy link
Contributor

konradkonrad commented Jun 14, 2017

We want a "scenario player" for repeatable directed case testing on the test network. The scenario player should not only allow for planned execution, but also include assertions and reporting of expected outcomes (and failures). The reporting may or may not be resolved by the same means as the general monitoring of the test network #650.

Scenarios

  • interwoven mediated transfers of different tokens to different targets
  • interwoven receiving and sending of mediated transfers
  • interwoven receiving and sending of mediated and direct transfers
  • graceful handling (rerouting) when mediators disappear
  • timeout cases, e.g. the initiator of a mediated transfer does not reveal the secret after being contacted by the target

Tasklist

  • create or chose a framework for scenario creation (descriptive or programmatic)
  • define or chose an outcome assertion description (descriptive or programmatic)
  • create a "player" for running the scenario (needs timed "orchestration" of several nodes)
  • create outcome reporting
@LefterisJP
Copy link
Contributor

This is taken out of the initial release of the dev preview.

@LefterisJP LefterisJP modified the milestones: Developer Preview, Next minor release Sep 12, 2017
@LefterisJP LefterisJP added the 3 label Sep 14, 2017
@czepluch czepluch removed this from the Next minor release milestone Nov 16, 2017
@andrevmatos andrevmatos self-assigned this May 29, 2018
@hackaugusto hackaugusto removed the 3 label Jun 20, 2018
@ulope ulope mentioned this issue Jun 20, 2018
3 tasks
@ulope
Copy link
Collaborator

ulope commented Sep 25, 2018

We finally closed this in #2524 🎉

@ulope ulope closed this as completed Sep 25, 2018
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

6 participants