-
Notifications
You must be signed in to change notification settings - Fork 468
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
Comprehensive node-addon-api test suite #163
Comments
I'm working on the documentation and it would be helpful for my work to have test cases for Reference. |
@anisha-rohra can you prioritize adding the test for Reference ? |
@jschlight talked to @anisha-rohra earlier in the week to get her up to speed on Reference, should be working on it now. |
@mhdawson, @anisha-rohra Can I also work on this issue together? (but I don't want to get in the way) |
Also, can we split a large test into smaller tests? |
@romandev absolutely. Splitting out if there are a lot of tests also makes sense to me. To grab one of the sections, just post a comment here with the ones you are working on so that other people wont' work on them at the same time. We'll try to periodically update the top part with that information as well. |
@mhdawson Sure, if so, I'll start to write a test for Object first. It has been marked as complete but still missed many APIs. |
@romandev sounds good. |
Is anyone working on |
@romandev I'm taking a look at it at the moment! Should be done in a couple of days. |
@romandev I know you contributed a number of tests for Object. Should I mark it as complete above ? |
@mhdawson Yep, I think we can mark it as complete :) Thank you. |
@NickNaso I think that makes sense a as more detailed list. |
Would appreciate any input on test cases that need to added and/or removed from this list, attempting to make it as comprehensive as possible!
The text was updated successfully, but these errors were encountered: