Turn your manual testers into automation experts! Request a DemoStart testRigor Free

How to Generate a File for testRigor iOS Simulators

To test an iOS application on testRigor infrastructure it is important to remember that we use simulators. At the moment, testing on real devices is possible by integrating a 3rd party device farm like LambdaTest with testRigor.

Our simulators are able to test iOS applications compiled for x86 (Intel chips) or arm64 (Apple Silicon chips). The following steps describe the process to correctly generate an iOS application file ready to upload to testRigor.

  1. Open the application in Xcode.
  2. Click the application name at the top of the application.
  3. Select a simulator device.
  4. Setting the correct scheme is a one-time process if it has not been done before:
    • Click the application name at the top of the application.
    • Select Edit scheme.
    • A pop-up will open.
    • Go to Run section.
    • Select Release from the Build configuration dropdown.
    • Click the Close button at the bottom right of the popup.
  5. Select the device from the list at the top menu.
  6. Click Product in the menu bar at the top of the screen.
  7. Select Build. This will cause your app to render a new .app file, which may take a few minutes, but you should be able to continue the process up to Step 18.
  8. Click Xcode on the right of the Apple logo ( or ) at the top of the screen.
  9. Select Preferences or Settings.
  10. Select the Locations tab in the popup that opens.
  11. Click the right arrow ( or ) on the right of the Finder directory below Derived data.
  12. Open the DerivedData folder.
  13. Open the folder with the name of the desired app/build (this might have a randomized string of characters added to the name).
  14. Open the Build folder.
  15. Open the Products folder.
  16. Open the Release-iphonesimulator folder.
  17. The latest build should be in that folder; you can distinguish it from other files of a similar name by the date and time of creation. If it has not finished rendering, allow it to complete the process before moving on to the next step.
  18. Add the extension .app to the name of the file once it has completed rendering.
  19. Right click on the file with the application name + the .app extension (e.g., myiosfile.app).
  20. Select Compress.
  21. The file should now have the .zip extension.

Now you are ready to begin testing your iOS application on testRigor. If you have already created your iOS suite, simply upload the filename.app.zip file into the file input in Test Suite Details. If you have yet to create your test suite, the filename.app.zip file will need to be ready before attempting to do so.

You're 15 Minutes Away From Automated Test Maintenance and Fewer Bugs in Production
Simply fill out your information and create your first test suite in seconds, with AI to help you do it easily and quickly.
Achieve More Than 90% Test Automation
Step by Step Walkthroughs and Help
14 Day Free Trial, Cancel Anytime
“We spent so much time on maintenance when using Selenium, and we spend nearly zero time with maintenance using testRigor.”
Keith Powe VP Of Engineering - IDT
Related Articles

All-Inclusive Guide to Test Case Creation in testRigor

Test cases fuel test automation tools. Over the years, the process of automating these test cases has undergone many changes. ...

How to Create Tests Using Live Mode in testRigor?

testRigor offers a unique capability known as the ‘Live Mode‘ to create and validate test cases. Using it, you can ...

How to Automate Web Testing with testRigor

Web testing plays a crucial role in the software development lifecycle, allowing web applications to function correctly, provide ...
On our website, we utilize cookies to ensure that your browsing experience is tailored to your preferences and needs. By clicking "Accept," you agree to the use of all cookies. Learn more.
Cookie settings
Privacy Overview
This site utilizes cookies to enhance your browsing experience. Among these, essential cookies are stored on your browser as they are necessary for ...
Read more
Strictly Necessary CookiesAlways Enabled
Essential cookies are crucial for the proper functioning and security of the website.
Non-NecessaryEnabled
Cookies that are not essential for the website's functionality but are employed to gather additional data. You can choose to opt out by using this toggle switch. These cookies gather data for analytics and performance tracking purposes.