Skip to content

Print the running test names on CI #4001

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

Closed
archmoj opened this issue Jun 30, 2019 · 5 comments · Fixed by #4012
Closed

Print the running test names on CI #4001

archmoj opened this issue Jun 30, 2019 · 5 comments · Fixed by #4012

Comments

@archmoj
Copy link
Contributor

archmoj commented Jun 30, 2019

Currently the tests that are skipped are logged in blue lines; whereas for the actual running tests only a dot is printed out.
As a result it looks almost impossible to figure out which tests are actually failing on the CI.

Why not logging the names of the tests that we run instead of those that are skipped?

Screenshot from 2019-06-30 19-46-30

@etpinard
Copy link
Contributor

etpinard commented Jul 2, 2019

You can try running the tests with --verbose

https://github.com/plotly/plotly.js/blob/master/CONTRIBUTING.md#jasmine-tests

@etpinard
Copy link
Contributor

etpinard commented Jul 2, 2019

We could also turned off

suppressFailed: true,
suppressPassed: true,

on CI if you prefer.

@etpinard
Copy link
Contributor

etpinard commented Jul 2, 2019

@archmoj @antoinerg let me know if you prefer the test report off:

https://circleci.com/gh/plotly/plotly.js/43636#tests/containers/1

using commit 51b60fb

@antoinerg
Copy link
Contributor

@archmoj @antoinerg let me know if you prefer the test report off:

https://circleci.com/gh/plotly/plotly.js/43636#tests/containers/1

using commit 51b60fb

I don't mind it :)

@archmoj
Copy link
Contributor Author

archmoj commented Jul 2, 2019

Love it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants