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

Refactor tests and sites #192

annawoodard opened this Issue Apr 3, 2018 · 1 comment


None yet
1 participant
Copy link

annawoodard commented Apr 3, 2018

As suggested by @kylechard

We have different tests for each executor (test_ipp, test_threads, and different sites (test_sites). We should refactor the tests such that there is one core set of tests and we cycle through the various executors and sites to run each one.

@annawoodard annawoodard changed the title Refactor tests Refactor tests and sites Apr 5, 2018


This comment has been minimized.

Copy link
Collaborator Author

annawoodard commented Apr 5, 2018

The same can be done with sites. I think we should aim for a core set of tests; then we can maintain a set of site configurations which we can loop through in addition to looping through the possible executors, in order to test all the combinations.

@annawoodard annawoodard self-assigned this Apr 23, 2018

@annawoodard annawoodard added this to the Parsl-0.6.0 milestone May 9, 2018

@annawoodard annawoodard referenced this issue May 11, 2018


Tests #128 #272

@yadudoc yadudoc closed this in #272 May 16, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.