parse-dashboard icon indicating copy to clipboard operation
parse-dashboard copied to clipboard

Add UI tests to CI

Open mtrezza opened this issue 3 years ago • 7 comments

New Feature / Enhancement Checklist

Current Limitation

The lack of UI tests in the CI process makes it difficult to identify bugs before release. That leads to severe bugs likely to make it into release, e.g.:

  • https://github.com/parse-community/parse-dashboard/issues/1991
  • https://github.com/parse-community/parse-dashboard/issues/1994
  • https://github.com/parse-community/parse-dashboard/issues/2006
  • https://github.com/parse-community/parse-dashboard/issues/2194

The current manual testing before merging a PR is not reliable nor scalable.

Feature / Enhancement Description

Add UI tests to CI, starting with just a few basic tests as guidance on how to write these tests, that can be extended over time.

Example Use Case

n/a

Alternatives / Workarounds

Manual testing which is not reliable or scalable.

3rd Party References

n/a

mtrezza avatar Jan 21 '22 13:01 mtrezza

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza, Are you talking about Cypress or Integration with RTL ecosystem?

paulovitin avatar Oct 04 '22 06:10 paulovitin

See https://github.com/parse-community/parse-dashboard/pull/2030, something like that.

mtrezza avatar Oct 04 '22 11:10 mtrezza

Hi @mtrezza, is this issue still open ?

mehulmathur16 avatar Apr 29 '24 19:04 mehulmathur16

Yep, it is, but there has been at least 1 PR: https://github.com/parse-community/parse-dashboard/pull/2030, not sure what the state of that is.

mtrezza avatar Apr 30 '24 21:04 mtrezza

Okay @mtrezza. I'll give this a try.

mehulmathur16 avatar May 01 '24 05:05 mehulmathur16

@mehulmathur16 fantastic, please take a look at the discussion in #2030, it contains some feedback regarding how to implement this.

mtrezza avatar May 01 '24 10:05 mtrezza