Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add UI tests to CI #2007

Open
3 tasks done
mtrezza opened this issue Jan 21, 2022 · 7 comments · May be fixed by #2552
Open
3 tasks done

Add UI tests to CI #2007

mtrezza opened this issue Jan 21, 2022 · 7 comments · May be fixed by #2552
Labels
bounty:$100 Bounty applies for fixing this issue (Parse Bounty Program) type:ci CI related issue

Comments

@mtrezza
Copy link
Member

mtrezza commented Jan 21, 2022 •
edited
Loading

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
@parse-github-assistant
Copy link

parse-github-assistant bot commented Jan 21, 2022 •
edited
Loading

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature type:ci CI related issue and removed type:feature New feature or improvement of existing feature labels Jan 21, 2022
@mtrezza mtrezza changed the title Add UI tests Add UI tests to CI Jan 21, 2022
@mtrezza mtrezza pinned this issue Jan 21, 2022
@mtrezza mtrezza mentioned this issue Jan 23, 2022
Merged
5 tasks
@damianstasik damianstasik mentioned this issue Jan 29, 2022
Open
8 tasks
@mtrezza mtrezza mentioned this issue Apr 20, 2022
Merged
@mtrezza mtrezza mentioned this issue Jul 2, 2022
Open
@mtrezza mtrezza added bounty:$100 Bounty applies for fixing this issue (Parse Bounty Program) and removed bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) labels Jul 2, 2022
@paulovitin
Copy link
Contributor

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

@mtrezza
Copy link
Member Author

mtrezza commented Oct 4, 2022 •
edited
Loading

See #2030, something like that.

@mehulmathur16
Copy link

Hi @mtrezza, is this issue still open ?

@mtrezza
Copy link
Member Author

mtrezza commented Apr 30, 2024 •
edited
Loading

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

@mehulmathur16
Copy link

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

@mtrezza
Copy link
Member Author

mtrezza commented May 1, 2024 •
edited
Loading

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

@mehulmathur16 mehulmathur16 linked a pull request May 2, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bounty:$100 Bounty applies for fixing this issue (Parse Bounty Program) type:ci CI related issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test: Cypress e2e setup mehulmathur16/parse-dashboard
3 participants
@paulovitin @mtrezza @mehulmathur16