Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

History won't be generated #682

Closed
johnmondeen opened this issue Nov 30, 2017 · 5 comments
Closed

History won't be generated #682

johnmondeen opened this issue Nov 30, 2017 · 5 comments
Labels
theme:epic type:new feature Change that add something new for end users

Comments

@johnmondeen
Copy link

I am using: protractor, jasmine-allure-reporter, allure-commandline


I had the problem, that no history would be generated over multiple testsuite executions.
After understanding the purpose of the history-feature (see https://stackoverflow.com/questions/47514696/what-exactly-are-history-and-retries-meant-to-mean-in-allure/47533045#47533045), more research and lots of trying out different things, I found this solution:

Before a new testsuite execution, the "history"-folder from "allure-report"-folder is supposed to be copied into the "allure-results"-folder. This way, allure will generate the right history from the saved "history"-folder.

My fix:
Execute the test via .bat and copy the folder beforehand:

if [[ -e ./allure-report/history ]]; then
  if [[ -e ./allure-results/history ]]; then
    rm -rf ./allure-results/history
  fi
  mv ./allure-report/history ./allure-results/history
fi
protractor conf.js
allure generate -c

Is there a better way to do this?
Shouldn't this happen by default?

@baev
Copy link
Member

baev commented Nov 30, 2017

yeah, thats how it works at the moment. BTW we are going to implement allure config that will allow you to specify history folder via commandline:

$ allure generate --history /my/local/history

or using yaml configuration file

# allure.yml
history: /my/local/history
other.configs...

and then such config will be used during report generation

$ allure generate --config my/allure/config 

@johnmondeen
Copy link
Author

I have found an issue with this solution. See the following scenario:

(Say we have two testuites, I'll call A and B, and a testcase, I'll call X.)

  1. Execute X in A
    --> A listed, has no history (as expected)
  2. Execute X in B
    --> B listed, has no history (as expected)
    --> X from 1) now in history of A (not expected?!)
  3. Execute X in B again
    --> B listed, has history --> X from 2) (as expected)
    --> X from 1) and X from 2) now in history of A (not expected?!)

Looking into the files, I found, that the doubled history-entries have different uid s, but their time-stamps are the same.


How do you generate a proper history, when not continuing the execution of a testsuite, but running the same testcase in a different testsuite?


Also: Why will the history only store up to five testcases? Can one somehow change that number?

@baev
Copy link
Member

baev commented Dec 4, 2017

Why will the history only store up to five testcases? Can one somehow change that number?

There is an issue #347

@baev baev added theme:epic type:new feature Change that add something new for end users work:backlog labels Dec 15, 2017
@baev
Copy link
Member

baev commented Dec 15, 2017

#697

@baev
Copy link
Member

baev commented Dec 15, 2017

I have found an issue with this solution. See the following scenario:

@johnmondeen please create a separate issue. Also provide sample project to reproduce the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme:epic type:new feature Change that add something new for end users
Projects
None yet
Development

No branches or pull requests

2 participants