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

inconsistent output using dataprovider in incomplete tests #1074

Closed
szigya opened this issue Dec 18, 2013 · 1 comment
Closed

inconsistent output using dataprovider in incomplete tests #1074

szigya opened this issue Dec 18, 2013 · 1 comment

Comments

@szigya
Copy link

szigya commented Dec 18, 2013

If I run two tests with the same dataprovider (in this case with 5 elements) and mark one of them incomplete, the output is sg. like this:

PHPUnit 3.7.27 by Sebastian Bergmann.
.....IIIII
Time: 263 ms, Memory: 2.25Mb
OK, but incomplete or skipped tests!
Tests: 10, Assertions: 5, Incomplete: 5.
Done.

But the junit-like xml tells me that I have just one incomplete test. (I can't paste xml here)

@sebastianbergmann
Copy link
Owner

Dear contributor,

let me start by apologizing for not commenting and/or working on the issue you have reported or merging the pull request you have sent sooner.

PHPUnit 5.0 was released today. And today I am closing all open bug reports and pull requests for PHPUnit and its dependencies that I maintain. Please do not interpret the closing of this ticket as an insult or a lack of interest in your problem. I am sorry for any inconvenience this may cause.

If the topic of this ticket is still relevant then please open a new ticket or send a new pull request. If your ticket or pull request is about a defect then please check whether the issue still exists in PHPUnit 4.8 (which will received bug fixes until August 2016). If your ticket or pull request is about a new feature then please port your patch PHPUnit 5.0 before sending a new pull request.

I hope that today's extreme backlog grooming will allow me to respond to bug reports and pull requests in a more timely manner in the future.

Thank you for your understanding,
Sebastian

Repository owner locked and limited conversation to collaborators Oct 2, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants