Refactor config import/export tests to allow for easy extension

Created on 10 October 2013, over 11 years ago
Updated 13 February 2025, 10 days ago

Probably at least makes sense to have a ConfigExportImportUITestBase.php with common properties/methods.

For example:

+ protected $tarball;
+ protected $admin_role;
+ const SORT_METHODS = TRUE;
+ protected function setUp() {

This would make each sub-class only responsible for their own testImport/testExport/doImport logic.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

config.module

Created by

πŸ‡¨πŸ‡¦Canada webchick Vancouver πŸ‡¨πŸ‡¦

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024