Bug 59016 - Empty name attribute in NunitLite test results file
Summary: Empty name attribute in NunitLite test results file
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Greg Munn
URL:
Depends on:
Blocks:
 
Reported: 2017-08-24 15:29 UTC by Naresh Thandu
Modified: 2017-10-13 17:35 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Results file (1.43 KB, text/xml)
2017-08-24 15:29 UTC, Naresh Thandu
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Naresh Thandu 2017-08-24 15:29:02 UTC
Created attachment 24403 [details]
Results file

Hello,

Using Xamarin Android Nunitlite to run the automated tests using the adb shell instrumentaion command.

It's executing the tests and generating the results file. I can pull and see the results but name attribute on 'test-results' is empty. It's causing issue in publishing the build results from VS online.

I have used the following command to execute the tests on emulator

adb shell am instrument -w Com.Droid.UnitTests/com.droid.unittests.TestInstrumentation

Following is the resu
Comment 1 Jon Douglas [MSFT] 2017-08-24 15:50:45 UTC
Does this happen with every test that generates a results file? Secondly, which nunit version are you using? nunit2 has a legacy XML format, and nunit3 has a nicer new format.

Perhaps you might be able to find more information pertaining to your issue here:

https://github.com/nunit/docs/wiki/NUnitLite-Options

Additionally, if you don't want to use the baked in testing items, I would highly recommend nunit.xamarin as an nunit 3 test runner:

https://github.com/nunit/nunit.xamarin

To further investigate this bug, can you please provide the following?

1. A reproduction case (Steps for us to replicate, or a project we can use to replicate the behavior described)
2. Your version information

Thanks in advance!
Comment 2 Naresh Thandu 2017-08-24 16:09:57 UTC
Hello Jon, thanks for replying.

It's an Android unit tests project and it was created using VS on Windows machine.

I believe Android unit tests project comes with Xamarin Android Nunit libraries which we are using to write the tests.

I am under the impression that we can not use Nunit runners to run this project as it has to run either device or emulator.

I will provide a test project in a while.

Thanks,
Naresh
Comment 3 Jon Douglas [MSFT] 2017-08-24 16:13:46 UTC
(In reply to Naresh Thandu from comment #2)
> Hello Jon, thanks for replying.
> 
> It's an Android unit tests project and it was created using VS on Windows
> machine.
> 
> I believe Android unit tests project comes with Xamarin Android Nunit
> libraries which we are using to write the tests.
> 
> I am under the impression that we can not use Nunit runners to run this
> project as it has to run either device or emulator.
> 
> I will provide a test project in a while.
> 
> Thanks,
> Naresh

Just for your information, these runners I linked are device/emulator runners. They create a very nice Xamarin.Forms UI for seeing passing/failed tests. I would recommend you try using it in the mean-time as it might resolve your issues. Feel free to provide a test project when you can! Thanks again.
Comment 4 Naresh Thandu 2017-08-24 16:16:44 UTC
Thanks again for replying.

Can I use these runners to run an Android Nunit project which I am using to test the Xamarin android library. I am not using Xamarin forms.

Thanks
Comment 5 Jon Douglas [MSFT] 2017-08-24 16:18:32 UTC
(In reply to Naresh Thandu from comment #4)
> Thanks again for replying.
> 
> Can I use these runners to run an Android Nunit project which I am using to
> test the Xamarin android library. I am not using Xamarin forms.
> 
> Thanks

These runners use Xamarin.Forms for their cross platform UI. You do not have to use Xamarin.Forms in any manner. It's purely for the runner.

You should be able to use these runners as a replacement to nunitlite. You'll have to experiment with them.
Comment 6 Jon Douglas [MSFT] 2017-10-13 17:35:23 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!