Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Valentin Willscher
    @valenterry
    Thanks, I will see if I can do that
    Raphael Mäder
    @randm-ch

    Hi all! When running tests on a SJS facade I get this error (Full stack trace):

    [error] Referring to non-existent method java.lang.Thread$.sleep(long)void
    ...
    [error] org.scalajs.linker.LinkingException: There were linking errors
    ...

    Test code:

    'Toast - {
      def create = {
        M.toast(ToastOptions(html = "I am a toast!"))
        M.Toast.getInstance(document.querySelector(".toast"))
      }
      ...
      'dismiss - {
        val toast = create
        toast.dismiss()
        eventually(document.querySelectorAll(".toast").length == 0)
      }

    The problem is with eventually, but I don't see what I'm doing wrong here. Any suggestions? Using Scala 2.12.6, Scala.js 1.0.0-M3 and utest 0.6.4. Thanks!

    Raphael Mäder
    @randm-ch
    Ok, so I did figure out that eventually doesn't work in SJS (duh) ;) I'm now trying to get it to work with Futures.
    nicosmaris
    @nicosmaris

    Hi all, I posted the following by accident at the mill channel: is there any github repository using mill and utest along with the command to run the tests?

    mill -i foo.test doesn't find any test and my directory structure is:
    foo
    foo/test
    foo/test/foo
    foo/test/foo/ExampleTest.scala
    foo/src
    foo/src/foo
    foo/src/foo/Example.scala

    After writing a hello world, my goal is to run integration tests at apache flink with scala.
    https://ci.apache.org/projects/flink/flink-docs-release-1.5/dev/stream/testing.html#integration-testing

    the output is:
    [55/55] foo.test.test
    -------------------------------- Running Tests --------------------------------
    if anyone has an idea, send me a message. Thank you for your time.

    Thai Dang Vu
    @dxxvi
    Hi All, can I call tests written with uTest in maven? If yes, how to do that?
    Thai Dang Vu
    @dxxvi
    Wow, I'm scared of ghosts when entering an empty room like this :-)
    nafg
    @nafg
    Boo
    Mikhail Filipchuk
    @LiuVII

    Hey guys!
    I'm using PantsBuild instead of SBT in my project and do like nice tree-like output formatting in the examples.

    Is there a way using standalone API to get an output that looks like this:
    https://user-images.githubusercontent.com/934140/30258464-4b7ecaf4-96ec-11e7-9914-a8f6963e7891.png
    instead of the default "flat" one with . like this one:
    https://user-images.githubusercontent.com/934140/30258485-886d819e-96ec-11e7-8fc3-1a728a923156.png
    ?
    or maybe there's some other approach besides standalone API to resolve this (which doesn't involve switching project to SBT, of course)?

    Mikhail Filipchuk
    @LiuVII
    ^ @lihaoyi
    and ty for your work! I was starting to question my sanity when encountered the issue with shared scopes/ nested tests and didn't find a neat solution in ScalaTest or other popular frameworks
    ping-liu-lendi
    @ping-liu-lendi
    Hi I am using utest (with mill) for my testing. It appears that test result is in json format. I would like to have xunit compatible result so that bitbucket can collect and display. Can someone help how I can do that? Is there a way to configure utest to produce xml format instead of json? Thanks Ping
    jokade
    @jokade
    Can anyone tell me how I can do a local build of utest for scala-native? I need to build against the current dev snapshot (0.3.9).
    John Feiler
    @jjfeiler
    Is there an easy way to determine if there were test failures from within utestAfterAll()? Background: we're running some integration tests in kubernetes using utest, creating k8s namespaces to keep test runs isolated, and deleting those namespaces to keep our cluster from getting cluttered in utestAfterAll(). The problem is that when there are test failures, the cleanup deletes to logs that we might want to use to debug the failures. I'd like to change the cleanup code to only delete the namespaces if there were no test failures, but haven't found a way to determine f there are failures.
    I think it can be done using a custom test runner, but I'd like to avoid that unless its necessary :)
    David
    @davoclavo

    :point_up: March 21, 2018 10:28 AM

    I think that async test do not wait for completion before starting the next test; is that correct? Is there a way to change it? I'd like to use mutable shared fixtures in a test suite, but I need the shared data updated before running the next test.

    I'm facing the same thing. Is there a way to run async tests sequentially? Or am I going to have to wrap every test in an Await.result

    Paulo "JCranky" Siqueira
    @jcranky
    is there a way to execute some piece of clean up code after a test suite is executed ?
    Ryan Williams
    @ryan-williams
    a 0.6.7 that includes #186 (cf. comment) would be useful to me (even in 2.12), in case anyone's thinking about doing a release :smile:
    Li Haoyi
    @lihaoyi
    @/all just updated my Patreon page; if you use uTest and you like it, please chip in to support it so it can continue to be maintained and developed! https://www.patreon.com/lihaoyi
    spova
    @spova
    Hi all! Is there a way to mixin TestSuite? I would like to make tests with akka.testkit.TestKit for example.
    Stan Domeshok
    @sdomeshok
    Can't spot it in the docs, is there a way to mark a test as skipped?
    Damian Reeves
    @DamianReeves
    I’m sure this has been asked before, but I’m using iPad app and room search is non-existent ... is there a junior adapter for test?
    nafg
    @nafg
    A what?
    Damian Reeves
    @DamianReeves
    Junit
    Sorry... autocorrect
    Dirk T.
    @DirkToewe
    Hi everyone. Say, is it possible to run the same test for a Seq of elements, have the progress displayed in utest and on failure, the exact item/index reported for which the test failed?
    Matthew Pocock
    @drdozer
    does utest have a version that works in dotty?
    Matthew Pocock
    @drdozer
    :(
      java.lang.NoSuchMethodError: utest.Tests$.apply(Lscala/runtime/BoxedUnit;)Lutest/Tests;
        ExampleSpec$.<init>(Test1.scala:28)
        ExampleSpec$.<clinit>(Test1.scala:-1)
        jdk.internal.misc.Unsafe.ensureClassInitialized0(Unsafe.java:-2)
    Omer Zach
    @omerzach
    hey! i’m interested in getting utest to work like junit tests so i can use it easily with pants rather than SBT. happy to contribute back myself, but will need some pointers.
    Mikhail Filipchuk
    @LiuVII
    ^ +1 to questions from Omer Zach and Damian Reeves on junit integration
    Li Haoyi
    @lihaoyi
    @omerzach @LiuVII the docs for https://github.com/lihaoyi/utest#running-utest-standalone tell you how to run uTest programmatically, so you can just write your own thin wrapper to do that
    you can do that in any build tool, or without a build tool at all
    Eric K Richardson
    @ekrich
    Hi Guys, looks like you dropped support in the latest release for sjs0.6 for Scala 2.11. Wondering what was the reasoning or purpose behind this?
    Li Haoyi
    @lihaoyi
    it's old and I can't be bothered :P
    you can keep using the previous version if you're on 2.11
    nafg
    @nafg
    3 versions of scala is a lot to support at once :)
    Eric K Richardson
    @ekrich
    ok, I like either 3 or 2 versions but inclined to keep one old and one new if it is not any hassle. Certainly, 2.10 can create headaches.
    Marc Grue
    @marcgrue

    Asking on the scala-js channel also but this could maybe be related to utest, so I ask here too. Hope that's ok. Have upgraded the scalajs-cross-compile-example in this fork to Scala-js 0.6.28 and added Native and utests. Running main methods works fine on all platforms but when I run fooNative/test, the compilation can't find the Native classes even though I can see that they have been compiled in the target folder. Not sure if it's an issue with how I have set up build.sbt or utest. Any clues as to what I am missing?

    Steps to reproduce:

    git clone https://github.com/marcgrue/scalajs-cross-compile-example.git
    cd scalajs-cross-compile-example
    sbt
    fooNative/test
    Marc Grue
    @marcgrue
    Needed to move Native test suit into a package - they can't be on the root level!. Also a prerequisite for running Native tests is to have installed some libraries (brew install llvm bdw-gc re2 libuv). So, here you have a minimal Scala-js 0.6.28 crossProject running and utesting on all three platforms Scala JVM/JS/Native.
    @lihaoyi, maybe you want to write just two lines somewhere in your utest documentation about these prerequisites for running Native utests? That would be super helpful. Thanks a ton for all your fantastic libraries! :-)
    Rich
    @richtype
    What 's the plan with Symbols? Should I replace all my utest Symbol literals with Symbol constructors, or are Symbols going to be replaced with Strings?
    nafg
    @nafg
    I think they already were. The whole syntax was changed
    Changed test syntax to test("foo"){...}, test{...}. Old syntax is now deprecated.
    Rich
    @richtype
    Ah great, so that'll be in the 0.7.1 release? I'm using 0.6.9 but I notice GIthub labels 0.6.6 as the latest release.
    Nadav Samet
    @thesamet
    @lihaoyi Is there anyone working on dotty support? I am looking into helping with this and wanted to verify there are no duplicate efforts.
    Li Haoyi
    @lihaoyi
    i think one of the epfl folks might have looked into it, maybe ask on the dotty channel?
    Nadav Samet
    @thesamet
    @lihaoyi will do. ty!
    2efper
    @2efPer
    Does utest support scala2.13?
    Li Haoyi
    @lihaoyi
    yes
    2efper
    @2efPer
    Ok, Thanks.I found out I am using utest0.6.0 which does not exist in maven repo anymore.