-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
Port robot tests #4019
Port robot tests #4019
Conversation
@1letter thanks for creating this Pull Request and helping to improve Plone! TL;DR: Finish pushing changes, pass all other checks, then paste a comment:
To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically. Happy hacking! |
@gforcada we're almost through with porting CMFPlone robot tests to playwright but right now the
do you have an idea how to fix this? |
/cc @mauritsvanrees once this is done, I think we can update the coredev versions again... these playwright tests should be much more stable than the selenium ones. |
@petschki @mauritsvanrees @datakurre |
I think they can be removed yes. @stevepiercy Is the Looking at the history, the last real commit was from 2018, all commits afterwards look more like search-and-replace through the entire code base. |
@petschki yes, I think we add/remove things there... but your test was about which branches? 🤔 |
those PRs were tested (see job parameters):
So coredev branch in combination with package PR will not work then? EDIT: I'd check for a branch checkout first before changeing the |
robotframework-browser 18.x version pins are merged in coredev#6.1 and nvm is now activated for all jobs on jenkins. lets see what the tests say. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, that is a lot of work. Thanks!
I skimmed through the changes, they seem mostly simplifying tests, removing all kinds of 'wait until' because they are no longer needed, which is good.
Jenkins 3.12 passes. I have started 3.10. Once that is green, I think this is mergeable!
Or do one or more of the Jenkins nodes still need an update? BTW, node 3 is down currently, "no route to host". |
@mauritsvanrees sometimes one or two tests fails on jenkins, locally all is fine. it looks like scarce resources on the nodes. but in general, the tests are stable. |
@mauritsvanrees I had a discord session yesterday night with @gforcada where he fixed the jenkins configs to correctly install I'm not sure if the resource problems are related to the new |
@mauritsvanrees
|
I've merged all test-porting PRs and will fix the one failing test here. So no more extra parameters needed! |
@jenkins-plone-org please run jobs |
This is part of #3813
port robot tests