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
We have page.on('metric') which allows us to group metrics when a URL match is found. The issue arises when the website under test makes different types of requests using the same URL, for example a GET to api/cart, and a POST to api/cart. In this case it's not going to be useful to group the same request together as the behaviour of them will be different.
What would be useful is to be able to filter/group also by the request type.
Suggested Solution (optional)
A possible solution is to extend the existing API so that it can also take a type field. If the type field isn't present, it will assume that all requests are to be grouped regardless of the type. If a type field is present it will take that into account:
The suggested (and the current) solution is mixing the tag name and URL properties.
It was fine when there was only url and name. I believe the API would be less confusing if it'd group urls by a name instead of having name as another property. Maybe something like:
Feature Description
We have
page.on('metric')
which allows us to group metrics when a URL match is found. The issue arises when the website under test makes different types of requests using the same URL, for example a GET to api/cart, and a POST to api/cart. In this case it's not going to be useful to group the same request together as the behaviour of them will be different.What would be useful is to be able to filter/group also by the request type.
Suggested Solution (optional)
A possible solution is to extend the existing API so that it can also take a
type
field. If thetype
field isn't present, it will assume that all requests are to be grouped regardless of the type. If atype
field is present it will take that into account:Already existing or connected issues / PRs (optional)
#371
#1434
Tasks
page.on('metric')
#1490The text was updated successfully, but these errors were encountered: