Failing Unit Tests in nanoframework.System.Net.Http #1464
Comments
josesimoes
added
up-for-grabs
good first issue
Priority: Low
Area: Class Libraries
and removed
Status: Waiting triage
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Library/API/IoT binding
nanoFramework.System.Net.Http
Visual Studio version
No response
.NET nanoFramework extension version
No response
Target name(s)
No response
Firmware version
No response
Device capabilities
No response
Description
There are some Unit Tests failing in nanoframework.System.Net.Http.
Namely:
HttpUtilityTest.UrlEncodeTestStreamContentTestThese are not new issues related to nanoframework/System.Net.Http#416, but have been there before.
Broken unit tests should be verified (if they point to an actual issue), then fixed or deleted.
How to reproduce
No response
Expected behaviour
No response
Screenshots
No response
Sample project or code
No response
Aditional information
No response
The text was updated successfully, but these errors were encountered: