[MGNLGQL-82] Check all GraphQL properties and sorting capabilities Created: 31/Mar/21 Updated: 18/Apr/21 Resolved: 14/Apr/21 |
|
| Status: | Closed |
| Project: | Magnolia GraphQL |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Lam Nguyen Bao |
| Resolution: | Done | Votes: | 0 |
| Labels: | VN-Analysis, VN-Implementation, VN-Testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1d 5.75h | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Epic Link: | GraphQL Phase 1 |
| Sprint: | HL & LD 26 |
| Story Points: | 3 |
| Description |
|
Based on this recently reported problem https://jira.magnolia-cms.com/browse/MGNLGQL-81, the GraphQL feature may still have some simple bugs. Try using all possible properties of Assets and of the sample "bookcase" demo project (and maybe the tourGuides demo project) Try the most obvious filtering and sorting options. This will help ensure that we don't launch with any easily-detectable bugs. We can time box this. |
| Comments |
| Comment by Jaroslav Simak [ 07/Apr/21 ] |
|
lam.nguyen czimmermann This should be ideally covered with integration tests, while manual tests can reveal bugs that are present in this moment, integration tests will give us confidence that nothing broke for future releases. |