multipart/form-data transmission requires modifying the Content-Type header with a boundary section identifier, and as such a custom content handler would not have previously had access to the running test case it was working on. This should hopefully be useful for other custom content handlers in the future.
Please let me know if the documentation could be better worded or if the check for the return of dumps in assert_in_or_print_output seems unnecessary (lines 547-551 of commit d71a477).
This resolve #211.
multipart/form-datatransmission requires modifying theContent-Typeheader with aboundarysection identifier, and as such a custom content handler would not have previously had access to the running test case it was working on. This should hopefully be useful for other custom content handlers in the future.Please let me know if the documentation could be better worded or if the check for the return of
dumpsinassert_in_or_print_outputseems unnecessary (lines 547-551 of commit d71a477).