Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Paweł Wiejacha
    @pawel-wiejacha
    sbt: sbt/testing/src/main/scala/sbt/TestFramework.scala
    Paweł Wiejacha
    @pawel-wiejacha
    sbt/main/actions/src/main/scala/sbt/Tests.scala
    metoda testTask
    Paweł Wiejacha
    @pawel-wiejacha
    tam są stacktracey
    Paweł Wiejacha
    @pawel-wiejacha
    scalatest/scalatest#97
    ScalaTestRunner
    Framework ze scalatest
    Paweł Wiejacha
    @pawel-wiejacha
    ScalaTestNestedTask i ScalaTestTask implementuja Task
    Maciej Biłas
    @maciej
    Framework.scala:438
    Anna Stępień
    @solitaire
    Miejsca, gdzie w Suite używany jest stopper.stopRequest: linie 1234, 1319
    Maciej Biłas
    @maciej
    ScalaTestFramework – implementuje starą wersję API
    Framework – nowa wersja API
    Anna Stępień
    @solitaire
    Klasy, w których wykorzystywany jest stopper: Engine, StepwiseNestedSuiteExecution, Suite, SuiteRerunner, Runner, SuiteRunner
    doRunRunRunDaDoRunRun
    nazwa metody z Runnera :)
    Maciej Biłas
    @maciej
    sbt/sbt#1442
    Maciej Biłas
    @maciej
    https://twitter.com/specs2org/status/572667876345135107 Specs2 właśni wyszedł w wersji 3.0 a nie ScalaTest. Paweł, już wiadomo co Ciebie zmyliło.
    This message was deleted
    Paweł Wiejacha
    @pawel-wiejacha

    Hello,

    together with Anna Stępień and Maciej Biłas we started working on following issues:

    • scalatest/scalatest#97
    • sbt/sbt#228

    We decided to focus on handling CTRL-C during test execution in sbt console.

    As for now we:

    1. Created Stoppable interface in sbt.testing (test-interface)
    2. Changed ScalaTest ScalaTestRunner so that it implements Stoppable interface. Currently stopping ScalaTestRunner does not stop/kill running test cases but new test cases/suites
      are not executed.
    3. We changed sbt so that SIGINT is intercepted and tests are stopped.

    But then incidentally we found Signal (in util/collection/src/main/scala/sbt) and TaskCancellationStrategy.Signal that was introduced by:

    commit 2686acd99326d99bf2f17a488858d6df5e27d52a
    Author: Josh Suereth joshua.suereth@gmail.com
    Date: Mon Apr 7 16:42:08 2014 -0400

    Part #1 of cancel-task-hooks - Hooks EvaluateTask.

    a year ago. And we found that after setting set cancelable in Global := true CTRL-C interrupts threads related to the task that's being executed.

    Our idea was CTRL-C should stop executing new test cases and then (e.g. after second CTRL-C/some timeout) interrupt TestingFramework threads because interrupting threads is quite
    dirty in our opinion.

    But maybe interrupting threads is the right thing to do - it's dirty but it's also simple and works for all kind of tasks, not only for test task.

    What do you think is a better strategy? Is it provi