[MGNLTEST-282] Extend / improve fwk configurability Created: 06/Jul/22  Updated: 15/Dec/22  Resolved: 05/Oct/22

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

Type: Epic Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 0.25d
Original Estimate: Not Specified

Issue Links:
dependency
Template:
Epic Name: improve-test-fwk-configurability
Acceptance criteria:
Empty
Date of First Response:
Team: Foundation

 Description   

Context

  • TF was originally created for core only. In the near future TF should be usable for various contexts incl. SaaS.
  • Currently test-fwk comes with values which are hard-coded or which are set via .env-file.
  • Some things - which now are always there - would be nice to allow to skip it via configuration.
  • We need to streamline configuration and make it easy usable for the various contexts.
  • As for now - we assume that the configuration can remain constant within one test-run / build.

This said - info.magnolia.test.setup.IntegrationTestSettings is still fine for configuration.

 

Task

 



 Comments   
Comment by Hua Tien Chanh [ 20/Jul/22 ]

Hi, I try to put some more context on the SaaS testing pipeline,

In the context of https://jira.magnolia-cms.com/browse/SRE-3319 we want to run the same E2E Staging test in the Production environment. In order to do that we would need to parameterize the test configuration base on the environment. (I don't have a completed list of configuration, but I think it will be cleared when we have the TF support for Staging env first)

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