You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rambo needs to be extended to support URI parameters - e.g. :id in /authors/:id. This feature is central to REST API design. This is very closely coupled to issue #87, which calls for support for nested routes.
Expected Behavior
Rambo should generate useful tests for routes with URI parameters.
Current Behavior
If a route with a URI parameter is nested, it is ignored. If it is not nested, the URI parameter is included verbatim in the URI - i.e., a request will be sent to "/authors/:id" instead of "/authors/27" or whatever that ID would actually be.
Technical Challenges
Identifying where a given value "comes from" - e.g., that an :id parameter must be the ID of a resource that exists in the database
Identifying the correct fixtures to be used for a given test
The text was updated successfully, but these errors were encountered:
Summary
Rambo needs to be extended to support URI parameters - e.g.
:id
in/authors/:id
. This feature is central to REST API design. This is very closely coupled to issue #87, which calls for support for nested routes.Expected Behavior
Rambo should generate useful tests for routes with URI parameters.
Current Behavior
If a route with a URI parameter is nested, it is ignored. If it is not nested, the URI parameter is included verbatim in the URI - i.e., a request will be sent to
"/authors/:id"
instead of"/authors/27"
or whatever that ID would actually be.Technical Challenges
:id
parameter must be the ID of a resource that exists in the databaseThe text was updated successfully, but these errors were encountered: