GPT Driver User Guide
GPT Driver User Guide
GPT Driver User Guide
  • Getting Started
    • πŸš€Getting Started
    • πŸ”ƒUploading a Build File
    • πŸ§™β€β™‚οΈCreating Tests
      • Commands
        • Tap Command
        • Type Command
        • scroll Command
        • scrollUntilVisible Command
        • swipe Command
        • slide Command
        • wait Command
        • assertVisible Command
        • openLink Command
        • pressBackButton Command
        • launchApp Command
        • restartApp Command
      • πŸ‘οΈwithVision: Instructions
      • 🧠AI Instructions
    • 🏁Executing Tests
  • ☎️Device Configuration
  • βš™οΈUnder the Hood
  • Getting Around
    • ✏️Test Editor
    • πŸ›°οΈTest Overview
    • πŸ…Test Reports
    • ⏺️Test Recordings
    • πŸ‘€Settings
  • Best Practices
    • πŸ§‘β€πŸ’»API Documentation
    • Versioning
    • ↗️Templates
    • πŸ–‡οΈTest Dependencies & Prompt References
    • πŸ”—Deep Links
    • πŸ“§Email Verification
    • πŸ“‘Network Calls
    • πŸͺ‘Parameterized Strings
    • πŸ“Changing Device Location
    • πŸͺΆConditional Steps
    • 🐦Nested Steps
    • ⌚Smart Caching
    • πŸ—£οΈEnv. Variables
    • πŸ’―Bulk Step Testing for Robustness
    • πŸ“–Exact Text Assertions
    • πŸ’¬Auto-grant Permissions
  • πŸ§ͺMocking Network Data
  • 🌎Localization Testing
  • Code Generation
  • ❔FAQs
Powered by GitBook
On this page
  • Baseline Creation
  • Subsequent Runs
  • Minor Screen Differences Don't Affect Cache
  1. Best Practices

Smart Caching

Closed Beta: Smart Caching is currently under development and only available to a selected group of companies on paid plans.

Baseline Creation

After a successful run where GPT Driver interacts with the application, a baseline (essentially a cache) is automatically created. This baseline stores information about the screens encountered during the run, along with the actions GPT Driver took for each screen.

Subsequent Runs

During future test editor and cloud runs, GPT Driver checks two things:

  1. Prompt Match: Is the prompt used exactly the same as the previous successful run?

  2. Screen Match: Does the current sequence of screens exactly match what was encountered in the baseline?

Action Reuse: If both the prompt and screens match the baseline, GPT Driver efficiently replays the stored actions for each screen. This saves time and ensures consistency in repetitive tasks.

Handling Discrepancies: If there are any differences between the current screens and the baseline (e.g., a change in button text), GPT Driver recognizes the variation and relies on its reasoning capabilities to determine the best course of action.

Minor Screen Differences Don't Affect Cache

To improve efficiency, the cache is tolerant of minor discrepancies in the screen appearance. For example, slight variations in display time on the emulator won't cause GPT Driver to abandon the cached actions.

PreviousNested StepsNextEnv. Variables

Last updated 1 month ago

⌚