-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Migrate test suite to Pytest #164
Comments
I could work on this, if you want me to ? |
That would be great! Most of this issue will just be adding If you need to me to set up the changes to the actions workflow, I can do that for you. Nobody likes messing with workflow files. |
sure |
Any progress here? |
done with the changes
…On Sat, May 11, 2024, 10:01 PM Peter ***@***.***> wrote:
Any progress here?
—
Reply to this email directly, view it on GitHub
<#164 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUDWDJG764DAMJ4TCO7YK3DZBZBXBAVCNFSM6AAAAABHHNJG4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVHE2DOOBQGQ>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Great! Go ahead and make a PR, I'll update the workflows if you haven't already |
before i make the PR is there anything to mind or any suggestion ? |
Do you want me to change something in the readme or any doc file ? |
Nope, I got it. |
Description:
Ward has been great, but using it over Pytest makes #109 more or less impossible. Pytest and Ward are pretty similar, but most developers are familiar with Pytest anyway, so this change will probably be for the best.
The text was updated successfully, but these errors were encountered: