Compared to wix detox, I feel cavys documentation is lacking a bit. Would be nice to have more test scenario examples, as well as a CI integration example. Roadmap for upcoming features would be nice.

The example for findComponent includes a fictional import 😂:

import { hasButtonText } from './helpers';

This could be confusing, as it's not part of Cavy's API.

Please could we replace with something more generic? Or define what hasButtonText does in the example?

Cavy doesn't ship with compiled JS, so you need Jest to transform cavy as well as React Native code.

Additionally, the default index.test.js from cavy-cli gets picked up as a test file.

On a default React Native app I had some joy with this config in package.json:

  "jest": {
    "preset": "react-native",
    "transformIgnorePatterns": [
      "node_modules/(?!(react-native|@react-native|cavy)/)"
    ],
    "testPathIgnorePatterns": [
      "/index.test.js"
    ]
  }