Repository navigation
Replies: 1 comment 1 reply
|
Thanks for the thorough testing, @mossabdeh. There are 2 validation gaps here; I've filed issues for both.
The date and scope fixes aren't deployed yet, so those expected |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
While building an independent QA project around the Frankfurter v2 API, I performed exploratory testing across rates, historical queries, providers, currencies, grouping, validation, and response formats.
Most behavior was clear and consistent. I noted a few cases where I wasn't sure whether the current behavior was intentional.
These are observations and questions, not confirmed defects.
Tested against:
https://api.frankfurter.dev/v2Observations
GET /rates?providers=XYZ200 OKwith[]GET /rates?providers=200 OKwith[]GET /rates?expand=200 OK, normal response without expansionGET /rates?from=2026-01-05&to=2026-01-02200 OKwith[]GET /rates?date=04-01-1994200 OKwith[]GET /rates?base=XYZ422 Unprocessable EntityGET /currency/XYZ404 Not FoundGET /currencies?scope=invalid200 OK, falls back to default behaviorGET /currencies?scope=200 OK, falls back to default behaviorGET /rates?group=month200 OK, latest-rate style responseQuestions
1. Unknown provider values
Is an unknown or empty
providersvalue intentionally treated as a valid filter with no matching data?For example:
returns:
The same happens with an empty
providersvalue.By comparison, unsupported values for some other parameters, such as
expand, return422.2. Empty
expandIs:
intentionally treated as "no expansion"?
An unsupported value such as:
returns
422, while an empty value returns the normal unexpanded response.3. Reversed time ranges
When
fromis later thanto, for example:the API returns:
Is this intentionally treated as a valid range with no matching data, rather than an invalid range?
4. Date format validation
Values such as:
return
422, while a non-ISO value such as:returns:
Is this intentional, or should unsupported date formats also be rejected?
5. Unknown currency behavior
I observed:
returns:
while:
returns:
The distinction makes sense as "invalid parameter" versus "resource not found". Is this the intended behavior?
6. Invalid
scopeFor
/currencies, an invalid or emptyscopefalls back to the default behavior and returns200.Is this intentional, or should unsupported
scopevalues be rejected?7. Grouping without a time range
A request with:
but no
from/torange has no apparent grouping effect.By comparison, an unsupported value such as
group=dayreturns422.Is
groupintentionally ignored when no time range is provided?Thanks for maintaining Frankfurter. I’m mainly asking so I can understand which behaviors are intentional before deciding what to assert in the automated tests.
QA project:
https://github.com/mossabdeh/frankfurter-api-qa
All reactions