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

enable test coverage on coveralls #7215

Merged
merged 3 commits into from
Jan 6, 2015
Merged

enable test coverage on coveralls #7215

merged 3 commits into from
Jan 6, 2015

Conversation

Carreau
Copy link
Member

@Carreau Carreau commented Dec 14, 2014

In progress, does not work yet:
https://coveralls.io/r/Carreau/ipython

I can submit manually the results from localhost, but it seem not to want to work through travis.

Works now.

@Carreau
Copy link
Member Author

Carreau commented Dec 14, 2014

Great, seem to work now, will cleanup/squash the commits.

@Carreau
Copy link
Member Author

Carreau commented Dec 14, 2014

Oh, the link : https://coveralls.io/r/ipython/ipython

@rgbkrk
Copy link
Member

rgbkrk commented Dec 14, 2014

Are we able to do any JavaScript coverage testing?

@rgbkrk
Copy link
Member

rgbkrk commented Dec 14, 2014

Great idea by the way. Big fan of coveralls.

@Carreau
Copy link
Member Author

Carreau commented Dec 15, 2014

The website seem to lack activity though.

Note to other, coverall can post on all PR. I have it deactivated for now.

@Carreau
Copy link
Member Author

Carreau commented Dec 15, 2014

Works now, just need to copy the .coverage and coverage.xml file back into IPython dir and be sure to cd back into it after iptest.

@Carreau
Copy link
Member Author

Carreau commented Dec 16, 2014

Are we able to do any JavaScript coverage testing?

Probably but I don't know how with casper/phantom

@rgbkrk
Copy link
Member

rgbkrk commented Dec 17, 2014

Well, I was thinking more like we use their node coverage plans. It would mean that we start to demarcate pieces of our IPython frontend JavaScript as working with node (which I'd like to see anyway, I could use it in Atom in a less hacky way then).

@Carreau
Copy link
Member Author

Carreau commented Dec 17, 2014

It would mean that we start to demarcate pieces of our IPython frontend JavaScript as working with node (which I'd like to see anyway, I could use it in Atom in a less hacky way then).

Yeah, that's one of the reason I fight against jquery and other. I would like that to.

@Carreau
Copy link
Member Author

Carreau commented Dec 23, 2014

Ping.

try:
cov.xml_report(outfile='ipy_coverage.xml')
except CoverageException:
pass
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probaby not a good idea to fail silently. Warn, at least?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@Carreau
Copy link
Member Author

Carreau commented Dec 25, 2014

I'm just unhappy, either coverall has been bought, or hacked, I need to authorize a new key to access the results, which does not look like coveralls for now. And it requires full read/write access.

@minrk
Copy link
Member

minrk commented Dec 25, 2014

@Carreau does that mean we should abandon this?

@Carreau
Copy link
Member Author

Carreau commented Dec 25, 2014

No, probably not. I think it's just a mistake of coveralls that push a testing key from the company that made the website. I've tweeted a inquery and will contact by mail later if no news or not fixed or not clarified.

try:
cov.xml_report(outfile='ipy_coverage.xml')
except CoverageException as e:
print('Generating coverage report failed. Are you running javascript tests only?')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should print the exception itself as well, yes?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seem like extra noise on js test, but if you wish so, done.

@damianavila
Copy link
Member

LGTM

No, probably not. I think it's just a mistake of coveralls that push a testing key from the company that made the website. I've tweeted a inquery and will contact by mail later if no news or not fixed or not clarified.

Any update?

@Carreau
Copy link
Member Author

Carreau commented Jan 6, 2015

Seem to be fixed. I had to do a bit of browser incognito mode hopping, but it does not require full access anymore.

minrk added a commit that referenced this pull request Jan 6, 2015
enable test coverage on coveralls
@minrk minrk merged commit 12277c7 into ipython:master Jan 6, 2015
@minrk minrk modified the milestone: 3.0 Jan 29, 2015
@Carreau Carreau deleted the coveralls branch December 20, 2015 21:20
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 this pull request may close these issues.

None yet

5 participants