Testing File Upload and Download Workflows

​

Upload Test Pattern

import { test, expect } from '@playwright/test';
import path from 'path';

test('uploads CSV successfully', async ({ page }) => {
  await page.goto('/imports');
  const filePath = path.resolve(__dirname, '../fixtures/customers.csv');

  await page.getByLabel('Upload CSV').setInputFiles(filePath);
  await page.getByRole('button', { name: 'Import' }).click();

  await expect(page.getByText('Import complete')).toBeVisible();
  await expect(page.getByText('120 rows processed')).toBeVisible();
});

​

Download Test Pattern

import { test, expect } from '@playwright/test';

test('exports report as CSV', async ({ page }) => {
  await page.goto('/reports');

  const [download] = await Promise.all([
    page.waitForEvent('download'),
    page.getByRole('button', { name: 'Export CSV' }).click(),
  ]);

  expect(download.suggestedFilename()).toContain('.csv');
  const filePath = await download.path();
  expect(filePath).toBeTruthy();
});

​

Validation Cases You Should Not Skip

• Oversized files are rejected with clear error text.
• Invalid type (.exe, wrong MIME) is blocked.
• Malformed CSV or JSON shows row-level error details.
• Duplicate uploads are idempotent or clearly prevented.
• Upload cancellation leaves no partial server records.

​

Keep Upload Tests Stable

• Avoid random fixture data unless uniqueness is required.
• Use a small fixture for smoke tests and a large one for stress tests.
• Clean up created records by exact IDs after test completion.

​

Stably Features to Use for File Workflows

• Store storage credentials, import endpoints, and size limits in Stably Environments.
• Run high-parallel browser coverage on Stably Cloud for faster feedback.
• Schedule heavier large-file suites with Scheduled Test Runs during off-hours.
• Route failures to Slack/email with Alerts & Notifications so ingestion breakages are surfaced quickly.
• Use Stably Test Reporter artifacts (traces/screenshots) to debug flaky upload timing and download corruption.