specs2

I'm quite new to Play2 and Scala. I'm writing a simple application that uses ReactiveMongo plugin. I wrote a simple object to use as DAO object UserDAO { def db: reactivemongo.api.DB = ReactiveMongoPlugin.db def collection: JSONCollection = db.collection[JSONCollection]("users") collection.indexesManager.ensure(Index(List("name" -> IndexType.Ascending), unique = true)) def insert(User): Future[LastError] = { collection.insert(unit) } def findOne(query: JsObject): Future[Option[User]] = { collection.find(query).one[User] } def removeOne(query: JsObject): Future[LastError] = { collection.remove

I'm trying to solve two ScalaCheck (+ specs2) problems: Is there any way to change the number of cases that ScalaCheck generates? How can I generate strings that contain some Unicode characters? For example, I'd like to generate about 10 random strings that include both alphanumeric and Unicode characters. This code, however, always generates 100 random strings, and they are strictly alpha character based: "make a random string" in { def stringGenerator = Gen.alphaStr.suchThat(_.length < 40) implicit def randomString: Arbitrary[String] = Arbitrary(stringGenerator) "the string" ! prop { (s:

Using typed value classes as IDs is a common pattern in Scala. However, it seems Mockito has an issue when stubbing methods that take value classes as arguments. In the example below, the first stub, with an actual value works just fine, but the second one, that uses an argument matcher throws NullPointerException. The only reference to this I've found is this question but the solution shown there does not work. Anyone knows a solution to this, or a work-around? Versions are: org.mockito:mockito-all:1.10.19 and org.specs2:specs2_2.11:2.4.15 import org.specs2.mutable.Specification import org

I have the following spec: import org.specs2.mock.Mockito import org.specs2.mutable.Specification class LinkUserServiceSpec extends Specification with Mockito { val linkUserService = mock[LinkUserService] "The 'LinkUserService' isUserLinked method" should { "return false when a previously unlinked userId is passed in for a given service" in { linkUserService.isUserLinked("nobody", "YT") returns false linkUserService.isUserLinked("nobody", "YT") must beFalse } } } And the following dependency in my build.sbt: "org.specs2" %% "specs2" % "2.2" % "test" However I get this error when I type test

How can I check if a Seq[String] is empty or not using specs2 in Scala ? I am using seq must be empty or seq.length must be greaterThan(0) but I end up always with type mismatch errors. ret is Seq[String] ret.length must be greaterThan(0) [error] ApiTest.scala:99: type mismatch; [error] found : Int [error] required: org.specs2.matcher.Matcher[String] [error] ret.length must be greaterThan(0) I think the type mismatch error is caused by another bit of code than that which you've posted. Your example should just work with: ret must not be empty I've tried and confirmed to be working correctly:

I'm used to JUnit, in JUnit it is possible to group several tests (usually related to a class) just by defining these tests in a single file (class) and annotating them with @Test . Then, to run several of these tests, a TestSuite is created with @Suite.SuiteClasses and so on. In specs2 it is possible to group several tests at two different levels extending some Specification . For example: "Whatever" should { "do its job when possible" in { whatever(new Thing).work must beSome } "return none when not possible" in { whatever(null).work must beNone } } We can group several Specification of this

For example, for code like this: myNum must beEqualTo("SOME INTERESTING TEXT") The message will be like the following: java.lang.Exception: ArrayBuffer() doesn't have size 1 but size 0 Is there an elegant way to get customised message displayed here? First you can name value you're testing. myNum aka "meaningful name" must_== expectedValue You can also overwrite the full message. (myNum must_== expectedValue).setMessage("Full failure message") 来源： https://stackoverflow.com/questions/25351312/how-to-show-custom-failure-message-in-specs2-scala

I'm using specs2/scala for unit tests and using gradle to build. By default the unit-test output goes to a html file. I would like to have the output go directly to stdout (just like sbt). Anyone know the magic incantation? thanks wing You can use test { //makes the standard streams (err and out) visible at console when running tests testLogging.showStandardStreams = true } But this logs stdout at the info level so you need to run gradle -i to see it (it seems this will be fixed in 1.1: http://issues.gradle.org/browse/GRADLE-1966 ) Alternatively, you can add an event handler: test { onOutput {