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.

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

Move all tests over to electron #4484

Open
wants to merge 33 commits into
base: main
Choose a base branch
from
Open

Move all tests over to electron #4484

wants to merge 33 commits into from

Conversation

lf94
Copy link
Contributor

@lf94 lf94 commented Nov 14, 2024

The electron tests are able to cover both web and desktop variants of the application. This PR moves any web-only tests over to electron.

The motivation for this is there are aspects of the application that interact with the external system and can affect the application. Our tests completely miss these effects, and cause incidents.

Copy link

vercel bot commented Nov 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
modeling-app ✅ Ready (Inspect) Visit Preview Nov 29, 2024 11:46pm

Copy link

qa-wolf bot commented Nov 14, 2024

QA Wolf here! As you write new code it's important that your test coverage is keeping up.
Click here to request test coverage for this PR!

@lf94
Copy link
Contributor Author

lf94 commented Nov 14, 2024

I think https://github.com/KittyCAD/modeling-app/actions/runs/11845816046/job/33014820216?pr=4484 is indicating we have 35 failures we've always been missing in our electron app. I'll correct them as part of this transition. It could take some time

@lf94
Copy link
Contributor Author

lf94 commented Nov 14, 2024

@nadr0 would you know why it says "expected..." ? Is it because we have them as required in settings and GH doesn't know this when they're removed?

@@ -221,136 +216,3 @@ jobs:
retention-days: 30
overwrite: true


electron:
Copy link
Collaborator

@nadr0 nadr0 Nov 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did we delete this electron configuration and make the web one above the new electron configuration?

If we are deprecating web, we should have used the electron configuration that already runs and works.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They were 99% the same 🤷

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My only concern is that we completely deleted the electron .yml configuration and then update the browser configuration to be electron.

I looked at them both side by side but more reviewers is always welcomed

@@ -0,0 +1,37 @@
#!/bin/sh
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope intended on removing it

@nadr0
Copy link
Collaborator

nadr0 commented Nov 25, 2024

Okay I am caught up on this work, I see that we are deprecating browser and moving it to electron.
Once this PR is ready, I can help coordinate disabling the browser playwright tests from the repository settings.

My only concern is that we completely deleted the electron .yml configuration and then update the browser configuration to be electron.

I would have to diff both of those configurations to see if there is anything subtle between the two in the pipeline job. My gut reaction would be completely delete browser and leave electron as the base because that is the one we already have running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants