search

GHPReporter / Ghpr.NUnit

Adapter for NUnit 3 (generate HTML report for NUnit 3)
http://ghpreporter.github.io/
MIT License
35 stars 14 forks source link

Screenshot fail when I set up the "TakeScreenshotAfterFail" parameter to True #7

Closed yfrindel closed 7 years ago

yfrindel commented 7 years ago

Hi elv1s42,

Thank you for this good report. I don't know why, but when I set up the "TakeScreenshotAfterFail" parameter to True, the tests failed don't appear in the report. Is it a bug ?

Thank you to help me.

Yannick

elv1s42 commented 7 years ago

Hello. Right now it does not work with Jenkins, it works only for running tests locally on your machine.

I will investigate this issue.

Thanks for this issue

elv1s42 commented 7 years ago

Hi @yfrindel ! Please let me know if this issue has gone with latest Ghpr.Core, Ghpr.NUnit (both v0.4.3) and NUnit.Console (v3.6). Please note, that now there is no need to edit nunit.console.exe.config file, because all settings are passed via .json settings file. If you are going to take screenshots inside yout tests, then make sure that you have the same Ghpr.NUnit.Settings.json file inside your C# project and inside NUnit.Console addins folder.

Also, take a look at How to work with screenshots section.

elv1s42 commented 7 years ago

Issue fixed in v0.4.3

yfrindel commented 7 years ago

Hi, not tested yet...I'm busy with other things, but I will take a look. Yannick 

Le Mardi 17 janvier 2017 17h07, Evgeniy Kosjakov <notifications@github.com> a écrit :

Hi @yfrindel ! Please let me know if this issue has gone with latest Ghpr.Core, Ghpr.NUnit (both v0.4.3) and NUnit.Console (v3.6). Please note, that now there is no need to edit nunit.console.exe.config file, because all settings are passed via .json settings file. If you are going to take screenshots inside yout tests, then make sure that you have the same Ghpr.NUnit.Settings.json file inside your C# project and inside NUnit.Console addins folder.Also, take a look at How to work with screenshots section.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.