Problem/Motivation

Although we are currently writing tests for this module, there are a lot of things that have not been tested yet. Also, only an exhaustive manual testing will determine if Configuration Management is working fine while exporting/importing configurations provided by contributed modules.

Proposed resolution

Use the comments of this page to describe what components are working and what are not. Test the basic functionality Import, Export, Start Tracking, Stop Tracking, Change values from files and see if changes are detected. Each fail should trigger a new issue, each feature that is working should have its own test to ensure no regressions in the future.

Remaining tasks

  • Test the Tracking functionality.
  • Test the No Tracking functionality.
  • Test the Migrate (Export) functionality.
  • Test the Migrate (Import) functionality.
  • Test the modifications of files without using the UI and see if changes are detected.
  • Test configurations that are only in the datastore.
  • Test configurations modified in both the Activestore and in the Datastore. (Or at least figure out when this can happen)
  • Test what happen when a configuration componenet is deleted (from the Datastore, from the Activestore)

Add other things to test to this list.
Update the list with the issues that are are tracking the progress of each test.

User interface changes

None

API changes

None

Comments

lucascaro’s picture

lucascaro commented

Here's my report for the items mentioned by @dagmar:

* Tracking functionality for core configurations is covered in the tests. We need to add tests for the contrib modules we support.
* No tracking functionality seems to work when tested manually. Needs automated tests.
* There are some tests for exporting configurations but we need to do a more thorough check.
* There are no tests for importing configurations.
* When changing the files outside the UI the module gets a little weird, for example:
- Deleting all configuration files breaks the state of the tracked configurations.
- Adding new configurations to the filesystem just ignores them if they're not being tracked.
- Editing the files and changing the values for configurations that are already being tracked works after using the button "Check for new configurations".
* Configurations changed both in the activestore and the datastore are just the same than configurations changed in one of them since the meaning of "Changed" is that it's different from the other ****store (i.e. activestore and datastore are not equal) and there's no intermediate state, therefore the same 2 options are presented, write AS to DS or write DS to AS.
* Deleting a component from the datastore (manually deleting the file) gives the following messages:

Notice: Undefined index: dependencies in _configuration_write_export_table() (line 1008 of /var/www/configuration/sites/all/modules/custom/configuration/configuration.module).
and
Removed 1 configuration(s). No Longer tracking page. Not found in datastore.
and
Configurations are out of sync and need to be either activated or written to file.

And doesn't remove the configuration (page in my case) from tracking but it sets it as "New configuration". So probably the "No longer tracking" message is wrong.
In general, deleting a configuration from a file without updating config.export leaves the system in an inconsistent state.

* Deleting a configuration from the active store (Tried adding a custom image style and deleted it after writing to the datastore) doesn't work since the configuration not only still shows as tracking, but it shows as In Sync. Even after using "check for new configurations".

dagmar’s picture

dagmar
Primary language Spanish
Location Argentina
commented
Status: Active » Closed (won't fix)

Let focus on 7.x-2.x.