databob VS µTest

Compare databob vs µTest and see what are their differences.

databob

Randomised, zero-boilerplate object builders (by daviddenton)

µTest

A simple testing framework for Scala (by lihaoyi)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
databob µTest
0 2
9 481
- -0.2%
0.0 4.2
almost 7 years ago 8 days ago
Scala Scala
Apache License 2.0 -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

databob

Posts with mentions or reviews of databob. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning databob yet.
Tracking mentions began in Dec 2020.

µTest

Posts with mentions or reviews of µTest. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-11.
  • From First Principles: Why Scala?
    11 projects | news.ycombinator.com | 11 Feb 2021
    I am a Scala programmer & think it's a great language. Here are some arguments for why not Scala:

    * Li's libs (os-lib, upickle, utest) have clean public interfaces, but most Scala ecosystem libs are hard to use

    * The Mill build tool looks a lot better than SBT, but seems like everyone is still using SBT

    * Scala minor version are binary incompatible, so maintaining Scala projects is a big pain. Upgrading Spark from Scala 2.11 to Scala 2.12 was a massive undertaking for example.

    * Scala has tons of language features and lets people do crazy things in the code. Hard to win technical arguments with Scala geniuses that like using complicated language features.

    * Scalatest is stil used by most projects and is annoying to use, as described here: https://github.com/lihaoyi/utest#why-utest

    I'm optimistic about Scala. There are some folks that love the language and are continuously improving the ecosystem. Scala 3 will have to sell a better story about ditching legacy tooling and giving users a better default stack if it wants to compete with modern Go/Rust/Python.

    11 projects | news.ycombinator.com | 11 Feb 2021
    Let's clarify some points for folks not so familiar with Scala.

    > * Scala minor version are binary incompatible, so maintaining Scala projects is a big pain. Upgrading Spark from Scala 2.11 to Scala 2.12 was a massive undertaking for example.

    Scala just chose a strange naming scheme. Other languages would have just increased their major version instead. The scala minor version is increased every few years and not every month or so.

    > * Scala has tons of language features and lets people do crazy things in the code.

    Actually, that's not true. Or rather: compared to what language?

    Scala has surprisingly few language features, but the ones it has are very flexible and powerful. Take Kotlin for example. It has method extensions as a dedicated feature. Scala just has implicits which can be used for method extension.

    > * Scalatest is stil used by most projects and is annoying to use, as described here: https://github.com/lihaoyi/utest#why-utest. The overuse of DSLs in Scala is really annoying.

    I agree with the overuse of DSLs. Luckily that got much better, but older libraries like scalatest still suffer from that.

    > * Li's libs (os-lib, upickle, utest) have clean public interfaces, but most Scala ecosystem libs are hard to use, see the JSON alternatives for examples

    I think that just comes from using the library in a non-idiomatic way. In most applications, you will need to use the whole json anyways, and then you use (or can use) circe like that:

        {

What are some alternatives?

When comparing databob and µTest you can also consider the following projects:

ScalaMock - Native Scala mocking framework

Diffy

scalaprops - property based testing library for Scala

cornichon - Testing tool in Scala for HTTP JSON API

Scalive - Connect a Scala REPL to running JVM processes without any prior setup

Scala Test-State - Scala Test-State.

Gatling - Modern Load Testing as Code

ScalaCheck - Property-based testing for Scala

ScalaMeter - Microbenchmarking and performance regression testing framework for the JVM platform.