Why file testing validates uploads and downloads in Cypress - Automation Benefits in Action

Verify file upload and download functionality

Preconditions (2)

Step 1: Click on the upload button and select 'testfile.txt' from fixtures

Step 2: Submit the upload form

Step 3: Verify the upload success message is displayed

Step 4: Click the download link for the uploaded file

Step 5: Verify the downloaded file content matches 'testfile.txt'

✅ Expected Result: File uploads successfully with confirmation message and downloaded file content matches the uploaded file exactly

Automation Requirements - Cypress

Assertions Needed:

Upload success message is visible

Downloaded file content equals the uploaded file content

Best Practices:

Use cy.fixture() to load test files

Use cy.get() with data-cy attributes for stable selectors

Avoid hardcoded waits; use cy.intercept() or cy.wait() for network calls

Validate file content programmatically after download

Automated Solution

Cypress

describe('File Upload and Download Test', () => {
  it('should upload a file and verify download content', () => {
    cy.visit('/file-upload')

    // Upload file
    cy.get('[data-cy=file-upload-input]').attachFile('testfile.txt')
    cy.get('[data-cy=upload-submit]').click()

    // Verify upload success message
    cy.get('[data-cy=upload-success]').should('be.visible').and('contain.text', 'Upload successful')

    // Intercept download request
    cy.intercept('GET', '/download/testfile.txt').as('fileDownload')

    // Click download link
    cy.get('[data-cy=download-link]').click()

    // Wait for download request to complete
    cy.wait('@fileDownload').then((interception) => {
      // Verify downloaded file content matches fixture
      cy.fixture('testfile.txt', 'utf8').then((fixtureContent) => {
        expect(interception.response.body).to.equal(fixtureContent)
      })
    })
  })
})

This test visits the file upload page and uses attachFile to upload a test file from fixtures. It clicks the submit button and checks for a visible success message to confirm upload.

For download, it intercepts the GET request to the file URL, clicks the download link, and waits for the request to finish. Then it compares the downloaded file content from the response body with the original fixture content to ensure they match exactly.

Selectors use data-cy attributes for stability. No hardcoded waits are used; instead, cy.intercept and cy.wait ensure synchronization.

Common Mistakes - 3 Pitfalls

Using CSS classes or IDs that change frequently as selectors

Using cy.wait with fixed time instead of intercepting network calls

Not verifying the actual content of the downloaded file

Bonus Challenge

Now add data-driven testing with 3 different files to upload and verify

Show Hint

Practice

1. Why is file testing important when validating uploads and downloads in Cypress?

easy

A. It ensures files are correctly sent and received without errors.

B. It speeds up the test execution time significantly.

C. It automatically fixes file format issues during upload.

D. It replaces the need for manual testing completely.

Solution

1. Step 1: Understand the purpose of file testing

   File testing checks if files upload and download correctly without corruption or errors.

2. Step 2: Evaluate the options

   Only It ensures files are correctly sent and received without errors. correctly states that file testing ensures files are sent and received properly. Other options describe unrelated or incorrect benefits.

3. Final Answer:

   It ensures files are correctly sent and received without errors. -> Option A

4. Quick Check:

   File testing validates file transfer = A [OK]

Hint: File testing checks correctness of file transfer [OK]

Common Mistakes:

• Thinking file testing speeds up tests
• Believing it fixes file format issues automatically
• Assuming it removes manual testing needs

2. Which Cypress command is used to simulate a file upload in tests?

easy

A. cy.attachFile()

B. cy.readFile()

C. cy.downloadFile()

D. cy.uploadFile()

Solution

1. Step 1: Identify the command for file upload simulation

   Cypress uses the attachFile command from a plugin to simulate file uploads.

2. Step 2: Check other commands

   readFile reads files, downloadFile is not a core Cypress command, and uploadFile does not exist.

3. Final Answer:

   cy.attachFile() -> Option A

4. Quick Check:

   Upload simulation = attachFile [OK]

Hint: Use attachFile for uploads in Cypress [OK]

Common Mistakes:

• Confusing readFile with upload
• Using non-existent uploadFile command
• Assuming downloadFile uploads files

3. Given this Cypress code snippet, what will be the output if the file content is 'Hello World'?

cy.readFile('cypress/fixtures/sample.txt').then((content) => { cy.log(content) })

medium

A. Logs the file path instead of content.

B. Throws an error because readFile cannot read text files.

C. Logs 'Hello World' in the Cypress test runner console.

D. Logs an empty string because the file is not found.

Solution

1. Step 1: Understand cy.readFile behavior

   The cy.readFile command reads the file content as a string or JSON depending on file type.

2. Step 2: Analyze the code snippet

   The file 'sample.txt' contains 'Hello World', so cy.log(content) will output that string in the test runner console.

3. Final Answer:

   Logs 'Hello World' in the Cypress test runner console. -> Option C

4. Quick Check:

   readFile outputs file content = C [OK]

Hint: readFile logs actual file content [OK]

Common Mistakes:

• Thinking readFile throws error on text files
• Expecting file path instead of content
• Assuming file not found without checking path

4. Identify the error in this Cypress test code for file upload:

cy.get('input[type=file]').attachFile('image.png')
cy.get('button#submit').click()
cy.readFile('cypress/downloads/image.png').should('exist')

medium

A. The attachFile command is missing the plugin import.

B. readFile cannot check file existence with should('exist').

C. The selector for the file input is incorrect.

D. The submit button selector is invalid.

Solution

1. Step 1: Review attachFile usage

   Assuming the plugin is installed, attachFile usage is correct with the file input selector.

2. Step 2: Check readFile assertion

   readFile reads file content; it does not support should('exist') to check file presence. Instead, use cy.task or other methods.

3. Final Answer:

   readFile cannot check file existence with should('exist'). -> Option B

4. Quick Check:

   readFile + should('exist') invalid = B [OK]

Hint: readFile reads content, doesn't assert existence [OK]

Common Mistakes:

• Assuming should('exist') works with readFile
• Confusing selector correctness
• Forgetting to import attachFile plugin

5. You want to verify that a downloaded CSV file contains the header 'Name,Email,Phone'. Which approach using Cypress best validates this?

hard

A. Use cy.downloadFile to download and automatically validate the header.

B. Use cy.attachFile to upload the CSV and check the header.

C. Use cy.get to find the CSV file element and check its text content.

D. Use cy.readFile to read the CSV and assert the first line equals the header string.

Solution

1. Step 1: Understand file validation for downloads

   To validate a downloaded file's content, cy.readFile reads the file from disk.

2. Step 2: Validate CSV header

   Reading the CSV file and asserting the first line matches the expected header string is the correct approach.

3. Final Answer:

   Use cy.readFile to read the CSV and assert the first line equals the header string. -> Option D

4. Quick Check:

   Read file and check content = D [OK]

Hint: Read downloaded file and check header line [OK]

Common Mistakes:

• Using attachFile for download validation
• Trying to get file element text in DOM
• Assuming downloadFile auto-validates content