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
In order to properly test the entry parser, we need to make sure that even if a future version of gonx (the parsing library) happens to be sending us invalid data, we handle the errors correctly.
This can be easily done by writing tests that do not use gonx but simply programmatically instantiate gonx.Entry objects and fill them manually with erroneous data.
However, since this is tedious and that I own the version of the library that I use, I know that these tests are most likely not needed for an MVP so I will tag this as a potential future improvement.
The text was updated successfully, but these errors were encountered:
In order to properly test the entry parser, we need to make sure that even if a future version of gonx (the parsing library) happens to be sending us invalid data, we handle the errors correctly.
This can be easily done by writing tests that do not use gonx but simply programmatically instantiate gonx.Entry objects and fill them manually with erroneous data.
However, since this is tedious and that I own the version of the library that I use, I know that these tests are most likely not needed for an MVP so I will tag this as a potential future improvement.
The text was updated successfully, but these errors were encountered: