RQ ->E2E -> KT
The work about react-query (RQ) (see related ticket) is transversal and has updated a lot of code.
Adding e2e tests to make sure nothing is broken (main usage) is a good end for the work.
It's also the opportunity to transfer knowledge to @amallahmar before @mike.velluet desertion (
We (PM & FE) can start with a brainstorm on the usecases tested upon a new release.
We'll (FE) be glad to add few usecases based on not so well-known features to avoid forgetting them.
Vis page requests
Use case 1 (overview)
> from search page (settings.json defaultView: "OVERVIEW")
> click on a dataflow
> Should have 1 request structure
> Should have 1 request data /all
> Should have 1 request availableconstraint
> Should habe 1 request data with dataquery
Use case 2 (overview)
> from vis/link
> Should have 1 request structure
> Should have 1 request data /all
> Should have 1 request availableconstraint
> Should habe 1 request data with dataquery
Use case 3 (table and chart)
> from search page (settings.json defaultView: "TABLE")
> click on a dataflow
> Should have 1 request structure
> Should have 1 request availableconstraint
> Should habe 1 request data with dataquery
Use case 4 (table and chart)
> click on a dataflow
> Should have 1 request structure
> Should have 1 request availableconstraint
> Should habe 1 request data with dataquery
Use case 1,2,3,4 made with Debt Transparency Aggregation dataflow OECD.DAF-DSD_DEBT_TRANS_DDOWN_DF_AGG-1.0-all.xml OECD.DAF-DSD_DEBT_TRANS_DDOWN_DF_AGG-1.0-data.csv
Edited by Mike Velluet