Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
We have about a dozen export buttons. The most I can assert from a feature file today is that a toast appeared, which passed happily for two weeks while the export was returning an empty file.
Is there a download step anywhere? I cannot find one in the step library.
Accepted answer
No download step ships. There is an open issue with a proposed set — filename, size, content type, CSV row count — and none of it is written yet.
The base class gives you waitForDownload(), so a project step is short:
@When('I export the current view as CSV')
async exportCsv() {
const download = await this.waitForDownload(() =>
this.page.getByRole('button', { name: 'Export' }).click(),
);
this.lastExport = await download.path();
expect(download.suggestedFilename()).toContain('.csv');
}Then a Then step that reads the file and asserts on it.
Given what you described — a toast that passed while the file was empty — please assert on content and not just on the filename. A zero-byte report.csv satisfies every filename check you can write.
Minimum useful pair: a byte size above some floor, and a row count that matches something you know (the number of rows the UI was showing). The second one has caught genuine bugs for us twice, both times a filter that applied on screen and not in the export.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.