- sanity validation of each of the 4 steps
- click through buttons Next/Back/Cancel
Notes:
- add data-testid attribute for the release select field b/c
there's no better way to query it
- add @testing-library/jest-dom for additional asserts
anticipate common mistakes
eslint-plugin-testing-library: for writing tests with Testing Library
eslint-plugin-jest-dom: for writing tests with jest-dom
As mentioned in the previous commit, `<Main>` doesn't really
belong in App.js, it instead belongs in LandingPage.js, because
it creates the html/css wrapper for the main contents, as a
sibling to the `<PageHeader>` component used in LandingPage.js.
However, including `<Main>` in LandingPage.js will cause the
tests to fail. Therefore, just the html and classes that
`<Main>` creates is used in LandingPage.js.
`<Main>` doesn't really belong in App.js given the html it renders,
but there's some additional thing happening with this component
that requires it to be here to support tests. This update addresses
the extra padding that it creates by being used at this level.
Closes#17
Basic jest tests are added for the landing page. These tests use the
react testing library so the enzyme dependencies are removed from the
package.json. The travis config is also updated.
The Main component in the LandingPage component has been moved to the
App component. This is required so the tests can mock the store without
any insights information.
* package.json: Clean up scripts
* travis: Run travis build scripts
These run with NODE_ENV=production, which is needed to have correct
routing on all clouddot instances.
The starter app has been updated over the last few months and new
options are required in the `scripts` section of `package.json`.
Bring the `scripts` section in line with the starter app to fix some
issues around routing requests to `/beta` in CI.
Signed-off-by: Major Hayden <major@redhat.com>
