Popularity
8.4
Growing
Activity
9.5
Stable
858
59
277

Programming language: Scala
Tags: Extensions    
Latest version: v3.0.8

Scalactic alternatives and similar packages

Based on the "Extensions" category

Do you think we are missing an alternative of Scalactic or a related project?

Add another 'Extensions' Package
Monitor and correlate metrics, traces, and logs in one platform. Free 14-day trial.
More from our partner

Popular Comparisons

SaaSHub - Software Alternatives and Reviews
More from our team

README

ScalaTest

Build Status

ScalaTest is a free, open-source testing toolkit for Scala and Java programmers.

Official Website: http://www.scalatest.org/

Using ScalaTest

Setup

Please visit Download and Setup for download and setup instructions.

Quick Start

Please visit Quick Start for steps to get started quickly.

Building ScalaTest

Pre-Requisites

The followings are needed for building ScalaTest:

use the following SBT options instead:

SBT_OPTS="-server -Xms512M -Xmx3000M -Xss1M  -XX:+UseConcMarkSweepGC -XX:NewRatio=8"

Building and Running Tests

This command will build and run the regular tests:

$ sbt test

To run generated all tests, you'll need to increase maximum heap size to at least -Xmx5000M, and use this command instead:

$ rm -rf gentests
$ sbt gentests/test

You can also run different groups generated tests separately: 

$ rm -rf gentests
$ sbt genMustMatchersTests1/test
$ sbt genMustMatchersTests2/test
$ sbt genMustMatchersTests3/test
$ sbt genMustMatchersTests4/test
$ sbt genGenTests/test
$ sbt genTablesTests/test
$ sbt genInspectorsTests/test
$ sbt genInspectorsShorthandsTests1/test
$ sbt genInspectorsShorthandsTests2/test
$ sbt genTheyTests/test
$ sbt genContainTests1/test
$ sbt genContainTests2/test
$ sbt genSortedTests/test
$ sbt genLoneElementTests/test
$ sbt genEmptyTests/test

What it does is simply switch to gentests project and run test.

To run scala-js tests: 

$ sbt scalatestAppJS/clean
$ sbt scalacticTestJS/test:compile
$ sbt scalacticTestJS/test
$ sbt scalatestTestJS/test:compile
$ sbt scalatestTestJS/test

To run scala-native tests: 

$ sbt -Dscalatest.skip.jdk.check=true ++2.11.12 scalatestAppNative/clean
$ sbt -Dscalatest.skip.jdk.check=true ++2.11.12 scalacticTestNative/test:compile
$ sbt -Dscalatest.skip.jdk.check=true ++2.11.12 scalacticTestNative/test
$ sbt -Dscalatest.skip.jdk.check=true ++2.11.12 scalatestTestNative/test:compile
$ sbt -Dscalatest.skip.jdk.check=true ++2.11.12 scalatestTestNative/test

Building Examples

You can build examples project using this command:

$ sbt examples/compile

Packaging

You can package the ScalaTest JAR file using this command:

$ sbt package

The resulting JAR file will be produced in target/scala-2.11/.

You can also publish it to your local Ivy repository using this command:

$ sbt publishLocal

Or publish it to local maven repository using this command:

$ sbt publishM2

Publishing

To publish to Sonatype, you first need to make sure you have the following:

  • A GPG client is installed on your command line path. For more information, please refer to GNU Privacy Guard Website.
  • You have created your GPG keys and distributed your public key to hkp://pool.sks-keyservers.net/. For more information, please refer to How To Generate PGP Signatures With Maven.
  • You have been granted the right to publish using org.scalatest and org.scalactic domain.

By default, ScalaTest build will read your Sonatype credentials from ~/.ivy2/.credentials, which is a properties file that looks like this:

realm=Sonatype Nexus Repository Manager
host=oss.sonatype.org
user=xxxxxxxx
password=xxxxxxxx

You can use SCALATEST_NEXUS_LOGIN and SCALATEST_NEXUS_PASSWORD environment variables to override Sonatype credentials.

For signing, ScalaTest build will use ~/.gnupg/secring.gpg by default and prompt for GPG passphase if required. Alternatively you can use SCALATEST_GPG_FILE to use a different GPG file, and use SCALATEST_GPG_PASSPHASE to provide GPG passphase to avoid input prompt.

