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.

Sign up for GitHub

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

Jump to bottom

Run integration tests on packages #37

Closed
CharliePoole opened this issue Mar 24, 2020 · 1 comment · Fixed by #38
Closed

Run integration tests on packages #37

CharliePoole opened this issue Mar 24, 2020 · 1 comment · Fixed by #38
Assignees
@CharliePoole
Labels
Build Normal Priority
Milestone
3.9.0

Comments

@CharliePoole
Copy link
Member

Integration tests (V2 tests) are currently run in the bin directory immediately after unit testing. They would be more useful and effective if run after packaging, using the content of the packages themselves. This will also help with issue #1.
@CharliePoole CharliePoole changed the title Run integration after packaging Run integration tests on packagegs Mar 24, 2020
@CharliePoole CharliePoole self-assigned this Mar 24, 2020
@CharliePoole CharliePoole added this to the 3.9 milestone Mar 24, 2020
@CharliePoole CharliePoole changed the title Run integration tests on packagegs Run integration tests on packages Mar 24, 2020
@CharliePoole CharliePoole mentioned this issue Mar 24, 2020
Merged
@CharliePoole
Copy link
Member Author

🎉 This issue has been resolved in version 3.9.0 🎉

The release is available on:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CharliePoole CharliePoole

Labels
Build Normal Priority
Projects
None yet
Milestone
3.9.0
Development

Successfully merging a pull request may close this issue.

Perform integration tests on packages nunit/nunit-v2-framework-driver
1 participant
@CharliePoole