@testing-library/react-native 12.2.1 → 12.2.2

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/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.

package/examples/basic/__tests__/App.test.tsx

@@ -1,137 +0,0 @@
-import * as React from 'react';
-import {
-  render,
-  screen,
-  fireEvent,
-  userEvent,
-} from '@testing-library/react-native';
-import App from '../App';
-
-jest.useFakeTimers();
-
-/**
- * A good place to start is having a tests that your component renders correctly.
- */
-test('renders correctly', () => {
-  // Idiom: no need to capture render output, as we will use `screen` for queries.
-  render(<App />);
-
-  // Idiom: `getBy*` queries are predicates by themselves, but we will use it with `expect().toBeOnTheScreen()`
-  // to clarify our intent.
-  expect(
-    screen.getByRole('header', { name: 'Sign in to Example App' })
-  ).toBeOnTheScreen();
-});
-
-/**
- * Hint: It's best when your tests are similar to what a manual test scenarions would look like,
- * i.e. a series of actions taken by the user, followed by a series of assertions verified from
- * his point of view.
- */
-test('User can sign in successully with correct credentials', async () => {
-  // Setup User Event instance for realistic simulation of user interaction.
-  const user = userEvent.setup();
-
-  // Idiom: no need to capture render output, as we will use `screen` for queries.
-  render(<App />);
-
-  // Idiom: `getBy*` queries are predicates by themselves, but we will use it with `expect().toBeOnTheScreen()`
-  // to clarify our intent.
-  expect(
-    screen.getByRole('header', { name: 'Sign in to Example App' })
-  ).toBeOnTheScreen();
-
-  // Hint: we can use `getByLabelText` to find our text inputs using their labels.
-  await user.type(screen.getByLabelText('Username'), 'admin');
-  await user.type(screen.getByLabelText('Password'), 'admin1');
-
-  // Hint: we can use `getByRole` to find our button with given text.
-  await user.press(screen.getByRole('button', { name: 'Sign In' }));
-
-  // Idiom: since pressing button triggers async operation we need to use `findBy*` query to wait
-  // for the action to complete.
-  // Hint: subsequent queries do not need to use `findBy*`, because they are used after the async action
-  // already finished
-  expect(
-    await screen.findByRole('header', { name: 'Welcome admin!' })
-  ).toBeOnTheScreen();
-
-  // Idiom: use `queryBy*` with `expect().not.toBeOnTheScreen()` to assess that element is not present.
-  expect(
-    screen.queryByRole('header', { name: 'Sign in to Example App' })
-  ).not.toBeOnTheScreen();
-  expect(screen.queryByLabelText('Username')).not.toBeOnTheScreen();
-  expect(screen.queryByLabelText('Password')).not.toBeOnTheScreen();
-});
-
-/**
- * Another test case based on manual test scenario.
- *
- * Hint: Try to tests what a user would see and do, instead of assering internal component state
- * that is not directly reflected in the UI.
- *
- * For this reason prefer quries that correspond to things directly observable by the user like:
- * `getByRole`, `getByText`, `getByLabelText`, `getByPlaceholderText, `getByDisplayValue`, etc.
- * over `getByTestId` which is not directly observable by the user.
- *
- * Note: that some times you will have to resort to `getByTestId`, but treat it as a last resort.
- */
-test('User will see errors for incorrect credentials', async () => {
-  const user = userEvent.setup();
-  render(<App />);
-
-  expect(
-    screen.getByRole('header', { name: 'Sign in to Example App' })
-  ).toBeOnTheScreen();
-
-  await user.type(screen.getByLabelText('Username'), 'admin');
-  await user.type(screen.getByLabelText('Password'), 'qwerty123');
-  await user.press(screen.getByRole('button', { name: 'Sign In' }));
-
-  // Hint: you can use custom Jest Native matcher to check text content.
-  expect(await screen.findByRole('alert')).toHaveTextContent(
-    'Incorrect username or password'
-  );
-
-  expect(
-    screen.getByRole('header', { name: 'Sign in to Example App' })
-  ).toBeOnTheScreen();
-  expect(screen.getByLabelText('Username')).toBeOnTheScreen();
-  expect(screen.getByLabelText('Password')).toBeOnTheScreen();
-});
-
-/**
- * Do not be afraid to write longer test scenarios, with repeating act and assert statements.
- */
-test('User can sign in after incorrect attempt', async () => {
-  const user = userEvent.setup();
-  render(<App />);
-
-  expect(
-    screen.getByRole('header', { name: 'Sign in to Example App' })
-  ).toBeOnTheScreen();
-
-  const usernameInput = screen.getByLabelText('Username');
-  const passwordInput = screen.getByLabelText('Password');
-
-  await user.type(usernameInput, 'admin');
-  await user.type(passwordInput, 'qwerty123');
-  await user.press(screen.getByRole('button', { name: 'Sign In' }));
-
-  expect(await screen.findByRole('alert')).toHaveTextContent(
-    'Incorrect username or password'
-  );
-
-  // Workaround for clearing TextInput, clear() function will be added soon.
-  fireEvent.changeText(passwordInput, '');
-
-  await user.type(passwordInput, 'admin1');
-  await user.press(screen.getByRole('button', { name: 'Sign In' }));
-
-  expect(await screen.findByText('Welcome admin!')).toBeOnTheScreen();
-  expect(
-    screen.queryByRole('header', { name: 'Sign in to Example App' })
-  ).not.toBeOnTheScreen();
-  expect(screen.queryByLabelText('Username')).not.toBeOnTheScreen();
-  expect(screen.queryByLabelText('Password')).not.toBeOnTheScreen();
-});

package/examples/basic/app.json

@@ -1,31 +0,0 @@
-{
-  "expo": {
-    "name": "RNTL Example Basic",
-    "slug": "rntl-example-basic",
-    "version": "1.0.0",
-    "orientation": "portrait",
-    "icon": "./assets/icon.png",
-    "userInterfaceStyle": "light",
-    "splash": {
-      "image": "./assets/splash.png",
-      "resizeMode": "contain",
-      "backgroundColor": "#ffffff"
-    },
-    "updates": {
-      "fallbackToCacheTimeout": 0
-    },
-    "assetBundlePatterns": ["**/*"],
-    "ios": {
-      "supportsTablet": true
-    },
-    "android": {
-      "adaptiveIcon": {
-        "foregroundImage": "./assets/adaptive-icon.png",
-        "backgroundColor": "#FFFFFF"
-      }
-    },
-    "web": {
-      "favicon": "./assets/favicon.png"
-    }
-  }
-}

package/examples/basic/babel.config.js

@@ -1,6 +0,0 @@
-module.exports = function (api) {
-  api.cache(true);
-  return {
-    presets: ['babel-preset-expo'],
-  };
-};

package/examples/basic/components/Home.tsx

@@ -1,28 +0,0 @@
-import * as React from 'react';
-import { StyleSheet, View, Text } from 'react-native';
-
-type Props = {
-  user: string;
-};
-
-export function Home({ user }: Props) {
-  return (
-    <View style={styles.container}>
-      <Text accessibilityRole="header" style={styles.title}>
-        Welcome {user}!
-      </Text>
-    </View>
-  );
-}
-
-const styles = StyleSheet.create({
-  container: {
-    padding: 20,
-  },
-  title: {
-    alignSelf: 'center',
-    fontSize: 24,
-    marginTop: 8,
-    marginBottom: 40,
-  },
-});