If you would like to export a particular private key into a separate GPG file, you can use the following command:

$ gpg --export-secret-keys example@example.com > example-secret-key.gpg

With Sonatype credentials and GPG file in place, you can now publish to Sonatype.

Before publishing any patch release, binary compatibility with previous version should be checked:

$ sbt ++2.11.12 scalactic/package scalactic/mimaReportBinaryIssues
$ sbt ++2.11.12 scalatest/package scalatest/mimaReportBinaryIssues
$ sbt ++2.11.12 scalacticJS/package scalacticJS/mimaReportBinaryIssues
$ sbt ++2.11.12 scalatestJS/package scalatestJS/mimaReportBinaryIssues

$ sbt ++2.10.7 scalactic/package scalactic/mimaReportBinaryIssues
$ sbt ++2.10.7 scalatest/package scalatest/mimaReportBinaryIssues
$ sbt ++2.10.7 scalacticJS/package scalacticJS/mimaReportBinaryIssues
$ sbt ++2.10.7 scalatestJS/package scalatestJS/mimaReportBinaryIssues

$ sbt ++2.12.9 scalactic/package scalactic/mimaReportBinaryIssues
$ sbt ++2.12.9 scalatest/package scalatest/mimaReportBinaryIssues
$ sbt ++2.12.9 scalacticJS/package scalacticJS/mimaReportBinaryIssues
$ sbt ++2.12.9 scalatestJS/package scalatestJS/mimaReportBinaryIssues

$ sbt ++2.13.0 scalactic/package scalactic/mimaReportBinaryIssues
$ sbt ++2.13.0 scalatest/package scalatest/mimaReportBinaryIssues
$ sbt ++2.13.0 scalacticJS/package scalacticJS/mimaReportBinaryIssues
$ sbt ++2.13.0 scalatestJS/package scalatestJS/mimaReportBinaryIssues

To publish scalactic, scalatest and scalatest-app use the following command:

$ sbt scalatestCompatible/clean scalatestCompatible/publishSigned
$ export SCALAJS_VERSION=0.6.28
$ sbt ++2.10.7 clean publishSigned "project scalatestAppJS" clean publishSigned
$ sbt ++2.11.12 clean publishSigned "project scalatestAppJS" clean publishSigned
$ sbt ++2.12.9 "project scalatestApp" clean publishSigned "project scalatestAppJS" clean publishSigned
$ sbt ++2.13.0 "project scalatestApp" clean publishSigned "project scalatestAppJS" clean publishSigned    
$ sbt ++2.11.12 "project scalatestAppNative" clean publishSigned
$ export SCALAJS_VERSION=1.0.0-M3
$ sbt ++2.11.12 "project scalatestAppJS" clean publishSigned
$ sbt ++2.12.6 "project scalatestAppJS" clean publishSigned
$ export SCALAJS_VERSION=1.0.0-M8
$ sbt ++2.13.0 "project scalatestAppJS" clean publishSigned
$ sbt scalacticDotty/clean scalacticDotty/publishSigned
$ sbt scalatestDotty/clean scalatestDotty/publishSigned

To publish scalatest modules for jvm, use the following commands: 

$ sbt scalatestModules/clean
$ sbt +scalatestModules/publishSigned

To publish scalatest modules for js, use the following commands: 

$ export SCALAJS_VERSION=0.6.28
$ sbt scalatestModulesJS/clean
$ sbt +scalatestModulesJS/publishSigned
$ export SCALAJS_VERSION=1.0.0-M3
$ sbt ++2.11.12 "project scalatestModulesJS" clean publishSigned
$ sbt ++2.12.6 "project scalatestModulesJS" clean publishSigned
$ export SCALAJS_VERSION=1.0.0-M8
$ sbt ++2.13.0 "project scalatestModulesJS" clean publishSigned

To publish scalatest modules for native, use the following commands: 

$ sbt ++2.11.12 scalatestModulesNative/clean
$ sbt ++2.11.12 scalatestModulesNative/publishSigned

To publish scalatest modules for Dotty, use the following commands: 

$ sbt scalatestModulesDotty/clean
$ sbt scalatestModulesDotty/publishSigned