We discussed about this with @derega and came to the conclusion that it would be better to do the tests at this point only with one attribute. In other words mpass-data works so that /api/1/user?dreamschool=123 is valid but /api/1/user?dreamschool=123&foo=bar is not.
Current implementation is not deterministic. If user makes query against the spec by giving two or more attributes, it is possible that at times the results differ, as only the first attribute is used for filtering but the order of get-attributes may change even between similar requests.
/api/1/user?dreamschool=123&foo=barfilters UserAttributes by only picking either of the parameters (randomly).
DoD: User queryset is filtered using all GET parameters
Line 144 in c37e991
This is the reason why following test failed: https://travis-ci.org/educloudalliance/eca-auth-data/jobs/102996338
The text was updated successfully, but these errors were encountered: