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
Hackathon coordination #1269
Comments
Hi Paul, that sounds great! Shall we reopen these two issues? |
awesome! Yes if we could try to get #1077 done first, that would make everything else simpler because we wouldn't have so many false positives on CI |
Hi all! I'll join in around 4pm PST to work on #892 |
@gurpreetatwal Sweet! Looking forward to it. I might be off, but I think that @gr2m should be on around then. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you! |
Hi! I was going to respond to #1268 (comment) but realized that is probably not the best place to have a discussion. 😄
I've used Nock in a handful of projects, though most heavily in Shields abstracted through our test framework (see badges/shields#927) which uses IcedFrisby and a nock plugin.
I made a couple small contributions a while back and merged a few others. My main interest is in addressing fundamental usability challenges e.g.:
Also the challenges that affect Shields contributors – who often have not written tests with mock responses and sometimes haven't written tests at all! – like troubleshooting matching.
I'm happy to jump in to work on tests if it can help move things in that direction!
The text was updated successfully, but these errors were encountered: