Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    Carlos Eduardo de Paula
    :point_up: Edit: This is a sample:
      def dummy(): Any = true
      it should "test Any as bool" in {
        dummy() should be (true) // <- doesn't compile
        dummy() should be (true.asInstanceOf[Any]) // <- works fine
        dummy() should be (1) // <- compiles fine, fails as expected
    Kilic Ali-Firat

    Hey I just migrated from scalatest 3.2.0 to 3.2.1 and I see a weird behaviour in the output.
    In the 3.2.0, I see in the stdout my suite tests something like :

    - test1 
    - test2 
    All tests passed

    While in 3.2.1, I have some tests that do no passed but I only get :

    info] *** 24 TESTS FAILED ***
    [error] Failed tests:
    [error]     FunctionalTestSpec
    [error] (functional-test / Test / test) sbt.TestsFailedException: Tests unsuccessful
    [error] Total time: 87 s (01:27), completed 20 déc. 2021, 14:08:05

    I don't see now which tests are not passing which is a bit hard to debug :-D
    I've checked the releases notes and I don't have the feeling to miss something but maybe you can help me ?

    Kilic Ali-Firat
    So I've tried the 3.2.3 and now I get the output so let's say that I will forget the 3.2.1
    Mark Dixon
    abstract class Test extends Suite with FunSuiteLike with Matchers {}
    This has me stumped, does anyone know why this does not compile in 2.13 when it does in 2.12 (Scalatest 3.0.9):
    illegal trait super target found for method withFixture required by trait TimeLimitedTests;
    abstract class Context {}
    abstract class TestTest[CONTEXT <: Context] extends Test with TimeLimitedTests {
    expected: protected def withFixture: ((test: _1.NoArgTest): org.scalatest.Outcome) forSome { val _1: [CONTEXT <: Context]TestTest[CONTEXT] } in trait TestSuiteMixin
        override def timeLimit: Span = Span.Max
    found : protected def withFixture: ((test: _1.NoArgTest): org.scalatest.Outcome) forSome { val _1: [CONTEXT <: Context]TestTest[CONTEXT] } in trait TestSuite;
    Shawn Garner
    Hello, I'm using ScalaCheckDrivenPropertyChecks from scalatestplus and when a property based test it displays the inputs but not the seed.
    Is there a way to display the seed and also run the tests with a given seed?
    This is when a property based test fails
    Henri Cook
    Hi everyone. Has 3.2.11 been released? Scala steward has raised an MR for me but I can't see it on the github releases page. Checking the releases page is part of my standard defence against supply chain attack (or is there a better source??)
    Chua Chee Seng
    @henricook Yes i am working on the release notes, will get it up ASAP.
    Henri Cook
    Thanks! Sorry to bother :-)
    Does Scalatest have a way to get diffs in the output?
    If you compare two values and they are similar but it's hard to see exactly where they differ
    Everton Eckert Schneider
    I would like to see 2 things in my suites of tests running using ScalaTest.
    1. Is it possible to count the number of assertions? One test may in some cases have more than one assertion, so instead of counting the number of tests, I wonder if I could get the total of assertions.
    2. Is there a kind of checkstyle to ensure that each test (it in FunAnySpec) has at least one assertion? In a group of suites of ~10K tests, I have already found in some cases a test without any assertion, so I'd like to know if I could have a way to check that.
    Carlos Eduardo de Paula
    I recently joined the Scala server on Discord and thought it would be beneficial to the community to maybe have a Scalatest channel over there. Since the server already have more than 700 users online, it's a great place to gather the community and discuss issues on the Scala ecosystem. What are the opinions of the scalatest users and maintainers about this?
    I asked the maintainers over there and they are open to create a new scalatest channel on the Community category, as long as scalatest community is ok with that avoiding fragmentation
    Ondřej Španěl
    My code inside of pendingUntilFixed throws NotImplementedError. This causes the test to be marked as failed. When I change it to UnsupportedOperationException, it works fine. Is this expected? If it is, what is the rationale? NotImplementedError is commonly used for unfinished code, for which pendingUntilFixed looks like a perfect solution.
    Matthew de Detrich
    Just created a PR at scalatest/scalatest#2155 which makes Prettifier.truncateAt work for collections within case classes