[MGNLTEST-12] Integration test writers can add file based resources Created: 23/Sep/19  Updated: 12/Jan/21  Resolved: 30/Oct/20

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

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Rishab Dhar
Resolution: Fixed Votes: 0
Labels: QA&Testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLTEST-137 Int. tests can add file based resourc... Selected
relates to MGNLTEST-114 Enrich definition rest api with decor... Selected
relates to MGNLTEST-135 CLONE - Extract separate extension fo... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: core-TF-features-bugs-improvements
Sprint: TE 13, TE 14
Story Points: 5

 Description   

As an integration-test-writer, I should be able to add file based resources / light-modules (YAML primarily).

Use cases

  • Resources module / resources-app
  • generally light-development

The "challenge"

Since the webapps to test against run on a docker image and the tests are executed from another (virtual) network location, we need a mechanism to transfer the files to the magnolia.resources.dir of the webapps.
In a 1st quick discussion about the topic, apchelintcev was proposing to have a specific servlet for this purpose on the test-webapps.

 Possibilities:

  • Uploading (and cleaning up) YAML files to resources workspace (imagine to reuse MagnoliaRestClient); maybe auto-wrapping "real" YAML files into mgnl:resource node bootstraps?
  • Consider adding folder support for Fixture/Cleanup utilities?
  • Mounting an external directory for light-module directory, and e.g. have a JUnit5 extension dynamically add/remove aliases/symlinks.

Timebox: 5



 Comments   
Comment by Mikaël Geljić [ 10/Nov/20 ]

mind pending follow-up MGNLTEST-113 to wait fluently for definition registration: JCR node presence doesn't necessarily mean definition is registered, because of JCR resource-origin observation interval.

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