If you have a hanging test, though, I would suggest running VisualVM and taking a thread snapshot. One of ScalaTest's secret features is that we rename threads to indicate what suite and test is running. So you can find the thread running your hanging test (or figure out what test is causing a hang if you don't know), and see where in the test it is stuck.
Oh, I know why it's breaking, sort of. This is my first time writing a library, and I'm trying to do a better job, write better code. And in the process of improving things, there are some higher level tests that have broken. I just haven't gotten a chance to fix them all yet.
@max-peroch I haven't tried it, but that would be an interesting idea. There is some reflection scattered here and there, unfortunately. So it would be a subset. Mainly RefSpec, which can be cut out, and matchers. So if you just use a different style than RefSpec and use assertions, it might work fine.
I made some progress regarding the above. Although, it seems that the native version fails to "discover" my test suite... ie when I do
java -cp "lib/*" org.scalatest.tools.Runner -w "com.company" -eDF -R lib/my_tests.jar it works as expected, but ./scalatest-native -w "com.company" -eDF -R lib/my_tests.jar returns No tests were executed.. Am I missing something obvious? Adding -s com.company.MySuite fails with a ClassNotFoundException so it looks like the native version isn't even looking into my_tests.jar? At this point I am not sure yet if I did something wrong with the native image generation or if I don't use scalatest's runner properly, possibly both :)
3 replies
@max-peroch fyi, the current scalatest-native support relies on TestUtils to instantiate the class, here: https://github.com/scalatest/scalatest/blob/3.2.x-new/native/core/src/main/scala/org/scalatest/tools/TaskRunner.scala#L80
@max-peroch i wonder if you created the native image from our scalatest jar or the scalatest native jar file? i am not sure if graal will recognize scala-native produced jar 'special'. perhaps graal working with our jvm jar makes more sense.
@max-peroch fyi for the jvm version, it is just a java reflection call here: https://github.com/scalatest/scalatest/blob/3.2.x-new/jvm/core/src/main/scala/org/scalatest/tools/Framework.scala#L447
Hello everyone :) I created a repo with a summary of the Scala testing libraries ecosystem: https://github.com/LLCampos/state-of-the-art-scala-testing/ Should I add/change anything regarding scalatest?
Once I get PinS 5ed out the door, which is going to coincide with the Scala 3 release, which may coincide with this coming week, I'm going to focus on ScalaTest for a while before starting the Advanced Programming in Scala book.
or is it called a "room"
@ldeck I unfortunately don't know that answer so hopefully someone else does.
I have several other AnyFunSuite tests which do not throw this error. If it helps, the effected Scala3 project can be found here:
https://github.com/objektwerks/scala3
We will look at it first thing Monday.
@objektwerks @bvenners fyi I replied to the ticket already: https://github.com/scalatest/scalatest/issues/2030#issuecomment-841963220
@fourth44 following scalatest/scalatest#1950 , it seems @Sciss no longer able to reproduce it, but it reads like you are encountering it in again, are you able to reproduce it in a minimized project?
@fourth44 the need to set an explicit scalactic version hint that you may have a different version of scalactic on your classpath.
At least in the project listed in the issue, ScalaOSC, it seems to be fine now.
@loup-fox Sorry, I forgot to check gitter for a few days. Didn't see an email notification though it did come through. Was lost in my inbox. Anyway, Hmm. Did you by chance find a solution in the past two days? If not, I wonder if you can make a ticket with a bit more detail, here: https://github.com/scalatest/scalatest/issues Tnx.
@loup-fox ok this is totally weird. I noticed that I had my test under main not test. I moved it to test and it worked. So under main I got the Position not found for parameter pos problem. My build does not have ScalaTest in main, so I wonder if perhaps it just can't find ScalaTest (or its transitive dependency Scalactic) at all, and it just stops complaining after the first problem it encounters, which is for some reason Position.
Hi all, I realized following
shows
However, doing the same with following does not show
I accept that they two test cases might look the same but they mean different things conceptually. I assume second one reports in a way that is not a standard so Intellij does not understand how to show diff?
List(1, 2, 2, 3, 3, 3) should be (List(3, 2, 3, 1, 2, 3, 5))shows
<Click to see difference> in Intellij which is nice.However, doing the same with following does not show
<Click to see difference>List(1, 2, 2, 3, 3, 3) should contain theSameElementsAs List(3, 2, 3, 1, 2, 3, 5)I accept that they two test cases might look the same but they mean different things conceptually. I assume second one reports in a way that is not a standard so Intellij does not understand how to show diff?
I am trying to use akka (2.6.14)'s ScalaTestWithActorTestKit with scala 3.0.0; when run I get the following error message:
java.lang.NoSuchMethodError: 'void org.scalactic.TripleEqualsSupport.$init$(org.scalactic.TripleEqualsSupport)' I am using scalatest/scalactic 3.2.9 building with mill. Any help is appreciated.
Hi, I upgraded to scalatest 3.2.9 from 3.0.9 and I get this compilation error:
type mismatch;
found : ResultOfATypeInvocation[ScriptResult.ScriptResultFailure] (in org.scalatest.words)
required: ResultOfATypeInvocation[_] (in org.scalatest.matchers.dsl)
result.failed.get shouldBe a[ScriptResultFailure]but in the doc I read its supported the syntax smthg shouldBe a [Double] where am I wrong?
@vimalaguti I don't see anything you're doing wrong. Can you make an issue here: https://github.com/scalatest/scalatest/issues
@jorgeadriano fyi i have uploaded an example project for supersafe here: https://github.com/scalatest/supersafe-sbt-example
Thank you @cheeseng!
hi all,
I'm
I built an async test using
I'm
Scala-2.12 and scalatest 3.0I built an async test using
fixture.AsyncWordSpec which works properly. The problem comes when I try to change the default execution context (which is a serial execution context provided by ScalaTest) by the global (scala.concurrent.ExecutionContext.Implicits.global). The suite is completed almost immediately with 0 tests completed. is there anything additional that needs to be done so that inner futures can run in a multi-threading execution context like the global one?