-
Notifications
You must be signed in to change notification settings - Fork 471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration from MSTest to NUnit #48
Conversation
…e downloaded here: https://visualstudiogallery.msdn.microsoft.com/0da0f6bd-9bb6-4ae3-87a8-537788622f2d Using AppDomain.CurrentDomain.BaseDirectory instead of Assembly.GetExecutingAssembly().Location to the determine the location of .docx files and other resources. This method is invariant under the test runner in use. Resources are set to "Copy if newer" to include them during build.
I've commited this but 9 tests failed ;) |
Test Name: GenerateHeadingTestDocument Result StackTrace: |
I guess replacing earlier version of _directoryWithFiles with new method didn't work as expected :-) |
I see. Does this happen with the NUnit 3 Test Adapter? Tests on my local VS install and AppVeyor all pass. |
Are you using NUnit 2 by any chance instead of NUnit 3? |
No. I've went to the link you mentioned in your post, run it in Visual Studio. It installed. Then I've tried running tests, it said it needs to get something from Nuget, I assume it did. And finally it gave error on 9 tests. I guess this is because the path to files is wrong as for some reason the "binary" executing the tests isn't in the same folder as the documents. |
@using (DocX document = DocX.Create(@"Document Header Test.docx")) on the other hand it's probably error because it can't create that document in the IDE directory... so this needs to be path outside of Visual Studio folder.. in other words .. all DocX.Create() fail because it tries to make those in "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE" - i don't see _directoryWithFiles being used there so most likely not a problem. |
Definetly seems to be a path issue. |
Migration to NUnit 3.4.1 to allow cross platform testing. Visual Studio Integration for NUnit can be downloaded here.
Notable changes are