Problem/Motivation
During our weekly Migrate in Core call on October 1, we discussed the fact that issues like #2346039 are likely due to bugs in our automated tests dump files. Currently, dump files are a bit unwieldy, as they are modified on an as-needed basis in a very unstructured manner.
Proposed resolution
Figure out a methodical way to generate and maintain the dump files. One solution discussed was to create a D6 site that we can modify to add the configuration and content we need for the dump files, then write a script that will automatically create the dump files from the D6 DB. This would also allow us to commit a SQL dump of the full DB to core.
This type of solution would be a tedious process, as we'd either have to spend a good deal of time creating a D6 site similar to our current dump files or update a good number of our tests to match the new DB.
Remaining tasks
Figure out if this is the best solution, discuss other potential solutions.
User interface changes
None.
API changes
None.