search

damianszczepanik / cucumber-reporting

HTML reports for Cucumber
GNU Lesser General Public License v2.1
546 stars 402 forks source link

Wish to have Tags Trends #648

Open yael-lorenzo opened 7 years ago

yael-lorenzo commented 7 years ago

Hello, I would like to dedicate one of my team members to work on a new feature.

I would like to have the current Tags Statistic view per build. This means that I would like to know wich tags failed in old builds.

I woul like to have an opinion about this, usablitity, factibility, any input is welcome to start developing it.

Thanks in advanced.

damianszczepanik commented 7 years ago

Tell me more about your business requirements and high level of how would you like to develop such feature.

yael-lorenzo commented 7 years ago

I am thinking in something like the attached image. It would be an improvement of the Trends view, where the report is showing the features failed and we don't know wich one.

screen shot 2017-08-08 at 9 21 24 am
damianszczepanik commented 7 years ago

I like it and would kindly advice you if you need help

yael-lorenzo commented 6 years ago

Hello Damian, we have achieved this in the last week forking your project. (Please avoid watching to closely the build number, this was fast and hardcoded for the example only) scenarios trends

We have the need to identify flaky tests and we believe this is going to work. I am not sure how this is going to perform with "json" database of trends, but I would like to have a chance. We are going to test in a small jenkins intance.

I appreciate your feedback.

damianszczepanik commented 6 years ago

Looks good! I would not worry about JSON performance as this is executed only when the report is generated and not when the browser opens generated page. Then even the generation time takes longer than usually it is still IMO acceptable.

When you write about trends for tags I thought this should be presented graphically as the chart and this above is something different

yael-lorenzo commented 6 years ago

Thanks to the team here!

I get your point about performance. And I agree.

Actually we changed our Target from the previous approach cause this is more valuable to track flacky tests. Later we can use the JSon with more info to identify the issue for real.

We installed this in a LOAN Jenkins where we can run different builds and check the results!

We will do unit tests following the approaches you have on others and let you know with a PR :p

On Nov 26, 2017 5:13 PM, "Damian Szczepanik" notifications@github.com wrote:

Looks good! I would not worry about JSON performance as this is executed only when the report is generated and not when the browser opens generated page. Then even the generation time takes longer than usually it is still IMO acceptable.

When you write about trends for tags I thought this should be presented graphically as the chart and this above is something different

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/damianszczepanik/cucumber-reporting/issues/648#issuecomment-347034918, or mute the thread https://github.com/notifications/unsubscribe-auth/AVkwJ-Gv_mRAvObsq4YhwdqJnEgQTbeSks5s6cZmgaJpZM4OvoTN .

krisvamsi commented 5 years ago

@yael-lorenzo We are looking with something similar to the above to identify flaky tests. Did you get a chance to do PR?

yael-lorenzo commented 5 years ago

hi @krisvamsi we did not continue as the team switched and never had the chance to finish the job. If you would like to have a look I could help you out. You could check this repo out (I forked the original one) https://github.com/yael-lorenzo/cucumber-reporting and the author is suciista09.