Upload a File in Your App Using ATS

Last modified: November 19, 2024

Introduction

This how-to explains how to upload a file in your app using ATS. You have some test situations in which you must upload a file to finish that test situation. During manual testing, you upload this file from your local computer into your app. ATS works similar, the only difference is that the local computer is your Selenium hub.

This is regarding file uploads by ATS.

Quick summary:

Selenium Setup Uploading your own file Uploading a file Uploading possible?
Local Selenium Server (Docker)
Limited1
Yes
Yes
BrowserStack (SaaS)
No
Yes
Yes
Sauce Labs (SaaS)
No
No
No
Selenium SaaS Agent
Limited2
Yes
No

1 This only possible when you prepare your own files on that server.
2 This depends on where the agent is installed.

This how-to teaches you how to do the following:

  • Understand why it is difficult to upload files in your app using automated testing
  • Uploading a file using ATS
  • The approach for each Selenium setup

Prerequisites

Before starting with this how-to, make sure you have the following prerequisites in place:

Uploading a File

Introduction

To upload a file in your app, ATS must have access to that file. Selenium simulates a user on a local computer. When ATS gives the command to upload a file, it provides a file path to the file you want to upload. Since there are three different Selenium setups, there are also three different situations.

The first situation is that you use Selenium on a local server. This means Selenium has no access to your local files. But you can add these files to the server or create a set of generic test files for that server.

The second situation is that you use Selenium SaaS. This means Selenium has no access to your local files unless you use an agent. When you use the agent, situation 1 applies. If you do not use an agent the Selenium SaaS creates a VM session for each test case you run. This means there are no constant values like on your local Selenium server. Some Selenium SaaS providers upload a generic set of test files into each VM session that you can use in your test case. In the quick summary in 1 Introduction chapter you see which Selenium SaaS provides these files.

The third situation is that you use a Selenium SaaS agent. ATS executes the test on the machine on which you installed the agent. In most cases this is a server inside your network. ATS can find all the files on this machine.

Uploading a File Using ATS

ATS has a standard action for uploading files into your Mendix app. The Set File Manager action uploads a file from the local computer into the app using a file path. As explained earlier the file must be on the local machine for this to work.

The Set File Manager action

A possible filepath is:

C:\users\ats\documents\receipt-1.png

File Uploader widget in the app

Advice

Each Selenium setup has different possibilities. We advise that if you want to test the uploading of files in your Mendix app, you must use a generic test file set. Create a set of files to use in your tests and make sure that your Selenium setup has access to it.

Selenium Setup Advice
Local Selenium Server (Docker) Put all the generic files a test folder on your server.
Selenium SaaS Depends on the chosen provider.
Selenium SaaS Agent Install the agent on a server with your Mendix app. Also put the generic test files there.

Uploading a File Using a Local Selenium Server (Docker)

When testing using a local Selenium server, ATS executes the test on that server. The Set File Manager action only has access to the files on that server. You can create a generic set of test files or just add files to the server and use them in your tests.

Uploading a File in BrowserStack (SaaS)

When testing using the BrowserStack, ATS executes the test against a new VM session every time. So every run gets a new VM session and afterwards BrowserStack deletes the entire session. With this setup it is not possible to upload your own files. BrowserStack does provide a large set of test files that they upload in each VM session. You can use the Set File Manager action to achieve this.

Those files are always present so you don’t have to change the filepath every time.

You can find the BrowserStack test files here.

Uploading a File with a Selenium SaaS Agent

When you use a Selenium SaaS provider you can also use their agent. Each provider gives access to an agent that allows you to test on a local machine. In the Set File Manager action, you can provide the filepath. This filepath depends on where you activated the local machine. Either a local server or a local computer.

Next Up

You now learned how to upload a file and if it is possible with your Selenium set up. The next how-to is How to Assert Data Grid Rows. You find an overview of all the how-tos and the structure on the ATS 2 How-tos page. We advise you to follow the predefined structure.