Xamarin support

[maosierra]

Why you remove the xamarin support? All was ok to yesterday. Please come back and dont remove that. Thanks.

[axodox]

Sorry for that, it was not intentional. That being said I was not aware that my plug-in worked with xamarin at all so never tested with it - it was basically accidental. The 1.1. version brings support to NUnit and Xunit. If Xamarin does not work you might just get the source and check it, it might be just a small issue. After all this is all free and open source... You can also switch to legacy branch to continue using the old version, or you can just go to releases here and download them manually.

The reality is that I have realized that maintaining this plug-in is taking over my free time entirely for half a year now, and people can be very harsh when something they need happen to not work and give one stars at marketplace at once, without even allowing me to respond or address the issue. My original goal was to make a free plug-in for testing for my own use, but I decided to share it so others may use it, I also added support for XUnit and NUnit although I have never used these myself - and it took a lot of time and I needed to release it at some point. But I have no time to support everyone. So there is that...

[maosierra]

Sorry for one star, I only wanted your attention. You have 5 stars now! thank you for your help.

For the other hand, I want to be part of your team for this. Let me help you :)

[axodox]

I have sent Skype contact info in e-mail. While there is no documentation for the code, it is not a large codebase. For this issue I can give you the following info:

• Before AxoCover 1.1 I used the mstest and the vs test console, this provided basic functionality, but the implementation was quite messy in some cases, and limited what I can do.
• In AxoCover 1.1 I use my own runner called AxoCover.Runner, this is built upon the forked versions of the visual studio test adapters, allowing me direct access to the features of different test frameworks while also reducing the amount of code, as I can reuse the adapters. The plan is to merge back the forked changes after a while so there is no need to maintain these - although that is not much work for now.

I do not have Xamarin on my machine - never used it before to be honest, but I would start the investigation of this issue the following way:

• Check the TestProvider class, which is responsible for discovering the tests. There could be several issues here: it might not realize that the project is a TestProject (around line 68), or it fails to discover the tests in the assembly (around line 127).
• If it discovers the assembly but the AxoCover.Runner returns no tests from it, you need to check the output window for errors, you might also add a Debugger.Launch call in AxoCover.Runner, in TestDiscoveryService.DiscoverTests(...).
• Should these above work properly you will now see the list of tests, if they fail to execute, you need to similarly to the above check the AxoTestRunner, and the TestExecutionService classes. I would avoid adding more details, since from here you can step through the code to see what is going on in detail.

I hope this information will help you to analyze the issue.