-
-
Notifications
You must be signed in to change notification settings - Fork 655
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
add example compatible with -> https://github.com/report-ci/ #212
Comments
No, it's not. jUnit/xUnit were left for a future version - contributions are welcome! Or perhaps in a few months once I get some free time again. I'm linking the old reporter issue which I closed because of some links: #138 (comment) |
Oh glad to read this issue, I think that we can ask report-ci if we can have a doctest compatibility ! I will keep you in touch ! Thanks a lot |
I wrote them an email at support@report.ci 22 days ago asking if XML report is enough and still no response. Hope you have better luck! |
We can probably open an issue on the github -> https://github.com/report-ci/scripts If it's possible to have the sample.xml that you send by mail with all explanation, i can open the issue following your email message (rmscastle@gmail.com) for my email |
Thanks a lot |
Sorry about the lost mail, I'll check the servers ASAP. I think we'll have doctest added within 2-3 weeks. |
Done, can be closed. Here's the code in the travis yaml https://github.com/report-ci/doctest/blob/travis/.travis.yml#L350 and in bash my_test --reporters=xml --out=my_test.xml
# Only looks for xml files!
curl https://report.ci/upload.py | python and here's the result: https://github.com/report-ci/doctest/runs/87455527 Btw. I normally build the example by having correct tests in the master and a PR from a branch with broken tests like here |
Hello, may be i'm missing something but i'm not able to make doctest work with report-ci with the new xml reporter, is this junit format right ?
The text was updated successfully, but these errors were encountered: