-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
ScalaTest 3.2 #353
ScalaTest 3.2 #353
Conversation
cheeseng
commented
Apr 18, 2022
•
edited
Loading
edited
- Updated to use ScalaTest 3.2.13.
- Dropped PhantomJS support.
- Added support for new MS Edge browser support.
…erSuite and AllBrowsersPerTest to def.
…-play into feature-scalatest-3.2
@@ -102,17 +101,23 @@ lazy val `scalatestplus-play` = project | |||
mimaSettings, | |||
organization := "org.scalatestplus.play", | |||
libraryDependencies ++= Seq( | |||
// Note: It seems like the only jackson version that works with all play, play-ws, play-json and selenium is 2.11.4. | |||
// play will bring in older version of selenium as well, so need excluding and let scalatest+selenium brings in the newer version.4 |
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.
If I remember correctly, this is because new selenium versions do not support Java 8 anymore, but right now Play still is build with Java 8.
However we are going to drop Java 8 very soon, so that would resolve that problem.
@mkurz I just pushed a quick commit according to your comments, do you mind to see if it is fit for merging now? Thanks! |
@mkurz I have resolved the conflict and upgraded to use scalatest+selenium 3.2.12.1, which includes a new support for MS Edge browser, do you mind to review and consider merging this when it is convenient for you? Thanks! |
@cheeseng Sure I will, I was a bit busy the last days, I will be back working on Play soon. Stay tuned. |
…-play into feature-scalatest-3.2
@mkurz Ping! I have resolved the conflict and this PR is ready for your review again. Thanks! |
Thanks @cheeseng! I want to set up GitHub actions before merging this pull request (actually, this is the last repo in the Play organization missing GHA) to make sure this change passes all the tests. |
@mkurz That's a good idea, I am adding CI build in scalatest+selenium (one of the dependency here) and it seems to work: scalatest/scalatestplus-selenium#20 But when I added the same ci.yml here it failed with this weird error:
I am not familiar with this, may be it is related to sbt-dynver? |
@mkurz By the way I think the current main is broken now? When I tried to build it I got the following error:
|
@mkurz I have added ci.yml that will run CI, here's the successfully run for this PR: https://github.com/playframework/scalatestplus-play/runs/7341113874?check_suite_focus=true Cheers. |
….0 and mockito 4.6.1.
@mkurz Ping again! I have updated the PR to use the newly released ScalaTest 3.2.13, the CI tests run that included in this PR seems to be green also: https://github.com/playframework/scalatestplus-play/runs/7604177607?check_suite_focus=true Cheers. |
@mkurz Ping again! I have updated the PR to use selenium 4.4.0 and htmlunit 3.64.0, and the CI build is green. |
@cheeseng Thanks again, fantastic! I will have a look asap 👍 |
…-play into feature-scalatest-3.2
…eServerPerSuiteWithOneBrowserPerTestSpec to prevent test failure flickerig.
@mkurz Ping again! I fixed the conflict and added some fix to avoid flickering of test failures, the CI passed also, do you mind to look at this again? Thanks. |
@cheeseng Sorry not being responsive here, I want to dedicate time tomorrow for this issue. |
@mkurz No worry at all, will be looking forward to tomorrow! :) For the sharable workflow, may I suggest that we address it in a separate PR? As it is quite different from the main intent for this PR. Cheers. |