Postman GET /ResourceTypes expectation is sensitive to ordering

[rdelao]

My following response will fail the Postman because it expects the /Users resource to be listed first. Is this an actual requirement or for AD SCIM application or is this just an oversight with the test?

{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:ListResponse"
    ],
    "startIndex": 1,
    "itemsPerPage": 100,
    "totalResults": 1000,
    "Resources": [
        {
            "schemas": [
                "urn:ietf:params:scim:schemas:core:2.0:ResourceType"
            ],
            "id": "Group",
            "description": "Group",
            "name": "Group",
            "schema": "urn:ietf:params:scim:schemas:core:2.0:Group",
            "endpoint": "/Groups",
            "meta": {
                "resourceType": "ResourceType",
                "location": "scim/v2/ResourceTypes/Groups"
            }
        },
        {
            "schemas": [
                "urn:ietf:params:scim:schemas:core:2.0:ResourceType"
            ],
            "id": "User",
            "description": "User Account",
            "name": "User",
            "schema": "urn:ietf:params:scim:schemas:core:2.0:User",
            "endpoint": "/Users",
            "schemaExtensions": [
                {
                    "schema": "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User",
                    "required": false
                }
            ],
            "meta": {
                "resourceType": "ResourceType",
                "location": "scim/v2/ResourceTypes/User"
            }
        }
    ]
}

[aliotta]

Not only that but the test checks. pm.expect(jsonData[0].endpoint).to.eql("/Users"); Which will never pass if the scim list response schema is followed (as it should be).