Open britt6612 opened 2 years ago
We should include a userAgent
test in our end-to-end testing since we had to remove it from our unit tests in https://github.com/grommet/grommet/pull/6066
It would also be good to add a test for responsive tabs. Since the responsive tabs rely on measuring the size of the container this type of test doesn't work well in jest and is better suited for an end to end environment. (related to https://github.com/grommet/grommet/pull/6137)
Decided that this application is going to live under grommet and be separate from a starter app The end-to-end testing aims to build our confidence that grommet components are working in real applications. We want to have a better way to have fewer regressions as well as test components in ways we wouldn't necessarily recommend for hpe applications.
We should add an end to end test for DateInput within a Form with validation="blur"
. See https://github.com/grommet/grommet/pull/6436#discussion_r1000999264)=
We should add end to end tests for the following PRSs since they can't be tested in jest https://github.com/grommet/grommet/pull/6536 https://github.com/grommet/grommet/pull/6535 https://github.com/grommet/grommet/pull/6575
We should add tests for the following issues: https://github.com/grommet/grommet/pull/6632 https://github.com/grommet/grommet/pull/6587 https://github.com/grommet/grommet/pull/6613
We should add a test for: https://github.com/grommet/grommet/pull/6844
In order to help with regressions with Grommet components, it would be nice to have a rich example of an application that uses a number of different components. This will help with how the components are being used in addition to having the snapshot in Grommet. We can create a narrative around how a user would go through an application and test each task to add to our testing coverage.