The patch intends to speed up testing by not using DDL instead logs the INSERT/DELETE/UPDATE queries and plays them back. This still needs quite a bit of work, 1) drop the tables the test installed 2) persist across batch (that's one of the reasons why we are using strings in the changelog)

CommentFileSizeAuthor
#1 changelogger.patch19.41 KBchx
changelogger.patch14.93 KBchx

Comments

chx’s picture

StatusFileSize
new19.41 KB

A much better but still not workin' version.

Crell’s picture

Talked to chx about this in IRC a bit. I don't like the approach of adding a parallel logging system but we discussed possible alternate implementations, mostly based around alternate drivers. chx is going to keep investigating to see if this would even result in a speedup in the first place, and if so we'll revisit how to hook it into the system.

And yeah, subscribing. :-)

boombatower’s picture

Also had discussion with chx about previous attempts at this and this approach. Also subscribing.

sun’s picture

Issue tags: +Testing system
sun’s picture

I wonder how this differs to #666956: Provide DrupalCloneTestCase for testing pre-configured drupal sites?

I.e., wouldn't be a lot easier if the first setUp() in a test case would dump/copy the structure + data somewhere directly after finishing the first setUp(), and have later invoked setUp()s reload/import that data?

In other words: Invoke setUp() only once per test case. 2-nth test does not invoke setUp(), restores "cached" state of first setUp() only.

chx’s picture

Assigned: chx » Unassigned
Issue summary: View changes
steinmb’s picture

Getting old, we should consider retiring this as wont fix.

Status: Needs work » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.