Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 08 2019 05:34

    xuwei-k on master

    Update sbt-header to 5.3.0 (compare)

  • Oct 17 2019 02:52

    xuwei-k on master

    Update specs2-core to 4.8.0 (compare)

  • Oct 16 2019 05:14

    xuwei-k on master

    Update sbt-release to 1.0.12 (compare)

  • Oct 14 2019 12:17

    xuwei-k on master

    sbt 1.3.3 (compare)

  • Oct 14 2019 04:50

    xuwei-k on master

    Update scalaz to 7.2.29 (compare)

  • Oct 02 2019 23:10

    xuwei-k on master

    Update sbt-microsites to 0.9.7 (compare)

  • Oct 02 2019 00:40

    xuwei-k on master

    Update tut-plugin to 0.6.13 (compare)

  • Oct 02 2019 00:40
    xuwei-k closed #36
  • Oct 02 2019 00:30
    codecov-io commented #36
  • Oct 02 2019 00:23
    xuwei-k opened #36
  • Sep 28 2019 23:14

    xuwei-k on master

    sbt-sonatype 3.8 (compare)

  • Sep 26 2019 02:17

    xuwei-k on master

    Update sbt-microsites to 0.9.6 (compare)

  • Sep 21 2019 23:26

    xuwei-k on master

    sbt 1.3.2 (compare)

  • Sep 20 2019 11:56

    xuwei-k on master

    sbt 1.3.1 (compare)

  • Sep 19 2019 06:57

    xuwei-k on master

    Update sbt-wartremover to 2.4.3… (compare)

  • Sep 19 2019 06:57
    xuwei-k closed #35
  • Sep 19 2019 06:51
    codecov-io commented #35
  • Sep 19 2019 06:51
    codecov-io commented #35
  • Sep 19 2019 06:46
    xuwei-k opened #35
  • Sep 18 2019 04:40

    xuwei-k on master

    Update scala-js to 0.6.29 (compare)

Harrison Houghton
@hrhino
I don't think there are too many right now
Edmund Noble
@edmundnoble
The pitch is mostly the design doc
@m13m
@vil1 Awesome!
Valentin Kasas
@vil1
@edmundnoble the said PR: scalaz/scalaz-schema#15
Rob Norris
@tpolecat
@edmundnoble your readme mentions the scalaz code of conduct … is this it?
Edmund Noble
@edmundnoble
Probably
Whichever the main scalaz/scalaz repo operates under, testz does
Rob Norris
@tpolecat
There is no mention in scalaz/scalaz as far as I can tell.
Edmund Noble
@edmundnoble
Hmmm perhaps I should delete the mention then, thanks for letting me know
Rob Norris
@tpolecat
Sure, just curious.
Edmund Noble
@edmundnoble
Big update: scalaz/testz#21
Among changes: now there's no need for a distinct harness interface for specs2, making it easier to write tests that work for specs2, scalatest and testz without depending on anything more than testz-core
Also a lot of documentation in the docs/ folder, still need to build it and get it up on gh-pages though
Valentin Kasas
@vil1
:+1:
Edmund Noble
@edmundnoble
@here testz now has documentation on github pages (and a new release: 0.0.5); you can read it at http://scalaz.github.io/testz. I've tried to document every line of (non-test) code in testz; please let me know if there are any oversights.
Valentin Kasas
@vil1
looking good so far
fun fact : testz.assert tends to disturb some people who confuse it with scala.Predef.assert and therefore find it not very FP-ish
Edmund Noble
@edmundnoble
They should look at the implementation. One nice thing is, if you don't import testz.assert and accidentally use Predef.assert, your code won't compile.
Zelenya
@Zelenya
@edmundnoble is this legal? or should I be ashamed and banned?
def sneakyHarness[T](self: Harness[T]): Harness[T] =
    new Harness[T] {
      def test(name: String)(assertions: () => Result): T =
        self.test(name) { () =>
          try {
            assertions()
          } catch {
            case _: NotImplementedError =>
              Fail()
            case ex: Exception =>
              ex.printStackTrace()
              Fail()
          }
        }
    ...
    }
Edmund Noble
@edmundnoble
Hey
Well, you should probably be ashamed and banned
But that's irrelevant here ;)
If you have a lot of code which can fail with exceptions, you can go ahead and do that. In general though, I think for most code throwing an exception is an irrecoverable failure for the rest of the tests.
There are exceptions to this. FutureHarness and TaskHarness catch exceptions, but not in this way; only inside the Task or Future context.
This means that if you take a FutureHarness and convert it to a Harness, there is no observable difference between that and PureHarness as a Harness.
I was just about to add tests for this for TaskHarness, actually, which are instructive: scalaz/testz#27
Edmund Noble
@edmundnoble
/cc @Zelenya
Zelenya
@Zelenya
@edmundnoble okay, thank you
Edmund Noble
@edmundnoble
Welcome!
Edmund Noble
@edmundnoble
New testz PR, changing around the primitives somewhat to make them easier to manipulate. Comes with TestOnly, for doing... exactly what it sounds like ;)
scalaz/testz#28
Harrison Houghton
@hrhino
BUT DOES IT HAVE SBT INTEGRATION ED
Edmund Noble
@edmundnoble
LOL
It might one day. Don't lose hope.
Harrison Houghton
@hrhino
today I found that each of my scalatest tests which were not chosen to run still took (and logged) 300-400ms (each)
bless you, testz
Edmund Noble
@edmundnoble
<3
Dale Wijnand
@dwijnand
Hey. Did you expand on your initial thoughts on property-based testing, Edmund? I'm interested to understand your take better.
Dimitar Georgiev
@dimitarg
Looking at the source code of testz, I see no way to return a message / description along with a Fail. I suppose the motivation is that tests of the correct granularity wouldn't need that and the description would come from the test or namedSection themselves?
Harrison Houghton
@hrhino
Pretty much right now.
I'm not convinced that failure messages are something we shouldn't support.
You can also provide an EffectHarness which returns results in Writer or something.
Dimitar Georgiev
@dimitarg
Oh yes, hadn't thought of that, thanks
Dale Wijnand
@dwijnand
scalaz/testz#29 is a doc link fix
Valentin Kasas
@vil1
hey folks, is there some non-obvious magic required in order to get code coverage reports? I see that you are just adding the sbt-scoverage plugin, but maybe I'm missing something
Valentin Kasas
@vil1
[narrator voice] no special magic was needed, sometimes things Just Work™
Edmund Noble
@edmundnoble
Heh yeah, that should work just fine :) it's how testz's coverage is tested itself
Salar Rahmanian
@softinio
Hi All
@edmundnoble are you planning on keeping this project under the scalaz org?
Martijn Hoekstra
@martijnhoekstra
is scaladoc published for testz?