Improve test coverage especially around wse_config

Created on 6 January 2025, 2 months ago

Problem/Motivation

In 🌱 Identify roadblocks to staging config in Workspaces (e.g., via wse_config) Active we discuss using wse_config to help Experience collect together a group of configuration and content changes. While coming to the conclusion that wse_config was the best starting point we found that the module lacked automated test coverage.

This issue exists to coordinate efforts to add test coverage to ensure that we can improve and extend the functionality delivered buy the module without breaking anything.

Proposed resolution

Areas to improve testing:

  • Extensive testing around how the module deals with caches
  • Editing the same config in a workspace and live
  • The hook for including simple configuration or whatever we come up with to replace this.

Remaining tasks

  • Open issues for identifed areas
  • Identify gaps

User interface changes

N/a

API changes

N/a

Data model changes

N/a

🌱 Plan
Status

Active

Version

2.0

Component

Workspace Config

Created by

πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

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

Comments & Activities

Production build 0.71.5 2024