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
The test suite does not cover the getEncoded method of most messages, and the tests which call that method are heavily obfuscated, making it unclear what messages are being tested without debugging the tests as they run.
During debugging, aisDecodeEncode only tested getEncoded in messages 1, 3, 4, 5, and 24 (assuming the changes in #37), and the rest of EncodeTest only covered getEncoded in the above messages and message 12. Overall, only messages 1, 3, 4, 5, 6, 8, 12, 18, and 24 had their getEncoded methods called in any test methods.
The text was updated successfully, but these errors were encountered:
I would attempt to write a test covering this class, however as I mentioned the existing tests are heavily obfuscated and hardly documented, and as such I am unsure of how to make a test string to test a specific message. See decode_encode_messages.txt for an example of the test strings I would need to add to.
The test suite does not cover the
getEncoded
method of most messages, and the tests which call that method are heavily obfuscated, making it unclear what messages are being tested without debugging the tests as they run.During debugging,
aisDecodeEncode
only testedgetEncoded
in messages 1, 3, 4, 5, and 24 (assuming the changes in #37), and the rest ofEncodeTest
only coveredgetEncoded
in the above messages and message 12. Overall, only messages 1, 3, 4, 5, 6, 8, 12, 18, and 24 had theirgetEncoded
methods called in any test methods.The text was updated successfully, but these errors were encountered: