Ordering operations not working with various url path

Hi,

Following the issue raised here: https://github.com/apideck-libraries/portman/issues/423 I found that there is indeed a minimal reproductible case when we have 2 http requests without any folder:

GET /users/
POST /users/search

Here is the following openAPI yaml corresponding to that:

openapi: 3.0.0
info:
  title: Sample API
  description: Sample desc
  version: 0.1.9
servers:
  - url: http://api.example.com/v1
    description: Optional server description, e.g. Main (production) server

paths:
  /users:
    get:
      summary: Returns a list of users.
      responses:
        '200':
          description: A JSON array of user names
          content:
            application/json:
              schema: 
                type: array
                items: 
                  type: string
  /users/search:
    post:
      summary: search for user
      responses:
        '201': 
          description: A JSON array of searched user names
          content:
            application/json:
              schema: 
                type: array
                items: 
                  type: string

Given the following portman config yaml:

{
  "version": 1.0,
  "tests": {},
  "globals": {
    "orderOfOperations": ["GET::/users/", "POST::/users/search"]
  }
}

I would expect to have the GET operation performed before the POST one. However, the generated collection has the the POST request before the GET, it is confirmed whenever newman is running it:

→ search for user
  POST https://api.toto.com/users/search

→ Returns a list of users.
  GET https://api.toto.com/users 
Collection run completed.

Is there any workaround that could exist ? I could put a tag but this does not really scale when we have like > 20 requests

[laurent-lemke]

Gosh yes it totally did, thanks for helping me to notice that !

[thim81]

@laurent-lemke If the above explanation helped you solve your issue, could you please close the item? Otherwise we will auto-close it after 7 days?