Closed (outdated)
Project:
SimpleTest
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Sep 2010 at 02:57 UTC
Updated:
27 Jun 2018 at 13:23 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Bevan commentedI started updating the patch from #580530: Command to run simpletests for Drupal 7 and Drush 3, but kept getting the following error. The attached patch is where I got to.
Comment #2
moshe weitzman commentedThanks for being persistent with this. I've thought it over, but I don't really want this in devel either. I'm hoping that we get some traction in that drush issue.
Comment #3
moshe weitzman commentedThanks for being persistent with this. I've thought it over, but I don't really want this in devel either. I'm hoping that we get some traction in that drush issue.
Comment #4
Bevan commentedMoshe, I think you still do not agree with me that these are two separate feature requests:
This one is intended for simpletest-authors so they can execute they test they are authoring and test the test. The other issue started out for the same feature, but then became about running all simpletests. These are unrelated features that do not depend on each other and are only mildly related; they have different uses and intended audiences.
I really don't want to create a module just for this drush command. Perhaps simpletest module will take it?
Comment #5
boombatower commentedAssume this needs to be adapted for simpletest then?
Comment #6
Bevan commentedboombatower; Yes. Adapting it is more or less just s/drush/simpletest/ and s/test/one. Would you accept this feature?
Comment #7
boombatower commentedSeems like a logical addition, yes.
Comment #8
Bevan commentedGreat! I'll work on this, on Monday with some luck.
Comment #9
Bevan commentedLast week didn't work out — my hard drive failed. I'm not sure when I'll get to this.
Comment #10
langworthy commentedregarding #4: #580530: Command to run simpletests did not turn into a discussion about running all simpletests. The projects in both #6 and #17 of that issue include options to run a single simpletest using drush. This seems to be the goal here as well.
The goal seems to be a drush command that runs tests. Do we need multiple drush commands that will print all passes and fails to the screen and also exit properly for automation tools?
Edit:// can't we still work together on this?
Comment #11
Bevan commentedI would love to be able to collaborate on this. I've implemented the single-test twice already for each of devel and drush modules and the feature was rejected in both issue queues because it was not a desirable feature to be able to run a single test.
Comment #12
langworthy commentedI believe all that is missing from the single-test functionality that has been implemented in one of the projects that drush would like to accept (yhahn's test.drush.inc) is output of each assertion. I think this could be accomplished with a flag.
On a separate but related to this issue note: I believe the errors encountered in the description of this issue are because the standard profile was being tested. I have opened up an issue regarding this. #974768: test-run command fails using standard install profile
Comment #13
kenorb commentedIt's possible to have 'test' command for Simpletest 6.x ?
Comment #14
langworthy commenteddrush test-runshould work for 6.x and you may have luck with therun-tests.shthat comes with Simpletest.Comment #15
kenorb commentedDrupal 6 is no longer officially supported. If you think this issue is still relevant for 8.x, feel free to re-open.