[MGNLTEST-158] Wait until all registry are refreshed when registering light module for test Created: 21/Apr/21  Updated: 09/Nov/23

Status: Selected
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: 1.1.0
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Milan Divilek Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLTEST-113 Verify Light module registration Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: core-TF-features-bugs-improvements
Team: Foundation
Work Started:

 Description   

info.magnolia.test.lightmodule.LightModuleUtil#loadLightModule waits until light module is registered in modules, but that doesn't mean that all registry are already refreshed yet (for example i18n, templates, etc.).

This can cause problem when opening app, clicking action, or selecting template, because they don't have to be available yet.

Acceptance criteria:

  • we need to resolve what registry are updated by light-module
  • check(probably via rest endpoint ) if the registry are refreshed and contains changes introduced by the light-module


 Comments   
Comment by Christoph Meier [ 28/Apr/21 ]

Note that we already did some work on this in the context of MGNLTEST-113 

Comment by Christoph Meier [ 28/Apr/21 ]

We need to define the acceptance criteria on this on. Once this is done, this one should be added to MOTION-319.

Comment by Milan Divilek [ 28/Apr/21 ]

Unfortunately what was done in MGNLTEST-113 isn't enough, it doesn't mean that all registry was refreshed

Generated at Mon Feb 12 07:46:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.