-
Notifications
You must be signed in to change notification settings - Fork 52
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
Proof of Concept - Playwright #571
Proof of Concept - Playwright #571
Conversation
Error showing in CI right now is also happening on
https://github.com/uPortal-Project/uPortal-start/runs/6866142583?check_suite_focus=true#step:8:381 |
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.
Is this at a point where we could add part (or all of this) to continuous integration (GitHub actions)?
@@ -1,5 +1,9 @@ | |||
apply plugin: 'com.github.node-gradle.node' | |||
|
|||
node { | |||
download = true |
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.
do we also want/need to declare the version of node, like:
uPortal-start/overlays/uPortal/build.gradle
Lines 17 to 20 in 9f24791
node { | |
version = nodejsVersion | |
download = true | |
} |
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.
need? no (at least not yet). When we bump up to the next version of the node plugin, we may want to control the version.
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.
It looks like the node versions between:
uPortal-start's current
uPortal-start/gradle.properties
Line 47 in 10e2921
nodejsVersion=12.16.1 |
and the gradle plugin are several major apart https://github.com/node-gradle/gradle-node-plugin/blob/1330dc94ce8cc5b2a64d77e4fd38c0792946378d/src/main/kotlin/com/github/gradle/node/NodeExtension.kt#L134
I do think uPortal-start's probably can be upgraded to 16, and this may be fine for now.
Just something to be aware of.
Not yet, since the portlet-list API has not yet been merged into the main branch of uPortal. |
The |
Good point - Setting up the test harness has nothing to do with the unmerged APIs, so that's not a blocker. We can also stand up a quick login / logout test so something is run. |
… playwrightDebug gradle task
This PR no longer is dependent on the portlet-lists api. It has a small number of page (ux) and api tests. |
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.
Could we include some of these tests as part of CI/CD?
Somewhere in/around
uPortal-start/.github/workflows/CI.yml
Lines 33 to 50 in 40ff401
- name: Build | |
run: ./gradlew -i -S build | |
- name: Tomcat Install | |
run: ./gradlew -i -S tomcatInstall | |
- name: Start Tomcat | |
run: ./gradlew -i -S tomcatStart | |
- name: Stop Tomcat | |
run: ./gradlew -i -S tomcatStop | |
- name: Clear Logs Tomcat | |
run: ./gradlew -i -S tomcatClearLogs | |
- name: Start Database | |
run: ./gradlew -i -S hsqlStart | |
- name: Init Data | |
run: ./gradlew -i -S dataInit | |
- name: Stop Database | |
run: ./gradlew -i -S hsqlStop | |
- name: Generate Skin | |
run: ./gradlew -i -S skinGenerate -DskinName=test |
Also could we look into the merge conflict?
merge conflict is now fixed. I'll add |
hmm the tests are not finding the expected data. taking a look... |
Setting aside the effort to include playwright in the CI flow for now. Tracked via #574 . |
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.
LGTM, thanks @cbeach47!
Checklist
Description of change
Proof of concept for Playwright test harness integration into uPortal-start.
Initial round of tests focus on an upcoming feature in uPortal, the portal-list api.
Near team goals: