[MGNLTEST-415] Disabled tests should skip setting up light module fixtures Created: 30/May/23  Updated: 08/Aug/23

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

Type: Improvement Priority: Neutral
Reporter: Michael Duerig 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-428 CE 6.2 and 6.3 pipelines unstable due... 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)
Team: Foundation

 Description   

Currently disabled tests that are annotated with @LightModule still set up and tear down the light module fixture. This can lead to test failures on disabled tests should the light module definition fail. It also unnecessarily prolongs test execution.

If possible we should improve the annotation processor such that it skips setting up the light module for tests that do not run.

Notes for discovery:

  • @LightModule and @Disabled can both be used on method and class level. We need a better understanding on how they interact with each other. E.g. if @LightModule is set on class level will it still execute for individual methods that have @Disabled set?
  • Instead of complicating the code backing @LightModule, could it be less effort to align usages of these to annotations (e.g. in ResourcesFunctionalTests).

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