[MGNLTEST-159] rest-assured to test-fwk Created: 22/Apr/21 Updated: 06/Sep/21 Resolved: 05/Aug/21 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Christoph Meier |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1d 4.25h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Epic Link: | core-TF-features-bugs-improvements | ||||||||
| Description |
Contexthttps://rest-assured.io/ is a very useful fwk to test REST endpoints or to check resources which are served via REST. In some of the new INT tests we use the MagnoliaRestCLient (which has the "adavantage" of being instance aware) and do assertions with com.jayway.jsonpath:json-path-assert. We should add/enable rest-assured to the test framework, in a way that makes it convenient to test REST resources in the Magnolia context - e.g. with convenient default, etc.
|
| Comments |
| Comment by Christoph Meier [ 20/Jun/21 ] |
|
I thought about adding some "convenience stuff" e.g. to for easy default, though haven't found a good way yet. |
| Comment by Christoph Meier [ 05/Aug/21 ] |
|
This ticket actually is obsolete now. There is no need to add the sole library to the test-fwk. I close it herby |