User guide

TabQA Pro Guide: Log Triage, Performance HUD, UI Inspection, and Environment Simulation

Free provides local mirroring and evidence capture. Pro adds AI-assisted log triage, performance HUD, UI inspection, and environment simulation.

Direct answer

TabQA Pro helps engineers investigate Android defects beyond evidence capture. Free provides mirroring, Network and Console capture, logs, screenshots, and video. Pro adds AI-assisted log triage, performance HUD, UI inspection, and environment simulation. Diagnostic results are investigation leads that need verification against actual reproduction.

1. Free and Pro features

FeatureFreePro
WebUSB mirroring, file transfer, and local evidence captureIncludedIncluded
Chrome / debug-enabled WebView Network, Console, and HARIncludedIncluded
Standard video and rolling bufferStandard video up to 180 seconds; rolling buffer includedSame as Free
Credential risk warningsIncludedIncluded
AI-assisted log triageNot includedP1/P2/P3 classification and noise filtering
Performance HUD and jank analysisNot includedFPS, CPU, PSS memory, temperature, and investigation tips
UI inspection, smart assertions, and A11y hintsNot includedElement properties, Appium examples, and accessibility hints
Environment simulation and health reportsNot includedLow battery, activity recreation, large fonts, and offline scenarios

Standard recording is currently limited to 180 seconds in both Free and Pro. Both include the rolling buffer; Pro does not include unlimited recording.

2. AI-assisted log triage

  1. Connect a device, select the target app, and open live logs.
  2. Choose AI triage to review categories, severity, and filtered issue logs.
  3. Check P1 crashes and P2 ANRs first, then share relevant logs with reproduction steps.

AI classifications, possible jank causes, and accessibility hints assist investigation. Verify them against logs, reproduction, and specialist tools. Response time depends on the network, device, and service.

3. Performance HUD and jank analysis

  1. Start mirroring and open the performance HUD.
  2. Reproduce stutter while reviewing FPS, CPU, PSS memory, battery temperature, and jank events.
  3. Use possible causes such as GC pressure, main-thread I/O, or overdraw as leads for specialist profiling.

Metric availability depends on the Android version, device permissions, and app state. Suggested causes are not confirmed code root causes.

4. Credential risk warnings

Credential risk warnings are currently available in both Free and Pro, for captured Chrome or debug-enabled WebView requests only.

  • Review risk warnings in the Network panel and check credential patterns in URLs, headers, and bodies.
  • Native networking libraries such as OkHttp and Retrofit are not covered. Detection does not identify every password, token, or personal data field.
  • Default redaction can hide credential patterns. No warning does not establish security or certify compliance.

5. UI inspection and smart assertions

  1. Open UI inspection in the mirroring toolbar and select a node.
  2. Review text, identifiers, state, and bounds, then copy a suggested Python/Appium assertion.
  3. Check touch target and missing accessibility label hints, and verify locators and scripts on the target device.

Adapt example code to your test suite. Accessibility hints do not replace a full accessibility audit.

6. Environment simulation and health reports

  1. Select an app in the environment sandbox and configure low battery, activity recreation, large fonts, dark mode, animations, or offline scenarios.
  2. Trigger memory trim or process termination as needed, then reproduce and check state recovery and logs.
  3. Generate and copy the Markdown environment report. Restore simulation settings after testing.

Device permissions can prevent simulation commands. Activity recreation and process termination are different operations. Reports currently reflect selected settings and do not automatically aggregate actual crashes or ANRs; scores do not establish a complete resilience assessment.

7. Activation, offline fallback, and data handling

After an AI request fails or times out, log triage, credential detection, UI assertions, and jank analysis fall back to local rules. Rule coverage can differ from cloud results. Initial activation needs internet access; offline Pro use still requires a valid license.

Capture attachments and OCR are processed locally. AI analysis sends log text, request information, UI properties, or performance metrics to the configured service. Credential analysis may also send requests during page debugging in Free; see the privacy policy.

  1. Follow the purchase link on the pricing page and obtain your Order ID or License Key.
  2. Click Pro in the side panel, enter the credential, and activate online. Check the license expiry.
  3. Use advanced tools as needed. Contact [email protected] when moving workstations or reaching a binding limit.

Frequently asked questions

Does Pro remove the standard recording limit?

Standard recording is currently limited to 180 seconds in both Free and Pro. Both include the rolling buffer; Pro does not include unlimited recording.

Are offline diagnostics equivalent to cloud results?

After an AI request fails or times out, log triage, credential detection, UI assertions, and jank analysis fall back to local rules. Rule coverage can differ from cloud results. Initial activation needs internet access; offline Pro use still requires a valid license.

Does deactivating let me immediately switch computers?

Device limits depend on the purchased license. Deactivation only clears the current browser's license data; it does not release server bindings. Contact [email protected] for migration or binding-limit issues.

Sources and basis