I have fixed two out of the three. And made sure the three does not cause an infinite loop. I will figure out this one, too.

Comments

Rok Žlender’s picture

FileSize
9.77 KB

Fixed few notices.

boombatower’s picture

Do we really need to just brute force turning on all the modules?

Can't we just simplify code by enabling certain cases where we know dependencies?

Just seems like a waste of processing time.

boombatower’s picture

FileSize
3.49 KB

I have essentially rewritten the system test. Much of the previous code was there to ensure the the module state was as it wanted.

Since we start off with a clean database that is no longer necessary. Attempting all possibilities is, as the loops did, is somewhat of over kill and is hard to follow, not to mention slow.

Let me know what you think.

boombatower’s picture

FileSize
4.88 KB

Here is a revised version which I think should do the trick.

boombatower’s picture

FileSize
4.6 KB

Cleaned up.

boombatower’s picture

FileSize
4.68 KB

t()ing cleanup.

boombatower’s picture

FileSize
4.94 KB

Last update.

Will move assertTableCount to DrupalTestCase in patch.

boombatower’s picture

This is patch that moves assertTableCount code to simpletest.module..

boombatower’s picture

Status: Needs review » Fixed

The system test and patch have been committed.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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