Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
simpletest.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Feb 2016 at 08:29 UTC
Updated:
25 Mar 2016 at 23:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
dawehnerThere we go.
Comment #3
dawehnerAdapted the code to use types instead of groups.
Comment #4
dawehnerExpanded to also add a explicit command to just render a certain type
Comment #5
dawehnerMore work was needed here.
Comment #7
dawehnerUps, this patch was the wrong way round.
Comment #8
alexpottComment #9
alexpottMissing --types documentation
Why should the types only work with --module and --all? Also tbh I think we should only have --types and make it work in conjunction with --all.
Comment #10
dawehnerGood point, well, I was probably lazy
Comment #11
alexpottI don't think the --all is required and the example needs to include what --types= should be and I guess it should give an example where it is multiple types.
Comment #12
dawehnerHa, I indeed stopped editing in the middle of it.
Comment #13
jibranNice work @alexpott and @dawehner this looks ready to me.
Do we typehint array now?
Comment #14
jibranNice work @alexpott and @dawehner this looks ready to me.
Do we typehint array now?
Comment #15
dawehnerWhy not, its an array.
Comment #16
dawehnerAdapted the title using the new approach.
Comment #17
jibranGiven that we ran into array typehinting issue in #2664290: Remove array typehints from batch callbacks. I think we should re-consider typehinting as array here as well.
This means that after the filtering if we have any array element left apply filter on those. Either we should document it explicitly or we should use third param
$before = TRUEto filter given array before or after the nested filtering.Comment #18
jibranFor point 2 clarification
Comment #19
dawehnerWell, I doubt entirely that drush will replace the core run-tests.sh
--typesparameter. Arrays as typehints isn't that uncommon:Comment #20
jibranAfter the discussion with @dawehner we agreed the point 1 is not valid here and expanding filter function is out of scope so this patch is ready imo.
Comment #21
xjmI think this is not a complete sentence?
Comment #22
dawehnerNot a problem of this issue, but sure, let's fix it.
Comment #23
isntall commentedIs there a list of all the --types that can be used?
Comment #24
isntall commentedrun-test.sh doesn't work with an equal sign, and the capital 'T' in SimpleTest should be lowercased.
Comment #25
isntall commentedWhen testing the patch, I noticed that inputing an invalid type did not result in an error, we might want to have another class written to check if the type is valid.
Comment #26
dawehnerIt is a good question whether we should hardcode the list of available types, so we can actually know which types exists and by that validate it.
Comment #27
isntall commentedOn the DrupalCI side, since the types are being include and not excluded, we need to hardcode the types that are being tested, and those types will need to be updated everytime they are changed.
DCI will allow D.o to send over the types via the DCI_TestGroups parameter, but then d.o will need to know what they are.
Comment #28
dawehnerI totally agree, well after alex denied to add
--exclude-types. I guess for core itself, hardcoding is valid as well. We don't add new ones every here and nowComment #29
Mixologicputting this back to RTBC. Tests check out.
Comment #32
alexpottCommitted 220e86d and pushed to 8.0.x, 8.1.x, and 8.2.x. Thanks!
A few very minor code style nits fixed on commit.
Comment #33
isntall commentedThe new DCI tag has been deployed that takes advantage of this new functionality.