-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Consider Adding "Resume" Functionality #704
Comments
great idea. +1 |
Sounds nice but do you mean this should work only with --stop-on-error? |
I had a fatal PHP error when I had this idea, but it could obviously be On Thu, Nov 1, 2012 at 8:41 PM, Alexander Ilyin [email protected]:
|
Doesn't |
This, again, depends on #10. We'd like to do this since a long time and it's a long requested feature but it would be quite ugly to implement in the current runner also it would require us do have a way to reliably store temporary data and "resume" from a temp data file. The functionally ("only run tests that failed in the last run" / resume from crash) is definitely desirable |
Huge +1 to the idea! |
+1 Just Googled to see if this functionality existed and found this thread. |
For the people interested in this feature, take a look at https://github.com/lstrojny/phpunit-clever-and-smart which offers something similar. |
@whatthejeff is there any impediment to adopt clever-and-smart behavior in PHPUnit itself by default? |
Qaqybxuxxuixmgym
|
@marcioAlmada The README for the project says, "It’s probably not yet very stable but try it out." I think once it's ready, @lstrojny will open a PR. In the end, @sebastianbergmann will have the final word since it is such a big addition. |
I beleave that PHPUnit already has this feature. I don't know if it is available for CLI, but i've used this through XML config stopOnError="false" stopOnFailure="false" stopOnIncomplete="false" stopOnSkipped="false" |
@emkookmer These are also available as CLI options. This feature request is about resuming at the point where the tests failed/stopped, though. |
+1 googled to see if this already exists, landed here :-) |
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, |
If you have a good number of tests, and some test at the end fails, it would be cool if phpunit could resume test execution where it failed after you have fixed the test.
I'd imagine something like
phpunit --continue
, or a command prompt a laphpunit has detected an unfinished run, do you want to continue (y/N)?
.The text was updated successfully, but these errors were encountered: