-
-
Notifications
You must be signed in to change notification settings - Fork 240
Unit tests for parser & composer status codes #792
Copy link
Copy link
Open
Labels
C-testscategory: Writing or improving testscategory: Writing or improving testseasy hacksSolution requires minimal project contextSolution requires minimal project contexthelp wantedLooking for contributorsLooking for contributors
Metadata
Metadata
Assignees
Labels
C-testscategory: Writing or improving testscategory: Writing or improving testseasy hacksSolution requires minimal project contextSolution requires minimal project contexthelp wantedLooking for contributorsLooking for contributors
Type
Fields
Give feedbackNo fields configured for Maintance.
Projects
StatusShow more project fields
Help wanted
This is a follow-up for #766 and #737.
Add simple tests to check how status codes returned from implementations of
IParserandIComposer:Add unit tests for rtp::Parser, rtp::Composer, fec::Parser, fec::Composer for the cases when they return non-OK status.
Add unit tests for components that use parsers and composers. In tests, check that the component properly forwards error code from parser/composer to the caller.
For example, a test makes Composer to fail with StatusNoMem, and check Shipper::write() returns StatusNoMem.
Classes to cover: