You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our test coverage consists of the test cases under test/addons-abi, which while better than nothing are far from exhaustive. They don't test error conditions at all, and several APIs are completely uncovered. We need to either expand these test cases or build some new test infrastructure. A problem with the way the current tests work is there isn't any way to assert in the C code -- all assertions are in the JavaScript code.
And then, it would be really nice to get code coverage to measure how much of the NAPI implementation code is being covered by the tests.
The text was updated successfully, but these errors were encountered:
We need better unit test coverage of NAPI APIs.
Currently our test coverage consists of the test cases under
test/addons-abi
, which while better than nothing are far from exhaustive. They don't test error conditions at all, and several APIs are completely uncovered. We need to either expand these test cases or build some new test infrastructure. A problem with the way the current tests work is there isn't any way toassert
in the C code -- all assertions are in the JavaScript code.And then, it would be really nice to get code coverage to measure how much of the NAPI implementation code is being covered by the tests.
The text was updated successfully, but these errors were encountered: