We support SAML 2.0 and OpenID Connect, so most identity providers are covered, including Okta, Azure AD, Google, and OneLogin. Read the setup instructions here. 

You can also invite new members to your QA Wolf team without contacting support. New members will receive an email to log in using a magic link or their identity provider if your workspace uses SSO. 

You can now configure the network speed when running your tests. Using network condition presets, you can select anything from 5G down to 2G, satellite, or congested WiFi and see how the app performs under real-world conditions. 

• Throttle network speed: Test what your app does when the connection is slow or unrealiable. ‍
• Test offline mode: See how your app handles losing connectivity entirely and whether it recovers when it comes back.

Check out our help docs to get started.

QA Wolf now lets you feed images, videos, and audio files directly into the iOS camera or microphone when testing on real iPhones and iPads. We’re opening up a ton of new testing possibilities for mobile teams:

• Scan a receipt, then convert it to a PDF or extract text with OCR
• Identify a song playing on the radio
• Record a video and post it on social media
• Scan barcodes and QR codes 
• Host a video chat and validate call quality on a second device
• …or anything else your app uses the camera and microphone for. 

You can also inject media into the camera roll, if there’s a test that uses media from the device itself.

QA Wolf now supports VPN configuration for iOS app testing, so you can test against internal staging environments, validate region-locked content, and use geo-specific APIs on real devices.

VPN sessions are configured per test run and torn down automatically, so there's no lingering state between runs and no manual setup for each run.

Read more about it here.

Whether your users have high-powered tablets or low-cost phones, your app should work across the entire Android ecosystem. QA Wolf’s Agentic Testing platform now gives you access to any device and OS combo that you need, and the infrastructure to run all your tests in parallel.

Read more: How we built it

Test on their device, not yours

The key to testing Android apps is to focus on the devices and OS combinations your users actually have in their hands. Every app has different needs and different customers—an app that works flawlessly on the latest flagship model could lag or crash on an entry-level model. A dual screen device will behave differently than a tablet. Testing your app on just one or two devices won’t give you full confidence. And testing on devices your customers don’t even use is a waste of time.

Build fast, test fast, ship fast

Our Android testing infrastructure gets mobile engineers up to speed with their web developer counterparts. Pre-warmed, GPU-powered emulators start up instantly and execute test suites in parallel, with real-world fidelity.

Support for biometrics, backgrounding, sensors, and radios means you can test the complex workflows where bugs are most likely to escape.

We're excited to announce QA Wolf has achieved SOC 2 Type II compliance!

QA Wolf helps teams automate testing so they can move fast without sacrificing quality. From day one, we have treated security and privacy core to how we build and run our platform, and our SOC 2 certification is proof of that commitment.

Learn more about our security and data protection practices.

QA Wolf is now HIPAA compliant!

We work with healthcare companies on everything from AI drug discovery, radiology, and e-prescriptions to FDA approval evidence and more. Until now, we've focused on non-sensitive environments. Now we can safely test workflows that handle PII and PHI, including production and issue trackers.

Get more details on our security and data protection here.

We just upgraded our runners to use WebRTC for lower latency, better performance, and live streaming that now works on mobile devices. 

WebRTC establishes a direct peer-to-peer connection between you and the runner, which means what you see is happening in real time. That makes a big difference if you’re testing games, video conferencing apps, or anything where the stream needs to keep up with fast motion.

👆Watch us playing a game live through the test runner with no lag or dropped frames—just don’t judge our ping pong skills. 

Every test run comes with logs, network requests, DOM snapshots, and traces. You can learn more about running tests in QA Wolf here.

Shiny new iPads were just installed on our device cloud, bringing complex iOS app testing to the big screen. 

On top of AppleID, Apple Pay, Face ID, and backgrounding, we also support iPad specific test cases:

• Split View and Slide Over
• Four- and five-finger gestures
• Corner swipes
• Multiple instances of your app

How tos are in our docs.

Now open for business: QA Wolf’s own device farm, so you can test iOS apps on real devices. 

Why build a device farm from scratch when we could rent capacity from somewhere else? Because they can’t support the range of complex testing that we can offer from infrastructure infrastructure designed and built for automated E2E testing:

• Push notifications, including when the app is running in the background
• Apple ID login and account switching
• Apple Pay and Apple Wallet
• Face ID and Touch ID
• Camera and photo library
• Background tasks and cross-app flows

Tests run in full parallel, and devices are kept in a ready state so that they launch immediately.

‍

It’s pretty straightforward to write E2E tests for a single user to complete a single workflow. Things get more complicated when you have thousands of E2E tests, some of which may depend on data or state from other tests. Or if your environments can’t handle that many concurrent runs. 

What do you do then? 

Run Rules let testers configure the order of individual tests and steps within tests. It’s all covered in our white paper. With Run Rules you can…

• Test multi-user workflows: Coordinate tests across different users and devices, like an Uber Rider and Driver that share data and state across two different users and devices.
• Share data between tests: Pass a user account, a recorded video, or a status update from one test to the next that needs it.
• Control the order tests run: Run one batch of tests before the next, or set a dependency so a test doesn’t start until another has completed a specific step.

Head to our docs for help setting up Run Rules.