Gerard Murphy

Integrate Hedgehog into Scalatest

13

### BACKGROUND I have used Scalacheck a lot in the past, and have gravitated over to the Scalatest flavour of it, using GeneratorDrivenPropertyChecks and native Scalatest assertions as opposed to...

It would be good to get a new release out - I'm currently having to workaround bugs that have been fixed since the last release, 0.4 at time of writing....

Loss of location of assert when using smart asserts.

2

Using: ```libraryDependencies += "com.lihaoyi" %% "utest" % "0.8.1" % Test```, running under IntelliJ. Code (Scala 3.3.0): ```scala package com.sageserpent.kineticmerge.core import utest.* object OddStackTraceReport extends TestSuite: def excised(item: Int): Unit =...

Error seen on parsing a case class nested in an object definition with Scala 3.

1

### Commit of tree-sitter-scala you tested this on dd02e510e92e057bdcadc4def1a3b28bed5fbea3 ### A code sample showing the error ```scala package com.sageserpent.kineticmerge.core object Merge: case class Location(runIndex: Int, locationInRun: String): end Location end...

Issue 239 Fix

2

Addresses this issue: [Possible bug in implementation of MapDecorator.mergeByKeyWith](https://github.com/scala/scala-collection-contrib/issues/239). Test added to reproduce the bug in: ~~bcc2b6efedcb97ae329b792940b52e44ef1db06e~~4fe84ca7370f05059817fd333f72719d33fb4652. Fix to make test pass in: ~~5088ed6ac8a23e3a9987491bf05f334d05cdfc74~~8c8d67bd323f7a9bf2b786b5b55c3349fa52f7f8.

### Seen in 0.3.0 ### Reproduction Scala worksheet, so assertions are verified by eye. Using `mergeByKey` for convenience, knowing it delegates to `mergeByKeyWith`. ```scala import scala.collection.decorators.mapDecorator val arthur = "arthur.txt"...

Trials.reject should be compatible with any type.

1

`Trials.reject` currently is typed to yield `Unit` in Scala and `void` in Java. This means that it can't be used in a value expression, so it tends to end up...

Hive off JUnit support into its own extension library.

1

The core functionality of Americium has nothing to do with JUnit, but the integrations with JUnit5 are very convenient both for traditional Java + JUnit5 development and also for Scala...

This follows in from #72. The situation here is that as test case synthesis code evolves, recipes can become invalid and cause either an exception deep in the Americium implementation...

The Java and Scala forms of `TrialsSkeletalImplementation` have odd return types for the methods that yield trials instances - sometimes it's a `TrialsSkeletalImplementation`, sometimes its a full-fat `TrialsImplementation`. In contrast,...