[MGNLPN-543] INT-Test::scenarios::Headless p13n via Delivery endpoint Created: 11/May/21  Updated: 16/Sep/21  Resolved: 23/Aug/21

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Fixed Votes: 0
Labels: VN-Testing
Remaining Estimate: Not Specified
Time Spent: 1d 7.5h
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLPN-542 Get (stateful) personalized content f... Closed
dependency
is depended upon by MGNLPN-550 Headless p13n REST integration tests Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Headless p13n
Sprint: HL & LD 35
Story Points: 1

 Description   

Define the scenarios for the integration tests for the feature „Getting (stateless) p13n content from the delivery endpoint""

Overview

  • Define the high level scenarios.

Acceptance criterias

  • List of the High level scenarios
    • is defined
    • aligned with PM/PO & dev.
    • all scenarios have a prio (high | medium | low)

Sources



 Comments   
Comment by Christoph Meier [ 11/Jun/21 ]

jsimak, czimmermann

Finally I have created the high level scenarios for "Stateless serving p13-content via Delivery endpoint API".

The scenarios are based on a quick discussion I had with Jarda, where we decided that we should test scenarios for:

  • Pages
  • Components
  • A mix of variant page with variant components

With the "base scenarios"

  • Get a variant by single trait
  • Get a variant by multiple traits
  • Get all the variants for a specific node
  • Non personalized delivery EP serves default non variant content

And we said we should use traits which are "easy" to test, such as

  • Country
  • cookie

To have a possibility to comment/etc. I created a new repo and now a PR for the given task.

=> PR

Please check

  • list of scenarios is "complete" (or sufficient)
  • the priorities (which I set maybe a bit arbitrary)

With detailled scenario descriptions we probably should wait a bit, until we are more about the how and where (of the scenarios to test).

Comment by Christoph Meier [ 04/Aug/21 ]

jsimak, cc czimmermann,
I have reopened this one, since

  • we have skipped the stateless "story"
  • The API has changed, now supporting passing traits to the server via
    • request parameter
    • cookies
    • request headers

The INT tests should have scenarios for all "methods" of the API (request param. cookie, request-header).

Comment by Christoph Meier [ 04/Aug/21 ]

scenarios must reflect the current possibilities of the API (request params. cookies, request headers)

Comment by Christoph Meier [ 23/Aug/21 ]

reviewed and merged

Generated at Mon Feb 12 06:38:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.