Run tests for releases after project published ZIP file

I was doing testing with Drupal 7.43. Spent ton of time to figure out why ModuleDependencyTestCase was failing...

The reason was a version tag in info file after release.

Potentially we can have tests failure after repackaging core or contrib project for release.

I propose to do testings on release as well, after info values has been set by project module.

GitHub Link:

https://github.com/backdrop/backdrop-issues/issues/1964

GitHub Issue #:

1964

Log in or register to post comments

Recent topics

Importing the staged config throws an error: another field with the same name already exists

Posted 1 day 9 hours ago by Francis Greaves (themetman) in How-To and Troubleshooting

Comments Enhanced

Posted 1 week 3 days ago by (izmeez) in How-To and Troubleshooting

Why not add a Github star?

Posted 1 week 4 days ago by (izmeez) in How-To and Troubleshooting

Recent comments

@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...

Posted 1 day 3 hours ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Thanks, I have to go out now, I will try later on and report back

Posted 1 day 8 hours ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....

Posted 1 day 8 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:

Importing the staged config throws an error: another field with the same name already exists