Would you like to have auto-generated test reports ?

[rstormsf]

Would you like to have auto-generated test reports ?
Example:
When Travis CI finished the job, it automatically pushes to github pages to the repo:
https://rstormsf.github.io/tokenReg_parity/mochawesome.html

Auto-deployed commit from travis: rstormsf/tokenReg_parity@e316303

Changes needed:

.travis.yml

deploy:
  provider: pages
  local_dir: mochawesome-report
  target_branch: gh-pages
  email: travis@ci.com
  name: Deployment Bot
  skip_cleanup: true
  github_token: $GITHUB_TOKEN # Set in travis-ci.org dashboard
  on:
    branch: master

truffle.js

  mocha: {
    reporter: 'mochawesome'
  }

package.json

yarn add mochawesome -D

If @maraoz or someone else can add GITHUB_TOKEN to the travis ENV vars, I can submit a PR.

Then we can always have link to the latest test suite report on README.md page like I did here:
https://github.com/rstormsf/tokenReg_parity - (click on Full Test Report)

Owner of the repo would also have to enable Github Pages hosting in settings

[rstormsf]

Looks like the reports are working!
https://travis-ci.org/OpenZeppelin/zeppelin-solidity/jobs/284884482#L806-L808

[frangio]

Thanks for the suggestion, @rstormsf!

I think this is interesting but that it doesn't add a lot of value for OpenZeppelin. Our policy is to keep tests always 100% passing. While it might be useful for other Git and collaboration models in which tests may temporarily fail, in our case it will only require maintenance but not add much value. What do you think?

Additionally, test results can already be seen in the Travis log. True, there's no fancy graphics or statistics but I think all the relevant information is there.

[rstormsf]

I agree, it doesn't add much value, just adds some fanciness to the project. Feel free to close the issue.