+# AngularJS Testing Library
-
-
-
+Simple and complete Vue.js testing utilities that encourage good testing
+practices.
-
Simple and complete React DOM testing utilities that encourage good testing
-practices.
-
-
-
-[**Read The Docs**](https://testing-library.com/react) |
-[Edit the docs](https://github.com/testing-library/testing-library-docs)
-
-
-
-
-
+AngularJS Testing Library is a lightweight adapter built on top of
+[DOM Testing Library](https://github.com/testing-library/dom-testing-library).
-[![Build Status][build-badge]][build]
-[![Code Coverage][coverage-badge]][coverage]
[![version][version-badge]][package] [![downloads][downloads-badge]][npmtrends]
[![MIT License][license-badge]][license]
-
-[![All Contributors](https://img.shields.io/badge/all_contributors-102-orange.svg?style=flat-square)](#contributors)
-[![PRs Welcome][prs-badge]][prs] [![Code of Conduct][coc-badge]][coc]
-[![Join the community on Spectrum][spectrum-badge]][spectrum]
-
-[![Watch on GitHub][github-watch-badge]][github-watch]
-[![Star on GitHub][github-star-badge]][github-star]
-[![Tweet][twitter-badge]][twitter]
-
-
## Table of Contents
@@ -56,26 +19,16 @@ practices.
- [The problem](#the-problem)
- [This solution](#this-solution)
- [Installation](#installation)
- - [Suppressing unnecessary warnings on React DOM 16.8](#suppressing-unnecessary-warnings-on-react-dom-168)
- [Examples](#examples)
- [Basic Example](#basic-example)
- - [Complex Example](#complex-example)
- - [More Examples](#more-examples)
-- [Hooks](#hooks)
- [Guiding Principles](#guiding-principles)
-- [Docs](#docs)
-- [Issues](#issues)
- - [π Bugs](#-bugs)
- - [π‘ Feature Requests](#-feature-requests)
- - [β Questions](#-questions)
-- [Contributors](#contributors)
- [LICENSE](#license)
## The problem
-You want to write maintainable tests for your React components. As a part of
+You want to write maintainable tests for your AngularJS components. As a part of
this goal, you want your tests to avoid including implementation details of your
components and rather focus on making your tests give you the confidence for
which they are intended. As part of this, you want your testbase to be
@@ -85,10 +38,10 @@ your team down.
## This solution
-The `React Testing Library` is a very lightweight solution for testing React
-components. It provides light utility functions on top of `react-dom` and
-`react-dom/test-utils`, in a way that encourages better testing practices. Its
-primary guiding principle is:
+The `AngularJS Testing Library` is a very lightweight solution for testing
+components. It provides light utility functions on top of `angular-mocks` and
+`@testing-library/dom-testing-library`, in a way that encourages better testing
+practices. Its primary guiding principle is:
> [The more your tests resemble the way your software is used, the more
> confidence they can give you.][guiding-principle]
@@ -99,89 +52,71 @@ This module is distributed via [npm][npm] which is bundled with [node][node] and
should be installed as one of your project's `devDependencies`:
```
-npm install --save-dev @testing-library/react
+npm install --save-dev angularjs-testing-library
```
-This library has `peerDependencies` listings for `react` and `react-dom`.
+This library has `peerDependencies` listings for `angular` and `angular-mocks`.
You may also be interested in installing `@testing-library/jest-dom` so you can
use [the custom jest matchers](https://github.com/testing-library/jest-dom).
-> [**Docs**](https://testing-library.com/react)
-
-### Suppressing unnecessary warnings on React DOM 16.8
-
-There is a known compatibility issue with React DOM 16.8 where you will see the
-following warning:
-
-```
-Warning: An update to ComponentName inside a test was not wrapped in act(...).
-```
-
-If you cannot upgrade to React DOM 16.9, you may suppress the warnings by adding
-the following snippet to your test configuration
-([learn more](https://github.com/testing-library/react-testing-library/issues/281)):
-
-```js
-// this is just a little hack to silence a warning that we'll get until we
-// upgrade to 16.9: https://github.com/facebook/react/pull/14853
-const originalError = console.error
-beforeAll(() => {
- console.error = (...args) => {
- if (/Warning.*not wrapped in act/.test(args[0])) {
- return
- }
- originalError.call(console, ...args)
- }
-})
-
-afterAll(() => {
- console.error = originalError
-})
-```
-
## Examples
### Basic Example
-```jsx
+```js
// hidden-message.js
-import React from 'react'
-
-// NOTE: React Testing Library works with React Hooks _and_ classes just as well
-// and your tests will be the same however you write your components.
-function HiddenMessage({children}) {
- const [showMessage, setShowMessage] = React.useState(false)
- return (
-
+`
+
+angular.module('atl', []).component('atlHiddenMessage', {
+ template,
+ controller: HiddenMessage,
+ bindings: {
+ message: '<',
+ },
+})
// __tests__/hidden-message.js
// these imports are something you'd normally configure Jest to import for you
-// automatically. Learn more in the setup docs: https://testing-library.com/docs/react-testing-library/setup#cleanup
+// automatically.
import '@testing-library/jest-dom/extend-expect'
// NOTE: jest-dom adds handy assertions to Jest and is recommended, but not required
-import React from 'react'
-import {render, fireEvent} from '@testing-library/react'
-import HiddenMessage from '../hidden-message'
+import angular from 'angular'
+import 'angular-mocks'
+import {render, fireEvent} from 'angularjs-testing-library'
+import '../hidden-message'
+
+beforeEach(() => angular.mock.module('atl'))
test('shows the children when the checkbox is checked', () => {
const testMessage = 'Test Message'
const {queryByText, getByLabelText, getByText} = render(
- {testMessage},
+ `
+
+ `,
+ {
+ scope: {
+ testMessage,
+ },
+ },
)
// query* functions will return the element or null if it cannot be found
@@ -197,139 +132,13 @@ test('shows the children when the checkbox is checked', () => {
})
```
-### Complex Example
-
-```jsx
-// login.js
-import React from 'react'
-
-function Login() {
- const [state, setState] = React.useReducer((s, a) => ({...s, ...a}), {
- resolved: false,
- loading: false,
- error: null,
- })
-
- function handleSubmit(event) {
- event.preventDefault()
- const {usernameInput, passwordInput} = event.target.elements
-
- setState({loading: true, resolved: false, error: null})
-
- window
- .fetch('/api/login', {
- method: 'POST',
- headers: {'Content-Type': 'application/json'},
- body: JSON.stringify({
- username: usernameInput.value,
- password: passwordInput.value,
- }),
- })
- .then(r => r.json())
- .then(
- user => {
- setState({loading: false, resolved: true, error: null})
- window.localStorage.setItem('token', user.token)
- },
- error => {
- setState({loading: false, resolved: false, error: error.message})
- },
- )
- }
-
- return (
-
-
- {state.error ?
{state.error.message}
: null}
- {state.resolved ? (
-
Congrats! You're signed in!
- ) : null}
-
- )
-}
-
-export default Login
-
-// __tests__/login.js
-// again, these first two imports are something you'd normally handle in
-// your testing framework configuration rather than importing them in every file.
-import '@testing-library/jest-dom/extend-expect'
-import React from 'react'
-import {render, fireEvent} from '@testing-library/react'
-import Login from '../login'
-
-test('allows the user to login successfully', async () => {
- // mock out window.fetch for the test
- const fakeUserResponse = {token: 'fake_user_token'}
- jest.spyOn(window, 'fetch').mockImplementationOnce(() => {
- return Promise.resolve({
- json: () => Promise.resolve(fakeUserResponse),
- })
- })
-
- const {getByLabelText, getByText, findByRole} = render()
-
- // fill out the form
- fireEvent.change(getByLabelText(/username/i), {target: {value: 'chuck'}})
- fireEvent.change(getByLabelText(/password/i), {target: {value: 'norris'}})
-
- fireEvent.click(getByText(/submit/i))
-
- // just like a manual tester, we'll instruct our test to wait for the alert
- // to show up before continuing with our assertions.
- const alert = await findByRole('alert')
-
- // .toHaveTextContent() comes from jest-dom's assertions
- // otherwise you could use expect(alert.textContent).toMatch(/congrats/i)
- // but jest-dom will give you better error messages which is why it's recommended
- expect(alert).toHaveTextContent(/congrats/i)
- expect(window.localStorage.getItem('token')).toEqual(fakeUserResponse.token)
-})
-```
-
-### More Examples
-
-> We're in the process of moving examples to the
-> [docs site](https://testing-library.com/docs/example-codesandbox)
-
-You'll find runnable examples of testing with different libraries in
-[the `react-testing-library-examples` codesandbox](https://codesandbox.io/s/github/kentcdodds/react-testing-library-examples).
-Some included are:
-
-- [`react-redux`](https://codesandbox.io/s/github/kentcdodds/react-testing-library-examples/tree/master/?fontsize=14&module=%2Fsrc%2F__tests__%2Freact-redux.js&previewwindow=tests)
-- [`react-router`](https://codesandbox.io/s/github/kentcdodds/react-testing-library-examples/tree/master/?fontsize=14&module=%2Fsrc%2F__tests__%2Freact-router.js&previewwindow=tests)
-- [`react-context`](https://codesandbox.io/s/github/kentcdodds/react-testing-library-examples/tree/master/?fontsize=14&module=%2Fsrc%2F__tests__%2Freact-context.js&previewwindow=tests)
-
-You can also find React Testing Library examples at
-[react-testing-examples.com](https://react-testing-examples.com/jest-rtl/).
-
-## Hooks
-
-If you are interested in testing a custom hook, check out [React Hooks Testing
-Library][react-hooks-testing-library].
-
-> NOTE it is not recommended to test single-use custom hooks in isolation from
-> the components where it's being used. It's better to test the component that's
-> using the hook rather than the hook itself. The `React Hooks Testing Library`
-> is intended to be used for reusable hooks/libraries.
-
## Guiding Principles
> [The more your tests resemble the way your software is used, the more
> confidence they can give you.][guiding-principle]
We try to only expose methods and utilities that encourage you to write tests
-that closely resemble how your react components are used.
+that closely resemble how your components are used.
Utilities are included in this project based on the following guiding
principles:
@@ -337,193 +146,13 @@ principles:
1. If it relates to rendering components, it deals with DOM nodes rather than
component instances, nor should it encourage dealing with component
instances.
-2. It should be generally useful for testing individual React components or
- full React applications. While this library is focused on `react-dom`,
- utilities could be included even if they don't directly relate to
- `react-dom`.
+2. It should be generally useful for testing individual AngularJS components or
+ full AngularJS applications.
3. Utility implementations and APIs should be simple and flexible.
At the end of the day, what we want is for this library to be pretty
light-weight, simple, and understandable.
-## Docs
-
-[**Read The Docs**](https://testing-library.com/react) |
-[Edit the docs](https://github.com/testing-library/testing-library-docs)
-
-## Issues
-
-_Looking to contribute? Look for the [Good First Issue][good-first-issue]
-label._
-
-### π Bugs
-
-Please file an issue for bugs, missing documentation, or unexpected behavior.
-
-[**See Bugs**][bugs]
-
-### π‘ Feature Requests
-
-Please file an issue to suggest new features. Vote on feature requests by adding
-a π. This helps maintainers prioritize what to work on.
-
-[**See Feature Requests**][requests]
-
-### β Questions
-
-For questions related to using the library, please visit a support community
-instead of filing an issue on GitHub.
-
-- [Spectrum][spectrum]
-- [Reactiflux on Discord][reactiflux]
-- [Stack Overflow][stackoverflow]
-
-## Contributors
-
-Thanks goes to these people ([emoji key][emojis]):
-
-
-
-