Uh oh!
There was an error while loading. Please reload this page.
test: testing noAssert in buffer.write() - #10790
Conversation
Trott
commented
Jan 13, 2017
You should be able to run these tests for those functions as well. The issue with those functions will only manifest if you request something out of range. Since this test requests valid ranges with |
b174d57 to
16573abComparelarissayvette
commented
Jan 14, 2017
@Trott included those test cases |
Trott
commented
Jan 14, 2017
There was a problem hiding this comment.
This functionality is tested every time. Wouldn't it be enough to test this only once?
There was a problem hiding this comment.
Oh, yes, that's testing the wrong thing. It should test a legit alloc() call and an out-of-range call to the write function being tested. @larissayvette can you adjust it?
16573ab to
1c69e01CompareTrott
commented
Jan 26, 2017
Changes LGTM |
Trott
commented
Jan 26, 2017
Trott
commented
Jan 26, 2017
Single failure on SmartOS is unrelated, opened an issue for it. |
Add test to cover previously untested `noAssert` functionality in buf.write*() functions. PR-URL: nodejs#10790 Reviewed-By: Rich Trott <rtrott@gmail.com>
Trott
commented
Jan 26, 2017
Landed in 084acc8. |
Add test to cover previously untested `noAssert` functionality in buf.write*() functions. PR-URL: #10790 Reviewed-By: Rich Trott <rtrott@gmail.com>
Add test to cover previously untested `noAssert` functionality in buf.write*() functions. PR-URL: #10790 Reviewed-By: Rich Trott <rtrott@gmail.com>
jasnell
commented
Mar 8, 2017
This would need a backport PR to land in v4 |
Add test to cover previously untested `noAssert` functionality in buf.write*() functions. PR-URL: #10790 Reviewed-By: Rich Trott <rtrott@gmail.com>
Checklist
Affected core subsystem(s)
test
Test for
noAssertin buffer.write() files and inludedbuffer.writeDouble*andbuffer.writeFloat*as it was not present in the first commit