@testing-library/react-native 12.2.1 → 12.3.0

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,14 +0,0 @@
----
-name: 🗣 Feature request
-about: Suggest an idea for React Native Testing Library.
-labels: 'feature request'
----
-
-## Describe the Feature
-<!-- Describe the requested Feature -->
-
-## Possible Implementations
-<!-- Describe how to implement the feature -->
-
-## Related Issues
-<!-- Link related issues here -->

package/.github/ISSUE_TEMPLATE/question.md

@@ -1,9 +0,0 @@
----
-name: 💬 Question
-about: You need help with React Native Testing Library.
-labels: 'question'
----
-
-## Ask your Question
-
-<!-- Ask your question -->

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,10 +0,0 @@
-<!-- Please provide enough information so that others can review your pull request. -->
-<!-- Keep pull requests small and focused on a single change. -->
-
-### Summary
-
-<!-- What existing problem does the pull request solve? Can you solve the issue with a different approach? -->
-
-### Test plan
-
-<!-- List the steps with which we can test this change. Provide screenshots if this changes anything visual. -->

package/.github/actions/setup-deps/action.yml

@@ -1,22 +0,0 @@
-name: Setup deps
-description: Setup Node.js and install dependencies
-
-runs:
-  using: composite
-  steps:
-    - name: Setup Node.js
-      uses: actions/setup-node@v3
-      with:
-        node-version: 18
-
-    - name: Cache deps
-      id: yarn-cache
-      uses: actions/cache@v3
-      with:
-        path: ./node_modules
-        key: ${{ runner.os }}-yarn-${{ hashFiles('./yarn.lock') }}
-
-    - name: Install deps
-      if: steps.yarn-cache.outputs.cache-hit != 'true'
-      run: yarn install --frozen-lockfile
-      shell: bash

package/.github/actions/setup-website-deps/action.yml

@@ -1,22 +0,0 @@
-name: Setup Website deps
-description: Setup Node.js and install website dependencies
-
-runs:
-  using: composite
-  steps:
-    - name: Setup Node.js
-      uses: actions/setup-node@v3
-      with:
-        node-version: 18
-
-    - name: Cache website deps
-      id: yarn-cache-website
-      uses: actions/cache@v3
-      with:
-        path: ./website/node_modules
-        key: ${{ runner.os }}-yarn-${{ hashFiles('./yarn.lock') }}-website
-
-    - name: Install website deps
-      if: steps.yarn-cache-website.outputs.cache-hit != 'true'
-      run: yarn --cwd website install --frozen-lockfile
-      shell: bash

package/.github/dependabot.yml

@@ -1,10 +0,0 @@
-version: 2
-updates:
-- package-ecosystem: npm
-  directory: "/"
-  schedule:
-    interval: "weekly"
-  open-pull-requests-limit: 3
-  ignore:
-    - dependency-name: "*"
-      update-types: ["version-update:semver-minor", "version-update:semver-patch"]

package/.github/workflows/deploy-website.yml

@@ -1,36 +0,0 @@
-name: Website
-
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  deploy:
-    name: Deploy to GitHub Pages
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and website deps
-        uses: ./.github/actions/setup-website-deps
-
-      - name: Build website
-        run: yarn --cwd website build
-
-      # Popular action to deploy to GitHub Pages:
-      # Docs: https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-docusaurus
-      - name: Deploy to GitHub Pages
-        uses: peaceiris/actions-gh-pages@v3
-        with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          # Build output to publish to the `gh-pages` branch:
-          publish_dir: ./website/build
-          # The following lines assign commit authorship to the official
-          # GH-Actions bot for deploys to `gh-pages` branch:
-          # https://github.com/actions/checkout/issues/13#issuecomment-724415212
-          # The GH actions bot is used by default if you didn't specify the two fields.
-          # You can swap them out with your own user credentials.
-          user_name: github-actions[bot]
-          user_email: 41898282+github-actions[bot]@users.noreply.github.com

package/.github/workflows/example-apps.yml

@@ -1,25 +0,0 @@
-name: Test Example Apps
-
-on: [workflow_dispatch]
-
-jobs:
-  test-example:
-    strategy:
-      matrix:
-        node: [14, 16, 18]
-        example: [basic, redux, react-navigation]
-    name: Test Example
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v3
-        with:
-          node-version: ${{ matrix.node }}
-          cache: 'yarn'
-
-      - name: Install and build
-        run: cd examples/${{ matrix.example }} && yarn install && yarn test

package/.github/workflows/main.yml

@@ -1,103 +0,0 @@
-name: Main
-on:
-  push:
-    branches: [main]
-  pull_request:
-    branches: ['**']
-
-jobs:
-  install-cache-deps:
-    runs-on: ubuntu-latest
-    name: Install and Cache deps
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup
-        uses: ./.github/actions/setup-deps
-
-  lint:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Lint
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Lint
-        run: yarn lint
-
-  typecheck:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Typecheck
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Typecheck
-        run: yarn typecheck
-
-  flow:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Flow
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Flow
-        run: yarn flow
-
-  test:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Test React 18
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Test React 18
-        run: yarn test:ci
-
-      - name: Upload coverage to Codecov
-        uses: codecov/codecov-action@v3
-
-  test-react-17:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Test React 17
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Test React 17
-        run: yarn test:ci:react:17
-
-  test-website:
-    runs-on: ubuntu-latest
-    name: Test Website
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and website deps
-        uses: ./.github/actions/setup-website-deps
-
-      - name: Build website
-        run: yarn --cwd website build

