Add Test Suite about openlivewriter

[MitchMilam]

@writeline, @willduff I can create an initial test project and start adding tests for CoreServices, if you wish.

Any part of CoreServices you feel should be handled first?

[rebornix]

IMO, another important part that should be test against ASAP is BlogClient. People are eager to add new blog providers for OLW, but they have no idea how it works as lack of design spec. Test suite can help them understand.

There is no need to write tests for all blog client for now, just one sample for a specific provider ( eg, wordpress ). Then we can ask people to write their own when bringing new providers.

Personally, I'm looking forward to see what framework we'll use, Nunit, VS Test Framework or something else.

[willduff]

Thanks for volunteering @MitchMilam. We already have an OpenLiveWriter.UnitTest.csproj, but it doesn't build or run yet. Please start by just getting that project to build with 1 dummy test that builds and runs.

Though, there is also the further question of what test runner should we use? Any suggestions?

Once we have the project building and running, we'll hook it up to our continuous integration server. Then we can add more tests.

@MitchMilam if you want to take this on, please reply back and I will assign the issue over to you for now. Thanks!

[MitchMilam]

@willduff No problem. Assign it to me. Yes, I saw that project and will take a look.

Let's stick with mstest since we know everyone will have that as part of VS.

[MitchMilam]

@willduff OpenLiveWriter.UnitTest is not a testing project, but a standard library project. That means we can't add unit tests to it.

Would you like me to create a new testing project?

PS. I had no trouble building it.

[gep13]

@MitchMilam said...
@willduff OpenLiveWriter.UnitTest is not a testing project, but a standard library project. That means we can't add unit tests to it.

@MitchMilam that sounds like you are trying to use MSTest, which I believe needs a specific Project Type GUID in order to light up the Unit Test integration within Visual Studio. Other testing frameworks, like NUNit or XUnit do not have this requirement. Instead, they work with a standard class library project.

[MitchMilam]

Thanks @gep13, that is probably it.
@willduff just let me know which testing technology you want to use and I'll get it hooked up.

[lisardggY]

As part of my WordCounter patch, I've added several tests to the OpenLiveWriter.UnitTest project. Currently I've used MSTest because it requires the least amount of 3rd party tool integration. Unlike the above, I've found there really isn't a problem using MSTest with the current Project type - I've just added a reference to Microsoft.VisualStudio.QualityTools.UnitTestFramework and decorated my tests with the right attribute, and VS 2015 Community picked up on it and shows the tests in the test explorer.

It does seem, however, that the AppVeyor build doesn't actually execute them, which is a shame.

If we want to switch test frameworks, this would be a good time before more are added. If not, it would be a good time to add them to the build process. :)