Allure 2.6.0 is not able to generate history trends

[holphi]

Not sure if this is the right place to submit bugs, but I'm having trouble in generating history trends with the latest Allure 2.6.0.

I followed the instructions in this ticket https://github.com/allure-framework/allure2/issues/682 and copied the history folder from ./allure-report to ./allure-results before generating new report, however, after invoking below command, I still can't see the history trends in TREND section.

allure generate -c

Does anyone else have the same issue? I am expecting your solutions on this. Thansk in advance!

BTW, I am using python behave as our test framework, and we're using the plug-in allure formatter convert behave result to allure result.

[Jiff21]

I'm not having this issue and am using. Python 3.6, OSX, Allure 2.6.0, behave 1.2.6. cp path/to/allure-reports/history path/to/allure_results/history allure generate path/to/allure_results/ -o path/to/allure-reports/ --clean allure open path/to/allure-reports/

[holphi]

Hi @Jiff21,

Thanks for your reply. Now I can see history trends in the allure report by following your commands, I should have specified the results folder when creating the reports.

Thanks, Alex

[ikostan]

Hi. I have a similar issue.

My dev config: Win 10 64 bit allure-pytest 2.7.1 selenium 3.141.0 pytest 5.0.0 allure 2.12.1

Step by step:

1. Run selenium tests from pytest using following arguments: -v --alluredir=allure-results
2. Open Power Shell > run: cp .\allure-report\history\ .\allure-results\history\
3. run: allure generate .\allure-results\ -o .\allure-report\ --clean Got following output: Report successfully generated to .\allure-report
4. run: allure open .\allure-report\

Now, as a result I see the report BUT no history trends there.

I need some help here.

Thanks

[Jiff21]

@ikostan Apologies if this doesn't help, can't debug your exact setup as I'm not on Windows. My instructions are a bit brief above, more detailed instructions can be found here. My instructions above are say missing -R on cp and a bit silly but you would have to generate a report before your steps above to have a history to copy.

[ikostan]

@ikostan Apologies if this doesn't help, can't debug your exact setup as I'm not on Windows. My instructions are a bit brief above, more detailed instructions can be found here. My instructions above are say missing -R on cp and a bit silly but you would have to generate a report before your steps above to have a history to copy.

Hi Jiff21.

You have nothing to apologies for. I think this is pure Windows (or maybe PowerShell) issue. What I mean by that is that cp .\allure-report\history\ .\allure-results\history\ (run it from PoweShell) does not copy anything for some reason. So I did it manually, as a result I got my history trend!!!

Thanks and have a nice weekend.

[Jiff21]

It could be the recursive copy, which is the cp -R thing I mentioned, but seems like Powershell uses a different command (see first comment here).

[auto-qa-git]

Can someone please help me with this? https://github.com/Codeception/CodeceptJS/issues/1706#issuecomment-579890602

[cinderblock]

Is there somewhere that documents this requirement of copying the history folder to the results? I've been trying to get this to work in GitHub Actions and have had no end of trouble getting the trends to show up. This issue is the first I've come across noting that the history folder needs to be copied over.

[kaufmann42]

Still seems to be buggy even when copying over that folder.

[fescobar]

Why don't use the latest version 2.13.2? https://github.com/allure-framework/allure2/releases/tag/2.13.2

[cinderblock]

@fescobar does the latest version automatically save the results now? That would be sweet!

[fescobar]

@cinderblock no. Use Allure docker container if you want that automatically https://github.com/fescobar/allure-docker-service#keep-history-and-trends

[cinderblock]

@fescobar fair enough. I figured out a different way :)

I'm using a git branch as a data store the results and copying the data in ci scripts. My readme automatically gets the latest trends with no services besides what are available on github! :D

Check it out: https://github.com/cinderblock/github-action-working-directory#allure-2-test-report

[praful-transcarent]

This does populate the history trend on the first execution. The problem I am getting is during the second run.

When I execute the same set of steps again, the history does not show the correct results.

1. Firstly it is showing me duplicate test cases out of which 1 does not have history maintained for it and the second one has two result for the same time .

Has anyone come across a similar problem.

[fescobar]

@praful-transcarent how are you generating the history? Manually?

[praful-transcarent]

@fescobar @Jiff21 yes this is being done manually. But eventually my goal is to push this to s3 and host the report on cloudfront

[praful-transcarent]

@fescobar @Jiff21 below are the steps i am following.

• newman run postmanCollection.json --reporters htmlextra,cli,allure --reporter-htmlextra-export SampleArtifact/postman-report.html
• cp -R allure-report/history allure-results/ (copying the history folder that was generated during the 1st execution)
• allure generate --clean
• allure open

[praful-transcarent]

@fescobar got a chance to look into the above comments ?

[fescobar]

Hi @praful-transcarent I have that implemented and it's working perfectly

https://github.com/fescobar/allure-docker-service#keep-history-and-trends

https://github.com/fescobar/allure-docker-service/blob/master/allure-docker-scripts/keepAllureHistory.sh