package/.gitignore

@@ -1,11 +0,0 @@
-node_modules
-coverage
-*.log
-.eslintcache
-build
-.idea
-.DS_Store
-
-# Ignore lock files in examples for now
-examples/**/yarn.lock
-.docusaurus

package/.prettierrc.js

@@ -1,5 +0,0 @@
-// added for Jest inline snapshots to not use default Prettier config
-module.exports = {
-  singleQuote: true,
-  trailingComma: "es5"
-}

package/CODE_OF_CONDUCT.md

@@ -1,73 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [oss@callstack.io](mailto:oss@callstack.io). All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct/
-
-[homepage]: https://www.contributor-covenant.org

package/CONTRIBUTING.md

@@ -1,64 +0,0 @@
-# Contributing
-
-## Code of Conduct
-
-We want this community to be friendly and respectful to each other. Please read [the full text](/CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.
-
-## Our Development Process
-
-The core team works directly on GitHub and all work is public.
-
-### Development workflow
-
-> **Working on your first pull request?** You can learn how from this _free_ series: [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github).
-
-1. Fork the repo and create your branch from `main` (a guide on [how to fork a repository](https://help.github.com/articles/fork-a-repo/)).
-2. Run `yarn` to setup the development environment.
-3. Do the changes you want and test them out in the example app before sending a pull request.
-
-### Commit message convention
-
-We prefix our commit messages with one of the following to signify the kind of change:
-
-- `fix`: bug fixes, e.g. fix incorrect error message.
-- `feat`: new features, e.g. add useful API.
-- `refactor`: code/structure refactor, e.g. new folder structure.
-- `docs`: changes into documentation, e.g. add usage example for `getByText`.
-- `test`: adding or updating tests, eg unit, snapshot testing.
-- `chore`: tooling changes, e.g. change circle ci config.
-- `BREAKING`: for changes that break existing usage, e.g. change API.
-
-Our pre-commit hooks verify that your commit message matches this format when committing.
-
-### Linting and tests
-
-We use `flow` for type checking, `eslint` with `prettier` for linting and formatting the code, and `jest` for testing. Our pre-commit hooks verify that the linter and tests pass when committing. You can also run the following commands manually:
-
-- `yarn flow`: run flow on all files.
-- `yarn lint`: run eslint and prettier.
-- `yarn test`: run tests.
-
-### Sending a pull request
-
-When you're sending a pull request:
-
-- Prefer small pull requests focused on one change.
-- Verify that `flow`, `eslint` and tests are passing.
-- Preview the documentation to make sure it looks good.
-- Follow the pull request template when opening a pull request.
-
-### Publishing a release
-
-If you have publish access to the NPM package, run the following from the main branch to publish a new release:
-
-```sh
-yarn publish
-```
-
-## Reporting issues
-
-You can report issues on our [bug tracker](https://github.com/callstack/react-native-testing-library/issues). Please follow the issue template when opening an issue.
-
-## License
-
-By contributing to `@testing-library/react-native`, you agree that your contributions will be licensed under its **MIT** license.

package/babel.config.js

@@ -1,22 +0,0 @@
-module.exports = {
-  presets: [
-    '@babel/preset-typescript',
-    '@babel/preset-react',
-    [
-      '@babel/preset-env',
-      {
-        targets: {
-          node: '14',
-        },
-        bugfixes: true,
-      },
-    ],
-  ],
-  plugins: ['@babel/plugin-proposal-class-properties'],
-  env: {
-    test: {
-      // https://github.com/react-native-community/upgrade-support/issues/152
-      plugins: ['@babel/plugin-transform-flow-strip-types'],
-    },
-  },
-};

package/build/helpers/getTextContent.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"getTextContent.js","names":["getTextContent","element","result","children","forEach","child","push","join"],"sources":["../../src/helpers/getTextContent.ts"],"sourcesContent":["import type { ReactTestInstance } from 'react-test-renderer';\n\nexport function getTextContent(\n  element: ReactTestInstance | string | null\n): string {\n  if (!element) {\n    return '';\n  }\n\n  if (typeof element === 'string') {\n    return element;\n  }\n\n  const result: string[] = [];\n  element.children?.forEach((child) => {\n    result.push(getTextContent(child));\n  });\n\n  return result.join('');\n}\n"],"mappings":";;;;;;AAEO,SAASA,cAAcA,CAC5BC,OAA0C,EAClC;EACR,IAAI,CAACA,OAAO,EAAE;IACZ,OAAO,EAAE;EACX;EAEA,IAAI,OAAOA,OAAO,KAAK,QAAQ,EAAE;IAC/B,OAAOA,OAAO;EAChB;EAEA,MAAMC,MAAgB,GAAG,EAAE;EAC3BD,OAAO,CAACE,QAAQ,EAAEC,OAAO,CAAEC,KAAK,IAAK;IACnCH,MAAM,CAACI,IAAI,CAACN,cAAc,CAACK,KAAK,CAAC,CAAC;EACpC,CAAC,CAAC;EAEF,OAAOH,MAAM,CAACK,IAAI,CAAC,EAAE,CAAC;AACxB"}

package/build/user-event/utils/host-components.d.ts

@@ -1,2 +0,0 @@
-import { ReactTestInstance } from 'react-test-renderer';
-export declare function isEditableTextInput(element: ReactTestInstance): boolean;

package/build/user-event/utils/host-components.js

@@ -1,11 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.isEditableTextInput = isEditableTextInput;
-var _hostComponentNames = require("../../helpers/host-component-names");
-function isEditableTextInput(element) {
-  return (0, _hostComponentNames.isHostTextInput)(element) && element.props.editable !== false;
-}
-//# sourceMappingURL=host-components.js.map

package/build/user-event/utils/host-components.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"host-components.js","names":["_hostComponentNames","require","isEditableTextInput","element","isHostTextInput","props","editable"],"sources":["../../../src/user-event/utils/host-components.ts"],"sourcesContent":["import { ReactTestInstance } from 'react-test-renderer';\nimport { isHostTextInput } from '../../helpers/host-component-names';\n\nexport function isEditableTextInput(element: ReactTestInstance) {\n  return isHostTextInput(element) && element.props.editable !== false;\n}\n"],"mappings":";;;;;;AACA,IAAAA,mBAAA,GAAAC,OAAA;AAEO,SAASC,mBAAmBA,CAACC,OAA0B,EAAE;EAC9D,OAAO,IAAAC,mCAAe,EAACD,OAAO,CAAC,IAAIA,OAAO,CAACE,KAAK,CAACC,QAAQ,KAAK,KAAK;AACrE"}

package/examples/basic/.expo/README.md

@@ -1,15 +0,0 @@
-> Why do I have a folder named ".expo" in my project?
-
-The ".expo" folder is created when an Expo project is started using "expo start" command.
-
-> What do the files contain?
-
-- "devices.json": contains information about devices that have recently opened this project. This is used to populate the "Development sessions" list in your development builds.
-- "packager-info.json": contains port numbers and process PIDs that are used to serve the application to the mobile device/simulator.
-- "settings.json": contains the server configuration that is used to serve the application manifest.
-
-> Should I commit the ".expo" folder?
-
-No, you should not share the ".expo" folder. It does not contain any information that is relevant for other developers working on the project, it is specific to your machine.
-
-Upon project creation, the ".expo" folder is already added to your ".gitignore" file.

package/examples/basic/.expo/packager-info.json

@@ -1,4 +0,0 @@
-{
-  "packagerPort": null,
-  "packagerPid": null
-}

package/examples/basic/.expo/settings.json

@@ -1,10 +0,0 @@
-{
-  "scheme": null,
-  "hostType": "lan",
-  "lanType": "ip",
-  "devClient": false,
-  "dev": true,
-  "minify": false,
-  "urlRandomness": null,
-  "https": false
-}

package/examples/basic/.expo-shared/assets.json

@@ -1,4 +0,0 @@
-{
-  "12bb71342c6255bbf50437ec8f4441c083f47cdb74bd89160c15e4f43e52a1cb": true,
-  "40b842e832070c58deac6aa9e08fa459302ee3f9da492c7e77d93d2fbf4a56fd": true
-}

package/examples/basic/.gitignore

@@ -1,14 +0,0 @@
-node_modules/
-.expo/
-dist/
-npm-debug.*
-*.jks
-*.p8
-*.p12
-*.key
-*.mobileprovision
-*.orig.*
-web-build/
-
-# macOS
-.DS_Store

package/examples/basic/App.tsx

@@ -1,20 +0,0 @@
-import * as React from 'react';
-import { SafeAreaView } from 'react-native';
-import { LoginForm } from './components/LoginForm';
-import { Home } from './components/Home';
-
-const App = () => {
-  const [user, setUser] = React.useState<string | null>(null);
-
-  return (
-    <SafeAreaView>
-      {user == null ? (
-        <LoginForm onLoginSuccess={setUser} />
-      ) : (
-        <Home user={user} />
-      )}
-    </SafeAreaView>
-  );
-};
-
-export default App;

package/examples/basic/README.md

@@ -1,11 +0,0 @@
-# Basic RNTL setup
-
-This example is shows a basic modern React Native Testing Library setup in a template Expo app.
-
-The app and related tests written in TypeScript, and it uses recommended practices like:
-
-- testing large pieces of application instead of small components
-- using `screen`-based queries
-- using recommended query types, e.g. `*ByText`, `*ByLabelText`, `*ByPlaceholderText` over `byTestId`
-
-You also use this repository as a reference when having issues in your RNTL configuration, as it contains the recommended Jest setup.