mirror of
https://github.com/DOI-DO/j40-cejst-2.git
synced 2025-07-30 12:21:17 -07:00
f7bfc979ba* Fix putting elements under <p> * Added Jest test to catch this mistake in the future. It does it by watching console.error(). To add in fixing the bug the test's emulated `console.error()` are echoed to the jest console.error() so they are not lost. * I tested this by putting a `<h1>` back into the `<p>` and it caught it. * Update scoreStepsList.test.tsx * added comment to move console.error ticket to global location Co-authored-by: Vim <86254807+vim-usds@users.noreply.github.com>
28 lines
778 B
TypeScript
28 lines
778 B
TypeScript
import * as React from 'react';
|
|
import {render} from '@testing-library/react';
|
|
import ScoreStepsList from './scoreStepsList';
|
|
import {LocalizedComponent} from '../test/testHelpers';
|
|
|
|
// TODO: Move this to a location that will detect on all tests
|
|
// See ticket: #550
|
|
beforeAll(() => {
|
|
jest.spyOn(global.console, 'error').mockImplementation((...params) => {
|
|
console.error(params);
|
|
});
|
|
});
|
|
|
|
describe('rendering of the component', () => {
|
|
const {asFragment} = render(
|
|
<LocalizedComponent>
|
|
<ScoreStepsList/>
|
|
</LocalizedComponent>,
|
|
);
|
|
|
|
it('should match the snapshot of the MapIntroduction component', () => {
|
|
expect(asFragment()).toMatchSnapshot();
|
|
});
|
|
|
|
it('No console errors', () => {
|
|
expect(console.error).toBeCalledTimes(0);
|
|
});
|
|
});
|