[MGNLTEST-322] Attach an app repo to the subscriptions managed by saas-test-framework Created: 18/Oct/22 Updated: 31/Jan/23 Resolved: 28/Oct/22 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Roberto Gomez | Assignee: | Roberto Gomez |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Epic Link: | subscription-life-cycle-support-by-test-fwk | ||||
| Team: | |||||
| Description |
|
The SaaS Test Framework allows dynamically subscription management for testing purposes. As it is now, the fresh new subscription is empty, but some e2e tests require a fully configured app (a git repo attached), hence the subscription needs to have attached an app repo fully fledged for e2e testing . There are a couple of sample app repos available:
Instead of creating every time a new project alongside new subscriptions, if possible, it's better to reuse the same existing app project for every susbcription. There is also the ProjectConfigurationTest.java with an example worth inspecting.
|