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

Evangelize WDL conformance tests #4858

Closed
unito-bot opened this issue Apr 2, 2024 · 3 comments
Closed

Evangelize WDL conformance tests #4858

unito-bot opened this issue Apr 2, 2024 · 3 comments

Comments

@unito-bot
Copy link

┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1535

@unito-bot
Copy link
Author

➤ Adam Novak commented:

This is meant to include emailing particular WDL-related people, some of whom we mentioned in another issue thread (where?), and telling them about the conformance tests, and seeing if they are interested in using them to help test their WDL runners.

Lon and I are supposed to make some e-mail introductions to accomplish this.

@unito-bot
Copy link
Author

➤ Adam Novak commented:

  • Send out WDL conformance/performance tests to The WDL People: Mike Lin, Kyle Vernest the development lead for Terra
    • Lon to email Kyle and Steven
    • Adam to email Mike and Steven
    • Ask what these people think of the conformance tests we have and the idea of a universal set of tests for all the runners

@unito-bot
Copy link
Author

➤ Adam Novak commented:

stxue says that the OpenWDL people have a test generator. (Where?)

We should look at that and see if it’s better than the old hackathon test setup and if we can use that, and how it relates to our conformance test setup. Is it an alternative? Is it a kind of test that our runner could learn to run or a format we could express our tests in? Is it a way to generate tests, and if so from what and can it generate tests comparable to the ones we have?

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

1 participant