Skip to content

Uploading a File for a Test

Certain tests require you to upload files when you schedule them.

Files to accompany tests can be code, or they can be supporting files. For example, if an iOS app is certificate-pinned, one of the supporting files to upload must be the certificate itself.

The kind of files to upload depends on the kind of test you plan to run:

  • Web

    Supporting Documents only.

  • Mobile

    Binary files that contain the compiled code to test. Supporting Documents are also allowed.

  • Source Code

    Source code files that contain the source to test. Supporting Documents are also allowed.

  • Network

    Supports files in .txt or .csv formats that contain the target IP list.

Note: After you schedule a test, you can change the uploaded file set at any time before the test completes.

The Managed Services Platform accepts files that have been saved in an archive format.

Important: For a mobile test, the code must be uploaded in its own .APK (Android) file or .IPA (iOS) file, and not in a different format type.

The table shows the file formats that you can upload:

`.7z` `.7zip` `.apk` `.bar` `.compress`
`.doc` `.docx` `.ear` `.gz` `.gzip`
`.ipa` `.iwa` `.j` `.jar` `.jar.pack`
`.json` `.mobileprovision` `.pdf` `.ppt`
`.pptx` `.rar` `.tar` `.tar.gz` `.tar-gz`
`.tar.xz` `.tar.z` `.tar-z` `.tgz` `.txz`
`.tz` `.war` `.xls` `.xlsx` `.z`
`.zip`        

Parent topic:Scheduling a Test

Related information

Scheduling Information for Web Targets

Scheduling Tests for Mobile Application Targets

Scheduling Information for Source Code Targets

Scheduling Tests for Network Targets