The test suite is one of the things that helps mdoc maintain backwards compatibility … without it, it would be impossible to determine if a change or new feature would break the large number of edge cases that can be represented in .NET APIs. Currently, a large portion of mdoc's tests are in the form of integration tests defined in a makefile … this makes cross-platform development a bit more difficult due to difficulty in getting this to run well on windows.
Goals
- Experiment with using MSBuild to convert tests from the current Makefiles (explore automated parsing/porting?)
- Experiment with using Experiment 1's model to recreate the integration tests as unit tests. This will greatly increase test suite speed, and make maintenance simpler if feasible.
- Consider using Xunit instead of Nunit to align with dotnet core.
The test suite is one of the things that helps mdoc maintain backwards compatibility … without it, it would be impossible to determine if a change or new feature would break the large number of edge cases that can be represented in .NET APIs. Currently, a large portion of mdoc's tests are in the form of integration tests defined in a makefile … this makes cross-platform development a bit more difficult due to difficulty in getting this to run well on windows.
Goals