What is an App?
In BugRadar, an app represents something you want to test - this can be a mobile app (iOS or Android) or a website.Key Concepts
- App: A mobile application or website you want to test
- Chrome Extension: An optional dependency included in web flow runs
- Build: A specific version of your mobile app (.app for iOS, APK for Android, or a url for a website)
- Default build: The build tests run on unless a run picks a different one
- Environment: Optional grouping to organize apps (e.g., Development, Staging, Production)
Creating a New App
Step 1: Navigate to Apps Page
Click on Apps in the sidebar navigation.Step 2: Click “Create New App”
Click the Create New App button in the top right corner.Step 3: Fill in App Details
Required Fields:- App Name: A descriptive name for your app (e.g., “MyApp iOS”)
- Bundle ID: Your app’s unique identifier (e.g.,
com.company.appname)
- App ID (iOS and Android): Expand App ID (optional) to set one. Only needed to keep several apps with the same bundle ID in one environment, for example one per release version.
- Environment: Assign the app to an environment for better organization
- Agent Context: Add special instructions for the agent (e.g., “The app requires biometric authentication on first launch”)
Step 4: Select Platform and Upload
Choose your app’s platform and provide the required build or URL:- iOS
- Android
- Web
- Chrome Extension
Upload Requirements:
- For simulator tests, upload a
.zipcontaining an.appbuilt for iOS Simulator - For physical-device tests, upload a Development or Ad Hoc signed
.ipa - BugRadar routes
.zip/.appbuilds to simulators and.ipabuilds to real devices - Each iOS build on the Apps page and in the Run dialog is tagged Simulator or Real device. If an app has only
.ipabuilds, Simulator is greyed out in the Run dialog until you upload a.app
Step 5: Complete Upload
Click Upload and wait for the file to upload. Once complete, your app will appear in the Apps list.Managing Builds
Each app can have many builds, so you can test new versions while keeping earlier ones available. Each app is a row on the Apps page, grouped under its environment. The row shows the app’s latest upload. Once an app has a build, click N builds (N URLs for a website, N versions for an extension) to list the 5 newest under the row. If there are more, View all builds (View all URLs, View all versions) opens every build in a side panel, where Search branches filters by branch name.Uploading a New Build
Click Upload build on the app’s row (Update URL for a website, Upload version for an extension), choose the file, and click Upload.Default build
Tests run on the default build unless a run picks a different one. Each upload becomes the default. To run tests on an older build instead, hover it in the builds list and click Make default. It stays the default until the next upload, and the row shows Default build is pinned to … so you know tests are not running on the newest upload.Build actions
Open a build’s ⋯ menu for:- Build variables: Set build variables
- Download: Download the build file (not for websites)
- Delete build: Remove the build. You can undo right after deleting.
Editing App Details
Changing App Name
- Hover the app name and click the pencil icon
- Edit the name
- Press Enter or click Save
App menu
Open the app’s ⋯ menu for:- Agent context: Special instructions for the agent when running flows on this app. Enter them and click Save.
- Change environment: Move the app to another environment, or No environment
- Copy app UUID: Copy the UUID that the Apps API and
BugRadar run --app-idaccept - Delete app
Organizing with Environments
Environments help you organize apps by deployment stage or purpose.Creating an Environment
- Navigate to Settings → Environments
- Click Create Environment
- Enter a name (e.g., “Staging”, “Production”, “QA”)
- Click Create
Assigning Apps to Environments
- During app creation: Select an environment from the dropdown
- After creation: Open the app’s ⋯ menu and choose Change environment
- Via CI/CD: Pass the
environmentparameter in the GitHub Action or Upload API to automatically assign the app to an environment on upload
app-id. The app’s row shows it next to the bundle ID. See Separate apps that share a bundle ID.
Troubleshooting
Common Issues
iOS:- For simulator runs, ensure the
.zipcontains a valid simulator.app - For physical-device runs, upload a Development or Ad Hoc signed
.ipa - Do not rename an IPA to
.zip; the extension determines the target device type - Verify the bundle ID matches what you entered
- Ensure the APK is properly signed
- Check that the file extension is
.apk - Verify the bundle ID matches the package name
- Only Manifest V3 extensions are supported
- Upload a
.zipof the unpacked extension, not a.crx - Keep
manifest.jsonat the archive root or inside one top-level folder - Extension-enabled runs use Chrome (default) or Chromium