I would like to continue maintaining SimpleTest after its transition to core. To make is simpler for everyone interested in testing I think we should file issues with tests under the simpletest.module component.

The tests are more related to SimpleTest than the modules themselves. They don't enhance the modules functionality and are related to testing. This would make it easy to find all testing related issues.

Comments

cwgordon7’s picture

cwgordon7 CreditAttribution: cwgordon7 commented

I'd be in support of this. It makes sense to file the issues under simpletest for easier categorization; it also makes sense for Jimmy to continue maintaining this module, considering what an awesome job he's done already.

(+1)

boombatower’s picture

boombatower CreditAttribution: boombatower commented
Status: Active » Fixed

In IRC we decided to go with tests as the component. Thanks to webchick this was changed quickly. :)

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented

We spoke on IRC and decided that it's better to have a distinction between bugs/issues related to *simpletest.module* itself (the code of which only a relatively small team of people are familiar with) and the *tests* themselves (which hopefully LOTS of people can write :D).

So I added a new component "tests" against which all tests and test-related issues should be filed. Keep the stuff about simpletest.module itself against simpletest.module component.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented

Oops. Too late. :D

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.