Story status
To be reviewed
Implementation status
Planned
Targetted user
Description
Tips
The Request-URI part of an HTTP message is made of /abs_path[?query]. As defined by RFC 3986, the non-empty path of an URI starts with the first "/" and is terminated by
- the first question mark ("?"),
- or number sign ("#") character,
- or by the end of the URI.
A path consists of a sequence of path segments separated by a slash ("/") character.
Description
As a test designer, I want to be able to define a set of rules that applies to the path part of the Request-URI part of an HTTP message, to verify that the SUT conforms to the specifications.
For each path segments, I shall be able to:
- Give a name,
- Give its position in the hierarchy represented by the path,
- Say whether it is optional or mandatory,
- Constrained its value with
- A fixed string,
- or a regular expression,
- or the expected datatype of the value,
- or a value set.
Examples of absolute paths that shall be checked:
- DICOMWeb WADO: /studies/{study}/series/{series}/instances/{instances}/metadata where {study}, {series}, and {instances} are the unique object identifier (OID format) of the queried studies, series, and instances respectively.
- FHIR: /Resource/{resourceId}/$operation
Acceptance criteria
V0.2
As a test designer, I can enter an ordered list of path segments.
For each segment,
- I can give it a name for sake of understandability,
- I can say whether it is required or optional.
- I can define a fixed value if relevant,
- I can define a regular expression, if relevant.
VXX
For each segment,
- I can select a datatype from a list
- I can enter the reference of a value set the value shall come from.
Jira issue