Skip to content

Add UI tests to CI #2007

Open
Open

Description

@mtrezza

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.:

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

Activity

  1. parse-github-assistant commented on Jan 21, 2022

    @parse-github-assistant

    Thanks for opening this issue!

    • 🎉 We are excited about your ideas for improvement!
  2. added
    bounty:$50Bounty applies for fixing this issue (Parse Bounty Program)
    type:featureNew feature or improvement of existing feature
    type:ciCI related issue
    and removed
    type:featureNew feature or improvement of existing feature
    on Jan 21, 2022
  3. changed the title [-]Add UI tests[/-] [+]Add UI tests to CI[/+] on Jan 21, 2022
  4. pinned this issue on Jan 21, 2022
  5. added
    bounty:$100Bounty applies for fixing this issue (Parse Bounty Program)
    and removed
    bounty:$50Bounty applies for fixing this issue (Parse Bounty Program)
    on Jul 2, 2022
  6. paulovitin commented on Oct 4, 2022

    @paulovitin
    Contributor

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

  7. mtrezza commented on Oct 4, 2022

    @mtrezza
    MemberAuthor

    See #2030, something like that.

  8. mehulmathur16 commented on Apr 29, 2024

    @mehulmathur16

    Hi @mtrezza, is this issue still open ?

  9. mtrezza commented on Apr 30, 2024

    @mtrezza
    MemberAuthor

    Yep, it is, but there has been at least 1 PR: #2030, not sure what the state of that is.

  10. mehulmathur16 commented on May 1, 2024

    @mehulmathur16

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

  11. mtrezza commented on May 1, 2024

    @mtrezza
    MemberAuthor

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

  12. added
    bounty:$20Bounty applies for fixing this issue (Parse Bounty Program)
    and removed
    bounty:$100Bounty applies for fixing this issue (Parse Bounty Program)
    on Jan 16, 2026
  13. removed
    bounty:$20Bounty applies for fixing this issue (Parse Bounty Program)
    on Mar 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:ciCI related issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions