There are times that we need to mock a response to write deterministic e2e tests and to mock responses we need to provide data and sometimes we need a lot of data, for example, 100+ data points are required for pagination to be visible in the UI.
Currently, we are storing all the required mock data in fixture files and those files can sometimes be up to 4000 lines long depending on the resource (see cypress/e2e/blueprints/explorer/cluster/events.js in the dashboard repo). Let's find a more efficient way of storing mock data.
UPDATE: Going to create real data instead of mock data which will resolve this issue ^ and so that we're testing against real data coming from the backend.
There are times that we need to mock a response to write deterministic e2e tests and to mock responses we need to provide data and sometimes we need a lot of data, for example, 100+ data points are required for pagination to be visible in the UI. Currently, we are storing all the required mock data in fixture files and those files can sometimes be up to 4000 lines long depending on the resource (see
cypress/e2e/blueprints/explorer/cluster/events.js
in the dashboard repo). Let's find a more efficient way of storing mock data.UPDATE: Going to create real data instead of mock data which will resolve this issue ^ and so that we're testing against real data coming from the backend.