From the looks of it you just use SimpleTest for functional testing, not anything under the hood (like jacking the browser).

If so it should not be listed as a dependency since your module does not need it to function, only as a useful development tool.

I am assuming this is the case with #389714: SimpleTest could not be installed. Showed as enabled, unchecked, and result disabled to Rules Simpletest. which is similar to a number of issues I get with people installing SimpleTest on production sites due to it being listed as a dependency, but not really need.

Not a big issues, but I would recommend removing it.

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Component: Miscellaneous » Documentation
Status: Active » Fixed

Thanks for the note, but I think it's better to stay with the dependency as I people shouldn't enable the "rules simpletest module" except for testing rules. However I've added a further note to the readme.

boombatower’s picture

boombatower commented

As a note core doesn't do that.

Great to hear your writing tests though!

fago’s picture

fago
Primary language German
Location Vienna
commented

But the core modules are mock modules aren't they? Is this feature available in 6.x-2.x too?

boombatower’s picture

boombatower commented

Mock meaning? The only feature that core has is adding hidden = true in the .info file so it doesn't show up on modules page. Perhaps putting something in the description of the module, as I have done before, saying "ONLY FOR TESTING." Only reason I say so is because people seem to just enable all modules instead of only the ones they need.

Status: Fixed » Closed (fixed)

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