@* * Copyright 2010-2017 Artima, Inc. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. *@ @import controllers.Application.milestoneScaladoc @nonHomePage("Older Releases of ScalaTest") {
Note: This page shows how to install older releases of ScalaTest. For the latest release, visit the Installing ScalaTest page.
ScalaTest and Scalactic 3.0.4 (the latest release for Scala 2.10.0+, 2.11.0+, and 2.12.0+)
The ScalaTest 3.0.4 artifacts and Scalactic 3.0.0 artifacts are available via the Sonatype OSS Maven repository and mirrored on Maven central.
To include ScalaTest 3.0.4 in your sbt project:
1. Add these lines to your build file:
libraryDependencies += "org.scalactic" %% "scalactic" % "3.0.0" libraryDependencies += "org.scalatest" %% "scalatest" % "3.0.4" % "test"
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by first adding this line to ~/.sbt/0.13/global.sbt
:
resolvers += "Artima Maven Repository" at "http://repo.artima.com/releases"
3. Then adding the following line to project/plugins.sbt
:
addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.0")
You are off and running! As a next step, visit the Getting Started section of the user guide.
To include ScalaTest 3.0.4 in your Maven project:
1. Add the following dependencies to your pom.xml
:
<dependency> <groupId>org.scalactic</groupId> <artifactId>scalactic_2.11</artifactId> <version>3.0.0</version> </dependency> <dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>3.0.4</version> <scope>test</scope> </dependency>
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by adding the following lines to your pom.xml
:
<repositories> <repository> <id>artima</id> <name>Artima Maven Repository</name> <url>http://repo.artima.com/releases</url> </repository> </repositories> <plugin> <groupId>net.alchim31.maven</groupId> <artifactId>scala-maven-plugin</artifactId> <configuration> <compilerPlugins> <compilerPlugin> <groupId>com.artima.supersafe</groupId> <artifactId>supersafe_2.12.3</artifactId> <version>1.1.2</version> </compilerPlugin> </compilerPlugins> </configuration> <executions> ... </executions> </plugin>
Note: You need to use the exact Scala version in the artifactId, because compiler plugin depends on compiler API that's not binary compatible between Scala minor releases.
You are off and running! As a next step, visit the Getting Started section of the user guide.
If you don't have it already, you'll also need Scala. You can use any 2.10, 2.11, or 2.12 release, which you can get from here:
ScalaTest and Scalactic 3.0.3 (the latest release for Scala 2.10.0+, 2.11.0+, and 2.12.0+)
The ScalaTest 3.0.3 artifacts and Scalactic 3.0.0 artifacts are available via the Sonatype OSS Maven repository and mirrored on Maven central.
To include ScalaTest 3.0.3 in your sbt project:
1. Add these lines to your build file:
libraryDependencies += "org.scalactic" %% "scalactic" % "3.0.0" libraryDependencies += "org.scalatest" %% "scalatest" % "3.0.3" % "test"
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by first adding this line to ~/.sbt/0.13/global.sbt
:
resolvers += "Artima Maven Repository" at "http://repo.artima.com/releases"
3. Then adding the following line to project/plugins.sbt
:
addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.0")
You are off and running! As a next step, visit the Getting Started section of the user guide.
To include ScalaTest 3.0.3 in your Maven project:
1. Add the following dependencies to your pom.xml
:
<dependency> <groupId>org.scalactic</groupId> <artifactId>scalactic_2.11</artifactId> <version>3.0.0</version> </dependency> <dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>3.0.3</version> <scope>test</scope> </dependency>
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by adding the following lines to your pom.xml
:
<repositories> <repository> <id>artima</id> <name>Artima Maven Repository</name> <url>http://repo.artima.com/releases</url> </repository> </repositories> <plugin> <groupId>net.alchim31.maven</groupId> <artifactId>scala-maven-plugin</artifactId> <configuration> <compilerPlugins> <compilerPlugin> <groupId>com.artima.supersafe</groupId> <artifactId>supersafe_2.12.3</artifactId> <version>1.1.2</version> </compilerPlugin> </compilerPlugins> </configuration> <executions> ... </executions> </plugin>
Note: You need to use the exact Scala version in the artifactId, because compiler plugin depends on compiler API that's not binary compatible between Scala minor releases.
You are off and running! As a next step, visit the Getting Started section of the user guide.
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and Scalactic 3.0.2 (the latest release for Scala 2.10.0+, 2.11.0+, and 2.12.0+)
The ScalaTest 3.0.2 artifacts and Scalactic 3.0.0 artifacts are available via the Sonatype OSS Maven repository and mirrored on Maven central.
To include ScalaTest 3.0.2 in your sbt project:
1. Add these lines to your build file:
libraryDependencies += "org.scalactic" %% "scalactic" % "3.0.0" libraryDependencies += "org.scalatest" %% "scalatest" % "3.0.2" % "test"
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by first adding this line to ~/.sbt/0.13/global.sbt
:
resolvers += "Artima Maven Repository" at "http://repo.artima.com/releases"
3. Then adding the following line to project/plugins.sbt
:
addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.0")
You are off and running! As a next step, visit the Getting Started section of the user guide.
To include ScalaTest 3.0.2 in your Maven project:
1. Add the following dependencies to your pom.xml
:
<dependency> <groupId>org.scalactic</groupId> <artifactId>scalactic_2.11</artifactId> <version>3.0.0</version> </dependency> <dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>3.0.2</version> <scope>test</scope> </dependency>
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by adding the following lines to your pom.xml
:
<repositories> <repository> <id>artima</id> <name>Artima Maven Repository</name> <url>http://repo.artima.com/releases</url> </repository> </repositories> <plugin> <groupId>net.alchim31.maven</groupId> <artifactId>scala-maven-plugin</artifactId> <configuration> <compilerPlugins> <compilerPlugin> <groupId>com.artima.supersafe</groupId> <artifactId>supersafe_2.12.3</artifactId> <version>1.1.2</version> </compilerPlugin> </compilerPlugins> </configuration> <executions> ... </executions> </plugin>
Note: You need to use the exact Scala version in the artifactId, because compiler plugin depends on compiler API that's not binary compatible between Scala minor releases.
You are off and running! As a next step, visit the Getting Started section of the user guide.
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and Scalactic 3.0.1 (the latest release for Scala 2.10.0+, 2.11.0+, and 2.12.0+)
The ScalaTest 3.0.1 artifacts and Scalactic 3.0.0 artifacts are available via the Sonatype OSS Maven repository and mirrored on Maven central.
To include ScalaTest 3.0.1 in your sbt project:
1. Add these lines to your build file:
libraryDependencies += "org.scalactic" %% "scalactic" % "3.0.0" libraryDependencies += "org.scalatest" %% "scalatest" % "3.0.1" % "test"
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by first adding this line to ~/.sbt/0.13/global.sbt
:
resolvers += "Artima Maven Repository" at "http://repo.artima.com/releases"
3. Then adding the following line to project/plugins.sbt
:
addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.0")
You are off and running! As a next step, visit the Getting Started section of the user guide.
To include ScalaTest 3.0.1 in your Maven project:
1. Add the following dependencies to your pom.xml
:
<dependency> <groupId>org.scalactic</groupId> <artifactId>scalactic_2.11</artifactId> <version>3.0.0</version> </dependency> <dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>3.0.1</version> <scope>test</scope> </dependency>
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by adding the following lines to your pom.xml
:
<repositories> <repository> <id>artima</id> <name>Artima Maven Repository</name> <url>http://repo.artima.com/releases</url> </repository> </repositories> <plugin> <groupId>net.alchim31.maven</groupId> <artifactId>scala-maven-plugin</artifactId> <configuration> <compilerPlugins> <compilerPlugin> <groupId>com.artima.supersafe</groupId> <artifactId>supersafe_2.12.3</artifactId> <version>1.1.2</version> </compilerPlugin> </compilerPlugins> </configuration> <executions> ... </executions> </plugin>
Note: You need to use the exact Scala version in the artifactId, because compiler plugin depends on compiler API that's not binary compatible between Scala minor releases.
You are off and running! As a next step, visit the Getting Started section of the user guide.
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and Scalactic 3.0.0 (the latest release for Scala 2.10.0+, 2.11.0+, and 2.12.0+)
The ScalaTest 3.0.0 artifacts and Scalactic 3.0.0 artifacts are available via the Sonatype OSS Maven repository and mirrored on Maven central.
To include ScalaTest 3.0.0 in your sbt project:
1. Add these lines to your build file:
libraryDependencies += "org.scalactic" %% "scalactic" % "3.0.0" libraryDependencies += "org.scalatest" %% "scalatest" % "3.0.0" % "test"
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by first adding this line to ~/.sbt/0.13/global.sbt
:
resolvers += "Artima Maven Repository" at "http://repo.artima.com/releases"
3. Then adding the following line to project/plugins.sbt
:
addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.0")
You are off and running! As a next step, visit the Getting Started section of the user guide.
To include ScalaTest 3.0.0 in your Maven project:
1. Add the following dependencies to your pom.xml
:
<dependency> <groupId>org.scalactic</groupId> <artifactId>scalactic_2.11</artifactId> <version>3.0.0</version> </dependency> <dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>3.0.0</version> <scope>test</scope> </dependency>
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by adding the following lines to your pom.xml
:
<repositories> <repository> <id>artima</id> <name>Artima Maven Repository</name> <url>http://repo.artima.com/releases</url> </repository> </repositories> <plugin> <groupId>net.alchim31.maven</groupId> <artifactId>scala-maven-plugin</artifactId> <configuration> <compilerPlugins> <compilerPlugin> <groupId>com.artima.supersafe</groupId> <artifactId>supersafe_2.12.3</artifactId> <version>1.1.2</version> </compilerPlugin> </compilerPlugins> </configuration> <executions> ... </executions> </plugin>
Note: You need to use the exact Scala version in the artifactId, because compiler plugin depends on compiler API that's not binary compatible between Scala minor releases.
You are off and running! As a next step, visit the Getting Started section of the user guide.
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and Scalactic 2.2.6 (the latest release for Scala 2.10.0+ and 2.11.0+)
The ScalaTest 2.2.6 artifacts and Scalactic 2.2.6 artifacts are available via the Sonatype OSS Maven repository and mirrored on Maven central.
To include ScalaTest 2.2.6 in your sbt project:
1. Add these lines to your build file:
libraryDependencies += "org.scalactic" %% "scalactic" % "2.2.6" libraryDependencies += "org.scalatest" %% "scalatest" % "2.2.6" % "test"
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by first adding this line to ~/.sbt/0.13/global.sbt
:
resolvers += "Artima Maven Repository" at "http://repo.artima.com/releases"
3. Then adding the following line to project/plugins.sbt
:
addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.0-RC6")
You are off and running! As a next step, visit the Getting Started section of the user guide.
To include ScalaTest 2.2.6 in your Maven project:
1. Add the following dependencies to your pom.xml
:
<dependency> <groupId>org.scalactic</groupId> <artifactId>scalactic_2.11</artifactId> <version>2.2.6</version> </dependency> <dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.2.6</version> <scope>test</scope> </dependency>
The dependency on Scalactic, ScalaTest's sister library focused on quality through types, is recommended but not required.
2. We also recommend you also include the SuperSafe Community Edition Scala compiler plugin, which will flag errors in your ScalaTest (and
Scalactic) code at compile time, by adding the following lines to your pom.xml
:
<repositories> <repository> <id>artima</id> <name>Artima Maven Repository</name> <url>http://repo.artima.com/releases</url> </repository> </repositories> <plugin> <groupId>net.alchim31.maven</groupId> <artifactId>scala-maven-plugin</artifactId> <configuration> <compilerPlugins> <compilerPlugin> <groupId>com.artima.supersafe</groupId> <artifactId>supersafe_2.11.7</artifactId> <version>1.1.0-RC6</version> </compilerPlugin> </compilerPlugins> </configuration> <executions> ... </executions> </plugin>
Note: You need to use the exact Scala version in the artifactId, because compiler plugin depends on compiler API that's not binary compatible between Scala minor releases.
You are off and running! As a next step, visit the Getting Started section of the user guide.
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and Scalactic 2.2.5 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.2.5 Scaladoc.
 A copy of Scalactic is
included in ScalaTest's jar file. If you wish to use Scalactic
in your production code as well, see the install page on the
scalactic.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.2.5</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.2.5" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and Scalactic 2.2.4 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.2.4 Scaladoc.
 A copy of Scalactic is
included in ScalaTest's jar file. If you wish to use Scalactic
in your production code as well, see the install page on the
scalactic.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.2.4</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.2.4" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and Scalactic 2.2.2 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.2.2 Scaladoc.
 A copy of Scalactic is
included in ScalaTest's jar file. If you wish to use Scalactic
in your production code as well, see the install page on the
scalactic.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.2.2</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.2.2" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and Scalactic 2.2.1 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.2.1 Scaladoc.
 A copy of Scalactic is
included in ScalaTest's jar file. If you wish to use Scalactic
in your production code as well, see the install page on the
scalactic.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.2.1</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.2.1" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and Scalactic 2.2.0 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.2.0 Scaladoc.
 A copy of Scalactic is
included in ScalaTest's jar file. If you wish to use Scalactic
in your production code as well, see the install page on the
scalactic.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.2.0</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.2.0" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
ScalaTest and ScalaUtils 2.1.7 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.1.7 Scaladoc.
 A copy of ScalaUtils is
included in ScalaTest's jar file. If you wish to use ScalaUtils
in your production code as well, see the information on ScalaUtils below or the
scalautils.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.1.7</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.1.7" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
Using ScalaUtils in your production code
The ScalaUtils library grew out of the ScalaTest 2.1.7 effort. ScalaTest 2.1.7 is tightly integrated with ScalaUtils. Although you
should not include ScalaTest in your production class path (because when ScalaTest doesn't like something, it tends to
throw TestFailedException
), you can make use of ScalaUtils in you production code. Here's how:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalautils</groupId> <artifactId>scalautils_2.11</artifactId> <version>2.1.7</version> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalautils" % "scalautils_2.11" % "2.1.7"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaUtils 2.1.7 Scaladoc.
ScalaTest and ScalaUtils 2.1.6 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.1.6 Scaladoc.
 A copy of ScalaUtils is
included in ScalaTest's jar file. If you wish to use ScalaUtils
in your production code as well, see the information on ScalaUtils below or the
scalautils.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.1.6</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.1.6" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
Using ScalaUtils in your production code
The ScalaUtils library grew out of the ScalaTest 2.1.6 effort. ScalaTest 2.1.6 is tightly integrated with ScalaUtils. Although you
should not include ScalaTest in your production class path (because when ScalaTest doesn't like something, it tends to
throw TestFailedException
), you can make use of ScalaUtils in you production code. Here's how:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalautils</groupId> <artifactId>scalautils_2.11</artifactId> <version>2.1.6</version> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalautils" % "scalautils_2.11" % "2.1.6"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaUtils 2.1.6 Scaladoc.
ScalaTest and ScalaUtils 2.1.5 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.1.5 Scaladoc.
 A copy of ScalaUtils is
included in ScalaTest's jar file. If you wish to use ScalaUtils
in your production code as well, see the information on ScalaUtils below or the
scalautils.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.1.5</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.1.5" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
Using ScalaUtils in your production code
The ScalaUtils library grew out of the ScalaTest 2.1.5 effort. ScalaTest 2.1.5 is tightly integrated with ScalaUtils. Although you
should not include ScalaTest in your production class path (because when ScalaTest doesn't like something, it tends to
throw TestFailedException
), you can make use of ScalaUtils in you production code. Here's how:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalautils</groupId> <artifactId>scalautils_2.11</artifactId> <version>2.1.5</version> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalautils" % "scalautils_2.11" % "2.1.5"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaUtils 2.1.5 Scaladoc.
ScalaTest and ScalaUtils 2.1.4 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.1.4 Scaladoc.
 A copy of ScalaUtils is
included in ScalaTest's jar file. If you wish to use ScalaUtils
in your production code as well, see the information on ScalaUtils below or the
scalautils.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.11</artifactId> <version>2.1.4</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.1.4" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
Using ScalaUtils in your production code
The ScalaUtils library grew out of the ScalaTest 2.1.4 effort. ScalaTest 2.1.4 is tightly integrated with ScalaUtils. Although you
should not include ScalaTest in your production class path (because when ScalaTest doesn't like something, it tends to
throw TestFailedException
), you can make use of ScalaUtils in you production code. Here's how:
Here's the code for your Maven POM (for Scala 2.11.0+):
<dependency> <groupId>org.scalautils</groupId> <artifactId>scalautils_2.11</artifactId> <version>2.1.4</version> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.11.0+):
libraryDependencies += "org.scalautils" % "scalautils_2.11" % "2.1.4"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.11 can be used with any 2.11.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.11.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 or 2.11 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaUtils 2.1.4 Scaladoc.
ScalaTest and ScalaUtils 2.1.3 (for Scala 2.10.0+ and 2.11.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.1.3 Scaladoc.
 A copy of ScalaUtils is
included in ScalaTest's jar file. If you wish to use ScalaUtils
in your production code as well, see the information on ScalaUtils below or the
scalautils.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM (for Scala 2.10.0+):
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.10</artifactId> <version>2.1.3</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.10" % "2.1.3" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
Using ScalaUtils in your production code
The ScalaUtils library grew out of the ScalaTest 2.1.3 effort. ScalaTest 2.1.3 is tightly integrated with ScalaUtils. Although you
should not include ScalaTest in your production class path (because when ScalaTest doesn't like something, it tends to
throw TestFailedException
), you can make use of ScalaUtils in you production code. Here's how:
Here's the code for your Maven POM (for Scala 2.10.0+):
<dependency> <groupId>org.scalautils</groupId> <artifactId>scalautils_2.10</artifactId> <version>2.1.3</version> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalautils" % "scalautils_2.10" % "2.1.3"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaUtils 2.1.3 Scaladoc.
ScalaTest and ScalaUtils 2.1.2 (for Scala 2.10.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.1.2 Scaladoc.
 A copy of ScalaUtils is
included in ScalaTest's jar file. If you wish to use ScalaUtils
in your production code as well, see the information on ScalaUtils below or the
scalautils.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM:
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.10</artifactId> <version>2.1.2</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.10" % "2.1.2" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
Using ScalaUtils in your production code
The ScalaUtils library grew out of the ScalaTest 2.1.2 effort. ScalaTest 2.1.2 is tightly integrated with ScalaUtils. Although you
should not include ScalaTest in your production class path (because when ScalaTest doesn't like something, it tends to
throw TestFailedException
), you can make use of ScalaUtils in you production code. Here's how:
Here's the code for your Maven POM:
<dependency> <groupId>org.scalautils</groupId> <artifactId>scalautils_2.10</artifactId> <version>2.1.2</version> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalautils" % "scalautils_2.10" % "2.1.2"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaUtils 2.1.2 Scaladoc.
ScalaTest and ScalaUtils 2.1.1 (for Scala 2.10.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.1.1 Scaladoc.
 A copy of ScalaUtils is
included in ScalaTest's jar file. If you wish to use ScalaUtils
in your production code as well, see the information on ScalaUtils below or the
scalautils.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM:
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.10</artifactId> <version>2.1.1</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.10" % "2.1.1" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
Using ScalaUtils in your production code
The ScalaUtils library grew out of the ScalaTest 2.1.1 effort. ScalaTest 2.1.1 is tightly integrated with ScalaUtils. Although you
should not include ScalaTest in your production class path (because when ScalaTest doesn't like something, it tends to
throw TestFailedException
), you can make use of ScalaUtils in you production code. Here's how:
Here's the code for your Maven POM:
<dependency> <groupId>org.scalautils</groupId> <artifactId>scalautils_2.10</artifactId> <version>2.1.1</version> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalautils" % "scalautils_2.10" % "2.1.1"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaUtils 2.1.1 Scaladoc.
ScalaTest and ScalaUtils 2.1.0 (for Scala 2.10.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.1.0 Scaladoc.
 A copy of ScalaUtils is
included in ScalaTest's jar file. If you wish to use ScalaUtils
in your production code as well, see the information on ScalaUtils below or the
scalautils.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM:
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.10</artifactId> <version>2.1.0</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.10" % "2.1.0" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
Using ScalaUtils in your production code
The ScalaUtils library grew out of the ScalaTest 2.1.0 effort. ScalaTest 2.1.0 is tightly integrated with ScalaUtils. Although you
should not include ScalaTest in your production class path (because when ScalaTest doesn't like something, it tends to
throw TestFailedException
), you can make use of ScalaUtils in you production code. Here's how:
Here's the code for your Maven POM:
<dependency> <groupId>org.scalautils</groupId> <artifactId>scalautils_2.10</artifactId> <version>2.1.0</version> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalautils" % "scalautils_2.10" % "2.1.0"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaUtils 2.1.0 Scaladoc.
ScalaTest and ScalaUtils 2.0 (for Scala 2.10.0+) are available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well).
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 2.0 Scaladoc.
 A copy of ScalaUtils is
included in ScalaTest's jar file. If you wish to use ScalaUtils
in your production code as well, see the information on ScalaUtils below or the
scalautils.org
website. Here is the information for including ScalaTest
in your project:
Here's the code for your Maven POM:
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.10</artifactId> <version>2.0</version> <scope>test</scope> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.10" % "2.0" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
Using ScalaUtils in your production code
The ScalaUtils library grew out of the ScalaTest 2.0 effort. ScalaTest 2.0 is tightly integrated with ScalaUtils. Although you
should not include ScalaTest in your production class path (because when ScalaTest doesn't like something, it tends to
throw TestFailedException
), you can make use of ScalaUtils in you production code. Here's how:
Here's the code for your Maven POM:
<dependency> <groupId>org.scalautils</groupId> <artifactId>scalautils_2.10</artifactId> <version>2.0</version> </dependency>
And for sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalautils" % "scalautils_2.10" % "2.0"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
If you don't have it already, you'll also need Scala. You can use any 2.10 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaUtils 2.0 Scaladoc.
ScalaTest 1.9.2 (for Scala 2.10.0+ and 2.9.0+) is available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well):
Here's the code for your Maven POM for Scala 2.10.0:
<dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.10</artifactId> <version>1.9.2</version> <scope>test</scope> </dependency>
For sbt, version 0.10 or higher (for Scala 2.10.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.10" % "1.9.2" % "test"
And via sbt (for Scala 2.9.0+):
libraryDependencies += "org.scalatest" %% "scalatest" % "1.9.2" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release, and 2.9.0 can be used with any 2.9.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
For Scala 2.9.x:
If you don't have it already, you'll also need Scala. You can use any 2.9 release or any 2.10 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.9.2 Scaladoc.
ScalaTest 1.9.1 (for Scala 2.10.0+ and 2.9.0+) is available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well):
Or via sbt (version 0.10 or higher) with, (for Scala 2.10.0+):
libraryDependencies += "org.scalatest" % "scalatest_2.10" % "1.9.1" % "test"
And via sbt (for Scala 2.9.0+):
libraryDependencies += "org.scalatest" %% "scalatest" % "1.9.1" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.10 can be used with any 2.10.x release, and 2.9.0 can be used with any 2.9.x release. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.10.x:
For Scala 2.9.x:
If you don't have it already, you'll also need Scala. You can use any 2.9 release or any 2.10 release, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.9.1 Scaladoc.
ScalaTest 1.8 (for Scala 2.8.1, 2.8.2, 2.9.0, 2.9.0-1, 2.9.1, and 2.9.2) is available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well):
Or via sbt (version 0.10 or higher) with:
libraryDependencies += "org.scalatest" %% "scalatest" % "1.8" % "test"
Alternatively you can just download Jar files for the library and Scaladoc documentation by hand from Sonatype. The artifacts tagged with 2.9.0 can be used with any 2.9.x release, and 2.8.1 can be used with any 2.8.x release except 2.8.0. Jar files are valid zip files, so to access the Scaladoc documentation just unzip the Jar file. The Scaladoc Jars do not contain a top-level directory, however, so you should unzip them in an empty directory.
For Scala 2.9.x:
For Scala 2.8.1 and 2.8.2:
If you don't have it already, you'll also need Scala. You can use any 2.9 release or any 2.8 release later than 2.8.1, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.8 Scaladoc.
ScalaTest 1.7.2 (for Scala 2.8.1, 2.8.2, 2.9.0, 2.9.0-1, 2.9.1, and 2.9.2) is available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well):
Or via sbt (version 0.10 or higher) with:
libraryDependencies += "org.scalatest" %% "scalatest" % "1.7.2" % "test"
You can alternatively download a zip file. For Scala 2.9.0+ (including 2.9.0, 2.9.0-1, 2.9.1, and 2.9.2) download and unzip scalatest-1.7.2-for-scala-2.9.zip. For Scala 2.8.1+ (including 2.8.1, 2.8.2) download and unzip scalatest-1.7.2-for-scala-2.8.zip. In either case you'll get a scalatest-1.7.1 directory that contains all the good stuff.
If you don't have it already, you'll also need Scala. You can use any 2.9 release or any 2.8 release later than 2.8.1, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.7.2 Scaladoc.
ScalaTest 1.7.1 (for Scala 2.8.1, 2.8.2, 2.9.0, 2.9.0-1, 2.9.1, and 2.9.2) is available via the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well):
Or via sbt (version 0.10 or higher) with:
libraryDependencies += "org.scalatest" %% "scalatest" % "1.7.1" % "test"
You can alternatively download a zip file. For Scala 2.9.0+ (including 2.9.0, 2.9.0-1, 2.9.1, and 2.9.2) download and unzip scalatest-1.7.1-for-scala-2.9.zip. For Scala 2.8.1+ (including 2.8.1, 2.8.2) download and unzip scalatest-1.7.1-for-scala-2.8.zip. In either case you'll get a scalatest-1.7.1 directory that contains all the good stuff.
If you don't have it already, you'll also need Scala. You can use any 2.9 release or any 2.8 release later than 2.8.1, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.7.1 Scaladoc.
ScalaTest 1.7 experienced a deployment problem for a few artifact IDs and was replaced by 1.7.1. Please use ScalaTest 1.7.1 instead. The 1.7.1 release is identical with 1.7, except a Guice dependency was made optional in the pom.xml file and, most importantly, the correct jar files were deployed for all artifact IDs.
For ScalaTest 1.6.1 (for Scala 2.9.x, including 2.9.0, 2.9.0-1, 2.9.1, and 2.9.2), download and unzip scalatest-1.6.1.zip. You'll get a scalatest-1.6.1 directory that contains all the good stuff.
You can alternatively download it from the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well):
Or via sbt (version 0.10) with:
libraryDependencies += "org.scalatest" %% "scalatest" % "1.6.1" % "test"
If you don't have it already, you'll also need Scala. You can use 2.9.0.final or later, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.6.1 Scaladoc.
For ScalaTest 1.5.1 (for Scala 2.8.1 and 2.8.2), download and unzip scalatest-1.5.1.zip. You'll get a scalatest-1.5.1 directory that contains all the good stuff.
You can alternatively download it from the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well):
Or via sbt (version 0.10) with:
libraryDependencies += "org.scalatest" %% "scalatest" % "1.5.1" % "test"
If you don't have it already, you'll also need Scala. You can use 2.8.1.final or later, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.5.1 Scaladoc.
For ScalaTest 1.5 (for Scala 2.8.1), download and unzip scalatest-1.5.zip. You'll get a scalatest-1.5 directory that contains all the good stuff.
You can alternatively download it from the Sonatype OSS Maven repository (which is mirrored on the central Maven repository as well):
If you don't have it already, you'll also need Scala. You can use 2.8.1.final, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.5 Scaladoc.
For ScalaTest 1.4.1 (for Scala 2.9.0+), download and unzip scalatest-1.4.1.zip. You'll get a scalatest-1.4.1 directory that contains all the good stuff.
You can alternatively download it from the Sonatype OSS Maven repository:
If you don't have it already, you'll also need Scala. You can use 2.9.0.final or later, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.4.1 Scaladoc.
For ScalaTest 1.3 (for Scala 2.8), download and unzip scalatest-1.3.zip. You'll get a scalatest-1.3 directory that contains all the good stuff.
You can alternatively download it from the Sonatype OSS Maven repository:
If you don't have it already, you'll also need Scala. You can use 2.8.0.final or later, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.3 Scaladoc.
For ScalaTest 1.2 (for Scala 2.8), download and unzip scalatest-1.2.zip. You'll get a scalatest-1.2 directory that contains all the good stuff.
You can alternatively download it from the Sonatype OSS Maven repository:
If you don't have it already, you'll also need Scala. You can use 2.8.0.final or later, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.2 Scaladoc.
For ScalaTest 1.1 (for Scala 2.7.x), download and unzip scalatest-1.1.zip. You'll get a scalatest-1.1 directory that contains all the good stuff.
You can alternatively download it from the Sonatype OSS Maven repository:
If you don't have it already, you'll also need Scala. You can use 2.7.3.final or later, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.1 Scaladoc.
For ScalaTest 1.0, download and unzip scalatest-1.0.zip. You'll get a scalatest-1.0 directory that contains all the good stuff.
You can alternatively download it from the Sonatype OSS Maven repository:
If you don't have it already, you'll also need Scala. You can use 2.7.3.final or later, which you can get from here:
For a list of the changes in this release, see the release notes. For detailed documentation, see the ScalaTest 1.0 Scaladoc.


What do you want to do today?
Reimbursement Id:
Request info from applicant
Request info from applicant
Request info from lower manager
Manager level you request info from:
Direct Manager
Department Head
Request info from manager
Sign reimbursement
Sign the reimbursement
Decline reimbursement
Reason for decline:
Decline the reimbursement
Confirm reimbursement
Confirm Reimbursement
Upload info for reimbursement
Upload Info
Benco only features
Refresh Info
Back


Package providing an alternative to the Singleton and Prototype design
patterns, including a consistent approach to configuration management.
It builds on the com.interface21.beans package.
This package and related packages are discussed in Chapter 11 of
Expert One-On-One J2EE Design and
Development
by Rod Johnson (Wrox, 2002).


This program will take you back to basics, using good compound movements to build strength.
These exercises will give you a total body workout. They are big muscle building moves, which will also supercharge your metabolism, meaning you will definitely be hungry after it!
Complete 3 to 4 sets of 6 repetitions with no more than 60 seconds rest between sets. With the weight you select you should only just be able to complete the 6 reps.


{% extends 'contents/_base.html' %} {% block title %}How to Propose a Tutorial{% endblock title %} {% block content %} {% url 'page' path='speaking/cfp' as speaking_cfp_url %} {% url 'page' path='speaking/talk' as speaking_talk_url %}
First of all, thank you considering giving a tutorial in PyCon Taiwan 2018.
Generally speaking, Good tutorials possess most of the traits good talks have. The most discernible differences of a tutorial from a talk are the hands-on nature and the longer time length. By longer time length, generally more content is required and it should remain interesting and keep the attendees awake and hyped even after hours of lecture and exercises. By containing hands-on exercises, experience of teaching coding to people is necessary. You also need at least two teaching assistants for a general class size of 20 people, who you should be able to comfortably communicate with during the tutorial. Both differences requires many times of practice and experience.
Therefore, the tutorial speaker usually satisfies at least one of the following prerequisites:
We might ask you to give the tutorial to the community before the conference if you lack the experience.
All tutorials are held at most three weeks before the conference dates. Given the availability of teaching space, tutorial speakers have full authority to decide when to give one's tutorial.
It is also possible to give tutorials on-site, that is, during the conference dates. In that case, please note your preference in the Supplementary section of your proposal and contact us directly.
The charging of tutorials are independent of the charging of conference itself. Charging policy will be jointly decided by both the tutorial speaker and PyCon TW Program committee. The charging can be determined respectively for each tutorial though we will seek an agreement on the overall policy between all tutorial speakers.
Note that if the tutorial is held on-site, there will be no extra charging available.
The easiest and the best answer: Go speak and involved at the local Python communities!
{% endblock content %}


Hi, thanks for checking out my site. Below you can find links to some of my GitHub repositories, and an 'About me' page. To the right are links to the actual sites themselves, if you'd rather just see how they look. Projects are listed newest to oldest.


Web Security
Here, you will find information about your system and even your location and the temperature where you are. This is to help you understand just how much can be found about you from visiting a web page.
| Property | Information |
| Web Browser Name | |
| Web Browser Version | |
| Operating System | |
| Screen Width | |
| Screen Height | |
| Screen Pixel Depth | |
| Latitude | |
| Longitude | |
| Altitude | |
| Temperature |
Here are some articles with tips for staying secure online:
1. Kaspersky Lab - Top 10 Internet Safety Rules & What Not to Do Online
This article covers tons of subjects in relation to staying safe online, including browsing, privacy settings, downloads, shopping, and passwords. There is a lot of information here for general safety.
2. McAfee - 10 Tips To Stay Safe Online
This article covers similar topics to the first, though it also has information that was not covered in the first, such as firewalls and VPNs.
3. Mozilla - How to stay safe on the web
This article will help users that use Firefox make sure that they remain safe while using the browser. This information almost entirely applies to only Firefox users, but there are some general tips at the bottom of the page.


the and that afrotherian with for from are morphological taxa characters were analysis within {background stem than which all was ==> character data have Yes more phylogenetic The early not but extant support taxon Afrotheria fossil [], been margin sister change {border-style Eocene crown these analyses clade extinct interordinal phylogeny placed placental px;} #ffffff;} (=>) UA_DT) some []. features rather synapomorphies among relationships this tree either new placement al. clades most present scaled absent across alternative could group supported two (OSA_AT, (Table Macroscelidea Paenungulata evidence has monophyly multistate order ordered origin other primitive set such supraordinal unordered Afrotheria, Kelba Tubulidentata afrotherians genomic molecular number only optimized parsimony recovered results their unambiguous (order Cretaceous Herodotius UA_AT, Widanelfarasia also between chromosomal consistently different given identified large mammal mammals px; there {font-family Afroinsectivora Afrosoricida, Hyracoidea Oligocene Tethytheria addition afrotherians, based both consensus derived evolution first font-size genus here herodotiines hypotheses index less members morphology possible recently scored species states trees unambiguously will "proto-ungulate" (Afrosoricida, (Hyracoidea, (OSA_DT) Acad African Afroinsectiphillia Afrosoricida Arsinoitherium Chambius Macroscelidea, Morphological Murphy Mus OSA_DT, One Paenungulata, Paleogene Phylogenetic Proboscidea Sci aardvarks analysis, ancestral basal because bold buccal can double; enigmatic file golden however, hypoconid included including informative into living macroscelideans mammalian orders paenungulates parsimonious provided resolved sequence small state topology well (Macroscelidea, (OSA) Additional Africa Afroinsectivora, Amrine-Madsen Miocene Natl Parsimony Press Tenrecoidea This Tubulidentata, again al.'s alone along anterior any bootstrap border-color border-width branches characters. clade, clade. competing constrained containing data, delayed dental did diversity each eutherian exclusion fact following forms future highly how late lower material molars multiple never one onto optimization proboscideans recent relative single solid; study synapomorphy testes through under using variably while {font-style {font-weight (=> (Mammalia, (OSA_DT, (Proboscidea, (UA) (UA_AT, =>) Adams Analysis Bayesian Character DNA Herodotius, Hyracoidea, Late North Paenungulata. Paleocene Pseudoungulata Results Royal Tubulidentata), University Vert [,,]. [,], [,]. aardvarks, accelerated afrosoricid afrosoricids alignment alleged analyses. analysis. branching considered consistency consistent courier; cranial current diverse due em; endemic entoconid forming found four herodotiine homoplasy hypocristid hypothesis internal interrelationships latter long lumbar macroscelidean macroscelideans, major might missing near nested obliqua obvious oldest optimal ordinal paenungulate paraconid parastyles part pattern previous problem proboscidean protoconid pt;} published radiation remains root sample sequences should statistically tenrecs tethytherian those total transformations unique very when


In the following example, we display the Sencha logo as a series of paths with 3 multi-stop gradients. The logo was created with a drawing tool and exported to SVG, which we used for the pathing. Because the new Ext.Draw system extends from Component, we get all the functionality available to any component. In this example, the component has been made resizable with a simple configuration. Note that because we use vectors to define the image, it is scalable to any size and is fully resolution independent. View Source.
See our introductory blog post on the topic here.


Bergsig groet juf Miemie Botha (1989 - 2019) wat ek het is net geleen, wat ek is, is net genade. Thank you for all your kindness and love.  Ons gaan jou baie mis. Mooi loop!
Our class of 2019 are currently writing their last high school examination. Who would have thought time could pass by so quickly?! We know you are all going to make us very proud. Soos Mevrou Potgieter vanoggend gesê het, kry ons trane in ons oë by die gedagte dat ons julle moet groet, al weet ons julle is gereed om jul vlerke te sprei.  The world is your oyster.
A very big welcome to Mrs Mmamosadi Mmekoa who was appointed as a new deputy from the 1st November 2019. Ons is baie trots op Mevrou Carien Loubser wat ook vanaf 1 November 2019 aangestel is as adjunkhoof.
Be a woman with a mind, a woman with attitude and a lady with class.  Lion Kotze 1ste junior 21km. Anushke Bruwer se 1ste 10km asook Kaylen Scholtz se 1ste 10km, albei in skitterende tyd voltooi! Well done, you make us proud!
Baie dankie aan elke deelnemer en ondersteuner/Thank you for your support! What a lovely evening!


WITNESS LIST Appropriations Committee March 8, 1999-8:00A Budget On: Brieden, John (Texas Veterans Commission) Cox, Sue (Texas Council on Problem Gambling) Demerson, Aaron (Comptroller of Public Accounts) Doebner, Thomas (Texas Department of Transportation) Dossett, James (Texas Department of Transportation) Garza, Tony (Railroad Commission) Goerkie, James (Commission on State Emergency Communications) Hamilton, Billy (Comptroller of Public Accounts) Harris, Ron (Commission on State Emergency Communications) Heald, Charles (Texas Department of Transportation) Hodgkiss, Melvin (Railroad Commission) Horwitz, Rita (Pension Review Board) Kiplin, Kimberly (Texas Lottery Commission) Laney, David (Texas Department of Transportation) Miers, Harriet (Texas Lottery Commission) Purcell, Carolyn (Department of Information Resources) Pyka, Kathy (Railroad Commission) Sanchez, Bart (Texas Lottery Commission) Schieck, David (Railroad Commission) Spence, Carey (Commission on State Emergency Communications) Williams, Cathy (Texas Department of Transportation)


About me
Principal Curriculum Developer, Docker Inc.
Docker Captain
Former Distinguished Software Architect
Former Chief Software Architect
Blogger, Author
@gnschenker
http://www.linkedin.com/in/gabrielschenker
www.lostechies.com/gabrielschenker
Demo
Containerize a Node JS app
Demo
Create a Docker Swarm
Demo
Deploy an app into the Swarm
Demo
Use a Secret


Exercise 2: Select a row (XAM280)
This exercise will continue building the Fun Flags ListView application. You'll add support to navigate to the provided details page when a flag is tapped in the ListView
To complete the exercise, you will need Visual Studio for Windows or macOS with the Xamarin development tools installed. You will also need either an emulator/simulator or a device to run the exercise on. Please see the setup page if you need help installing the Xamarin development environment.
Open the starter solution
This exercise is a continuation of the previous exercise. You can use your existing solution or begin from the prior Exercise 1 > Completed solution in your copy of the cloned or downloaded course materials.
Verify that we have a root NavigationPage
In this step, you'll verify that a NavigationPage
is available to perform stack navigation. You'll use it to display the detail page.
- Open App.xaml.cs which holds your
Application
class. - Check the assignment to the
MainPage
property. To use stack-based navigation, this should be set to aNavigationPage
. The constructor of theNavigationPage
takes the first page to display (the "root").
Handle the selection of an item in the ListView
Next, you'll handle the selection for a single flag and provide navigation to a second (details) screen.
- Wire up to the
ItemTapped
event on theListView
. You can do this in XAML or in code behind if the element has a name. - The
ItemTapped
event passes anItemTappedEventArgs
which has the actual object from the collection assigned to theItemsSource
property, however it needs to be cast. Recall that in this application, each data item is represented aFlag
object. Retrieve that object out from the event arguments and cast it to aFlag
. -
You have a property on your
FunFlactsViewModel
namedCurrentFlag
of typeFlag
which the details page uses to display the current flag. Set theFunFlactsViewModel.CurrentFlag
property to the flag from the event arguments. You'll need to retrieve the object from theDependencyService
. -
Use the
Page.Navigation
property to navigate to a new instance of the details page. Use thePushAsync
method so that you can use the C#async
andawait
support to ensure you see exceptions. - Run the application and try tapping on an item to see it navigate to the details page. Use the arrow keys on the detail page to move to a different flag and then press the back button in the header. Notice that the original flag is still selected in the
ListView
.
async void OnItemTapped(object sender, ItemTappedEventArgs e)
{
DependencyService.Get<FunFlactsViewModel>().CurrentFlag = (Flag)e.Item;
await this.Navigation.PushAsync(new FlagDetailsPage());
}
Bind to SelectedItem
The ListView
has another property you can use to track and manage selection: SelectedItem
. This property is also bindable; you can use it to connect to any property of the BindingContext
, such as the CurrentFlag
property! In fact, if you make the binding two-way, you can get it to update the state of the ListView automatically.
- Delete the code in the
OnItemTapped
method that is setting theCurrentFlag
property - you won't need it anymore; all you need now is the code to navigate to the second page. - Add a binding in the XAML for the
ListView.SelectedItem
property to connect it to theCurrentFlag
property. Make sure it's marked as a two-way binding, and then run the app again and change the current flag on the details page using the up/down buttons. Then back up to theListView
and note that it tracks the current selection!
<ListView ItemsSource="{Binding Flags}"
SelectedItem="{Binding CurrentFlag, Mode=TwoWay}"
ItemTapped="OnItemTapped" />
Exercise summary
In this exercise, you added support to detect selection within the ListView and navigate to a second screen.
You can view the completed solution in the Exercise 2 > Completed folder of your copy of the cloned or downloaded course materials.


{% extends "structureadmin.html" %} {% block body %}
You can go back to the previous page, or return home.
{{ error }}


My first RPub
30 Jun 2012I'm quite impressed with Rstudio, an integrated development environment (IDE) for R. If you haven't tried it yet, I strongly recommend you to do so, you won't regret it.
One of the great things about RStudio is that it allows you to work with R markdown which is great for creating reproducible web reports with a fairly simple syntax.
Although I've been playing with RStudio and R markdown for a while, I recently decided to try RPubs, a service provided by RStudio in which you can publish documents on the web with the click of a button.
Anyway, I just wanted to share my first Rpub about visualizing hurricane trajectories in North America. For those readers interested in the behind the scenes issues, here's the code I used in RStudio to create the markdown file for my first RPub.


//
Custom Functionality
Last semester, I teamed up with some other students to create Scumbag Galaxy.
My role in the project was comprised almost entirely with my custom event-based user interface API. I had to build the system from the ground up using all
original code. The engine we used (MonoGame) was a frequent tool for developing Xbox 360 games. As such, in-engine mouse support was near non-existant. So I created an
efficient engine to run mouse events. On the front end, the engine makes use of layered rectangle objects, each with their own mouse events. Boxes on ‘top’ capture events and display
above ‘lower’ objects. All of this is handled through the parent UIBox class. All UI elements are derived from it, allowing the engine backend to work seamlessly
no matter what type of window is needed during the design process.
The backend of the engine is where things get more complex. I used a custom version of quad tree architecture to achieve resource-efficient mouse collision detection.
Native MonoGame only provides the mouse location for the current frame. The GameBoard class manages nearly everything. On creation, it divides up the screen space
using a quickly-searchable tree structure. The smallest section of screen that fits into this tree holds an array of references to UI Boxes that overlap with it.
In the UIBox constructor, the object places itself into the GameBoard tree (ordered by layer and visibility). This system is highly efficient to determine with which objects
the mouse collides. Instead of checking thousands of UI objects every frame, the tree structure reduces that number to less than 10.
Mouse events are checked for during every frame by comparing the previous mouse location with the current one (but it is much more complicated than that). Layer-based
mouse events have innumerable edge cases. If the mouse stays on a lower object for both steps, but moves onto a higher layered object (one that overlaps the lower
object) in those two steps, what events trigger? Comments in the code on GitHub go through each of these ideas and how they were fixed, so I won’t cover them here.
When a mouse event is detected for a UIBox, it calls that box’s corresponding mouse event function.
//
Engine Capabilities
View and Zoom Support
I implemented a fully scale-able viewport system. The player can zoom in on text and units or pan around the board, all without breaking the underlying mouse event features.
Window Drag and Layering
The API can (and is) used to create dynamic window objects with proper layering. Drag and drop functionality, mouse-enter and mouse-leave, and clicks all support the layering functionality.
Efficient and Elegant Upscaling
Due to the efficiency of my custom tree data structure, stress tests proved that the engine could support the full-force complexity of tactical RPG games filled with tens of thousands of UI objects.
Game States
Quickly and dynamically switch between entirely different screen layouts. This functionality was used for our game's title screen, but could easily be used for entirely new UI windows such as maps or inventory screens.
Copyright © 2016 Daniel Timko


--- layout: page title: Posts --- {% for post in site.posts %} {% include post_item.html %} {% endfor %}
All tags: {{ site | tag_cloud }}


Chi Chi - After Completion
63. Chi Chi - After Completion
-- --
----- above K'an The Abysmal, Water
-- --
-----
-- -- below Li The Clinging, Flame
-----
The Judgement
After Completion. Success in small matters.
Perseverance furthers.
At the beginning good fortune,
At the end disorder.
The Image
Water over fire: the image of the condition
In After Completion.
Thus the superior man
Takes thought of misfortune
And arms himself against it in advance.
The Lines
Nine at the beginning means:
He brakes his wheels.
He gets his tail in the water.
No blame.
() Six in the second place means:
The woman loses the curtain of her carriage.
Do not run after it;
On the seventh day you will get it.
Nine in the third place means:
The Illustrious Ancestor
Disciplines the Devil's Country.
After three years he conquers it.
Inferior people must not be employed.
Six in the fourth place means:
The finest clothes turn to rags.
Be careful all day long.
Nine in the fifth place means:
The neighbor in the east who slaughters an ox
Does not attain as much real happiness
As the neighbor in the west
With his small offering.
Six at the top means:
He gets his head in the water. Danger.


We use a standard input element with type="radio"
for radio buttons but we need to wrap it in a div to get the right style for the different states.
Use rows and columns to create a responsive layout, in the example below radio buttons will be placed inline on medium sized screens and up. On smaller screens the radio buttons will stack on top of each other, test by resizing the window. Use one of the following utility classes .my-*
, .mb-*
or .mt-*
to add spacing between the different options, ie. mb-2 mb-md-0
to get a small bottom margin on small screens and below.


The Dalvik virtual machine can produce a complete dump of the contents of the virtual heap. This is very useful for debugging memory usage and looking for memory leaks. Getting at the information can be tricky, but has become easier in recent releases.
In what follows, the version number refers to the software release running on the phone. To take advantage of the DDMS integration, you will also need a sufficiently recent version of DDMS.
The first step is to cause the VM to dump its status, and then pull the hprof data off. The exact manner for doing so has changed over time.
There is a runhat
shell function, added by
build/envsetup.sh
, that partially automates these steps. The
function changes in each release to accommodate newer behavior, so you have
to be careful that you don't use the wrong version.
You can only generate heap data on the emulator or a device with root access, because of the way the dump is initiated and where the output files go.
Get a command shell on the device:
$ adb shell
You can verify that you're running as root with the id
command.
The response should look like uid=0(root) gid=0(root)
. If not,
type su
and try again. If su
fails, you're out
of luck.
Next, ensure the target directory exists:
# mkdir /data/misc # chmod 777 /data/misc
Use ps
or DDMS to determine the process ID of your application,
then send a SIGUSR1
to the target process:
# kill -10 <pid>
The signal causes a GC, followed by the heap dump (to be completely accurate, they actually happen concurrently, but the results in the heap dump reflect the post-GC state). This can take a couple of seconds, so you have to watch for the GC log message to know when it's complete.
Next:
# ls /data/misc/heap-dump* # exit
Use ls
to check the file names, then exit
to quit
the device command shell.
You should see two output files, named
/data/misc/heap-dump-BLAH-BLAH.hprof
and
.hprof-head
, where BLAH is a runtime-generated value
that ensures the filename is unique. Pull them off of the device and
remove the device-side copy:
$ adb pull /data/misc/heap-dump-BLAH-BLAH.hprof tail.hprof $ adb pull /data/misc/heap-dump-BLAH-BLAH.hprof-head head.hprof $ adb shell rm /data/misc/heap-dump-BLAH-BLAH.hprof /data/misc/heap-dump-BLAH-BLAH.hprof-head
Merge them together and remove the intermediates:
$ cat head.hprof tail.hprof > dump.hprof $ rm head.hprof tail.hprof
You now have the hprof dump in dump.hprof
.
Some steps were taken to make this simpler. Notably, the two output
files are now combined for you, and a new API call was added that allows
a program to write the dump at will to a specific file. If you're not
using the API call, you still need to be on an emulator or running as root.
(For some builds, you can use adb root
to restart the adb
daemon as root.)
The basic procedure is the same as for 1.0/1.1, but only one file will
appear in /data/misc
(no -head
), and upon
completion you will see a log message that says "hprof: heap dump completed".
It looks like this in the log:
I/dalvikvm( 289): threadid=7: reacting to signal 10 I/dalvikvm( 289): SIGUSR1 forcing GC and HPROF dump I/dalvikvm( 289): hprof: dumping VM heap to "/data/misc/heap-dump-tm1240861355-pid289.hprof-hptemp". I/dalvikvm( 289): hprof: dumping heap strings to "/data/misc/heap-dump-tm1240861355-pid289.hprof". I/dalvikvm( 289): hprof: heap dump completed, temp file removed
Summary: as above, use mkdir
and chmod
to ensure the directory exists and is writable by your application.
Send the SIGUSR1
or use the API call to initiate a dump.
Use adb pull <dump-file>
and adb shell rm
<dump-file>
to retrieve the file and remove it from the
device. The concatenation step is not needed.
The new API is in the android.os.Debug
class:
When called, the VM will go through the same series of steps (GC and generate a .hprof file), but the output will be written to a file of your choice, e.g.public static void dumpHprofData(String fileName) throws IOException
/sdcard/myapp.hprof
. Because you're
initiating the action from within the app, and can write the file to
removable storage or the app's private data area, you can do this on a
device without root access.
No real change to the way profiling works.
However, 1.6 introduced the WRITE_EXTERNAL_STORAGE
permission, which is required to write data to the SD card. If you're
accustomed to writing profile data to /sdcard
, you will
need to enable the permission in your application's manifest.
In 2.0, features were added that allow DDMS to request a heap dump on demand, and automatically pull the result across. Select your application and click the "dump HPROF file" button in the top left. This always writes files to the SD card, so you must have a card inserted and the permission enabled in your application.
DDMS heap dump requests are now streamed directly out of the VM, removing the external storage requirement.
The data file format was augmented slightly from the common hprof format,
and due to licensing restrictions the modified hat
tool cannot
be distributed. A conversion tool, hprof-conv
, can be used
to strip the Android-specific portions from the output. This tool was
first included in 1.5, but will work with older versions of Android.
The converted output should work with any hprof data analyzer, including
jhat
, which is available for free in the Sun JDK, and
Eclipse MAT.
Copyright © 2009 The Android Open Source Project


Currently you can only see the link of a "installed" plugin and not a name or a description of it.
It would be nice if it were a possibility to give captions and descriptions to plugins,
so you can see easier which plugin you have "installed" or you want to enable or disable.
Example:
Name
(Link)
[ ] [X]
Description
Names and descriptions could be given by the user manually while adding a plugin.


| testthat_results {testthat} | R Documentation |
testthat_results
object from the test results
as stored in the ListReporter results field.Create a testthat_results
object from the test results
as stored in the ListReporter results field.
testthat_results(results)
results |
a list as stored in ListReporter |
its list argument as a testthat_results
object
ListReporter


package stat
The stat
package contains classes, traits and objects for basic statistical
functions and analyses. The package object itself defines an implicit
conversion from scalation.linalgebra.VectorD
to StatVector
.
- Alphabetic
- By Inheritance
- stat
- AnyRef
- Any
- Hide All
- Show All
- Public
- All
Type Members
-
class
Anova
extends AnyRef
The Anova class provides the functions necessary for performing a one-way ANalysis Of VAriance (ANOVA) on the input data matrix x.
The Anova class provides the functions necessary for performing a one-way ANalysis Of VAriance (ANOVA) on the input data matrix x. The data matrix: row i - i-th group/treatment column j - j-th replica
-
class
BatchVector
extends AnyRef
The
BatchVector
class contains aVectorD
for maintaining experimental data in multiple batches and methods for computing statistics on these data.The
BatchVector
class contains aVectorD
for maintaining experimental data in multiple batches and methods for computing statistics on these data. Ex: It can be used to support the Method of Batch Means (MBM). -
class
Canvas
extends Panel
Create a canvas on which to draw the histogram.
-
class
FramelessHistogram
extends AnyRef
The
FramelessHistogram
class should be used in embedded applications. -
class
GoodnessOfFit_CS
extends Error
The
GoodnessOfFit_CS
class is used to fit data to probability distributions.The
GoodnessOfFit_CS
class is used to fit data to probability distributions. Choosing the number of 'intervals' can be challenging and can affect the result: Suggestions: each interval should have 'E_i = n*p_i >= 5' and intervals >= sqrt (n). It uses the Chi-square goodness of fit test with equal width intervals.- See also
www.eg.bucknell.edu/~xmeng/Course/CS6337/Note/master/node66.html Compute the following for each interval and sum over all intervals. (O_i - E_i)^2 / E_i where O_i and E_i are the observed and expected counts for interval 'i', respectively.
-
class
GoodnessOfFit_CS2
extends Error
The
GoodnessOfFit_CS2
class is used to fit data to probability distributions.The
GoodnessOfFit_CS2
class is used to fit data to probability distributions. Suggestions: each interval should have 'E_i = n*p_i >= 5' and intervals >= sqrt (n). It uses the Chi-square goodness of fit test with equal probability intervals.- See also
www.eg.bucknell.edu/~xmeng/Course/CS6337/Note/master/node66.html Compute the following for each interval and sum over all intervals. (O_i - E_i)^2 / E_i where O_i and E_i are the observed and expected counts for interval 'i', respectively.
-
class
GoodnessOfFit_KS
extends Error
The
GoodnessOfFit_KS
class is used to fit data to a probability distribution.The
GoodnessOfFit_KS
class is used to fit data to a probability distribution. It uses the Kolmogorov-Smirnov Goodness of Fit Test. Determine the maximum absolute difference 'd_max' between the data points 'd_i' and the theoretical value from a CDF F,d_max = max 1≤i≤n {|Fe(d_i) - F(d_i)|} (concept)
d_max = max 1≤i≤n {F(d_i) − (i−1)/n, i/n − F(d_i)} (calculation)
where 'Fe(.)' is the empirical distribution and 'F(.)' is the theoretical distribution. If 'd_max' is large, the fit should be rejected.
- See also
www.itl.nist.gov/div898/handbook/eda/section3/eda35g.htm ---------------------------------------------------------------------------------
www.eg.bucknell.edu/~xmeng/Course/CS6337/Note/master/node66.html
-
class
Histogram
extends VizFrame
The
Histogram
class takes a vector of values, counts the number of values in each of several intervals and displays the counts vertically in a histogram. -
final
class
MM_StatVector
extends AnyVal
The
MM_StatVector
value class provides methods for computing statistics on data vectors.The
MM_StatVector
value class provides methods for computing statistics on data vectors. Both maximum likelihood and unbiased estimators are supported. Unbiased should only be used on sample (not population) data. Ex: It can be used to support the Method of Independent Replications (MIR). For efficiency,MM_StatVector
is a value class that enriches theVectorD
. The corresponding implicit conversion in thestat
package object.- See also
stackoverflow.com/questions/14861862/how-do-you-enrich-value-classes-without-overhead -----------------------------------------------------------------------------
-
class
StatTable
extends Frame
The
StatTable
class display statistical results in a frame's table. -
final
class
StatVector
extends AnyVal
The
StatVector
value class provides methods for computing statistics on data vectors.The
StatVector
value class provides methods for computing statistics on data vectors. Both maximum likelihood and unbiased estimators are supported. Unbiased should only be used on sample (not population) data. Ex: It can be used to support the Method of Independent Replications (MIR). For efficiency,StatVector
is a value class that enriches theVectorD
. The corresponding implicit conversion in thestat
package object.- See also
stackoverflow.com/questions/14861862/how-do-you-enrich-value-classes-without-overhead -----------------------------------------------------------------------------
-
class
Statistic
extends Error
The
Statistic
class is used to collect values and compute sample statistics on them (e.g., waiting time).The
Statistic
class is used to collect values and compute sample statistics on them (e.g., waiting time). Contrast withTimeStatistic
defined below. -
class
TimeStatistic
extends Statistic
The
TimeStatistic
class is used to collect values and compute time-persistent statistics on them (e.g., Number in Queue).The
TimeStatistic
class is used to collect values and compute time-persistent statistics on them (e.g., Number in Queue).- See also
staff.unak.is/andy/Year%203%20Simulation/Laboratories/v4manual/internal.htm
Value Members
-
implicit
def
vectorC2StatVector(x: VectorC): StatVector
Implicit conversion from
VectorD
toStatVector
, which supports more advanced statistical operations on vectors (e.g., covariance).Implicit conversion from
VectorD
toStatVector
, which supports more advanced statistical operations on vectors (e.g., covariance). Other vector types require to conversion toVectorD
via 'toDouble'. Caveat: won't work for vectors of string numbers (VectorS
).- x
the vector to be enriched
- implicit def vectorD2StatVector(x: VectorD): StatVector
- implicit def vectorI2StatVector(x: VectorI): StatVector
- implicit def vectorL2StatVector(x: VectorL): StatVector
- implicit def vectorQ2StatVector(x: VectorQ): StatVector
- implicit def vectorR2StatVector(x: VectorR): StatVector
-
object
AnovaTest
extends App
This object is used to test the Anova class.
This object is used to test the Anova class.
- See also
wiki.uiowa.edu/display/bstat/One-way+fixed+effects+ANOVA > run-main scalation.stat.AnovaTest
-
object
BatchVectorTest
extends App
The
BatchVectorTest
object provides an example of how to use theBatchVector
class to implement the Method of Batch Means (MBM). -
object
Conversions
The
Conversions
object provide implicit conversion from memory mapped vectors toStatVectors
. -
object
GoodnessOfFit_CS
The
GoodnessOfFit_CS
companion object provides two discrepancy metrics to capture the differences between observed 'o' and expected 'o' counts.The
GoodnessOfFit_CS
companion object provides two discrepancy metrics to capture the differences between observed 'o' and expected 'o' counts.- See also
en.wikipedia.org/wiki/G-test
-
object
GoodnessOfFit_CS2Test
extends App
The
GoodnessOfFit_CS2Test
object is used to test theGoodnessOfFit_CS
class.The
GoodnessOfFit_CS2Test
object is used to test theGoodnessOfFit_CS
class.- See also
www.seattlecentral.edu/qelp/sets/057/057.html > run-main scalation.stat.GoodnessOfFit_CS2Test
-
object
GoodnessOfFit_CSTest
extends App
The
GoodnessOfFit_CSTest
object is used to test theGoodnessOfFit_CS
class.The
GoodnessOfFit_CSTest
object is used to test theGoodnessOfFit_CS
class.- See also
www.seattlecentral.edu/qelp/sets/057/057.html > run-main scalation.stat.GoodnessOfFit_CSTest
-
object
GoodnessOfFit_KS
The
GoodnessOfFit_KS
object provides methods to approximate the critical values/p-values for the KS Test.The
GoodnessOfFit_KS
object provides methods to approximate the critical values/p-values for the KS Test.P(D_n < d)
- See also
sa-ijas.stat.unipd.it/sites/sa-ijas.stat.unipd.it/files/IJAS_3-4_2009_07_Facchinetti.pdf
www.jstatsoft.org/article/view/v008i18/kolmo.pdf
-
object
GoodnessOfFit_KSTest
extends App
The
GoodnessOfFit_KSTest
object is used to test theGoodnessOfFit_KS
class.The
GoodnessOfFit_KSTest
object is used to test theGoodnessOfFit_KS
class.- See also
www.seattlecentral.edu/qelp/sets/057/057.html > run-main scalation.stat.GoodnessOfFit_KSTest
-
object
GoodnessOfFit_KSTest2
extends App
The
GoodnessOfFit_KSTest2
object is used to test theGoodnessOfFit_KS
object.The
GoodnessOfFit_KSTest2
object is used to test theGoodnessOfFit_KS
object.- See also
www.utdallas.edu/~herve/Abdi-Lillie2007-pretty.pdf > run-main scalation.stat.GoodnessOfFit_KSTest2
-
object
GoodnessOfFit_KSTest3
extends App
The
GoodnessOfFit_KSTest3
object is used to test theGoodnessOfFit_KS
object.The
GoodnessOfFit_KSTest3
object is used to test theGoodnessOfFit_KS
object.- See also
www.jstatsoft.org/article/view/v008i18/kolmo.pdf > run-main scalation.stat.GoodnessOfFit_KSTest3
-
object
GoodnessOfFit_KSTest4
extends App
The
GoodnessOfFit_KSTest4
object is used to test theGoodnessOfFit_KS
object.The
GoodnessOfFit_KSTest4
object is used to test theGoodnessOfFit_KS
object. Fifty data points generated by a random variate generator for the Normal distribution are tested to see if they pass the Normality test. > run-main scalation.stat.GoodnessOfFit_KSTest4 -
object
HistogramTest
extends App
The
HistogramTest
object is used to test theHistogram
class.The
HistogramTest
object is used to test theHistogram
class. As 'k' increases, the sum of Uniform approaches Normal. > run-main scalation.stat.HistogramTest -
object
MM_StatVectorTest
extends App
The
MM_StatVectorTest
object is used to test theMM_StatVector
class.The
MM_StatVectorTest
object is used to test theMM_StatVector
class. > run-main scalation.stat.MM_StatVectorTest -
object
MM_StatVectorTest2
extends App
The
MM_StatVectorTest2
object provides an example of how to use theMM_StatVector
class to implement the Method of Independent Replications (MIR) following a simple two-stage procedure. -
object
MethodOfMoments
The
MethodOfMoments
object provides methods for estimating parameters for popular probability distributions using the Method of Moments (MOM).The
MethodOfMoments
object provides methods for estimating parameters for popular probability distributions using the Method of Moments (MOM). The main alternative is to use Maximum Likelihood Estimators (MLE).- See also
www.math.uah.edu/stat/point/Moments.html
-
object
Normality
The
Normality
object provides methods for testing Normality based on skewness and kurtosis.The
Normality
object provides methods for testing Normality based on skewness and kurtosis. Such test are more suitable for large sample sizes where more powerful goodness-of-fit tests tend to frequently reject Normality.- See also
en.wikipedia.org/wiki/D%27Agostino%27s_K-squared_test
stats.stackexchange.com/questions/2492/is-normality-testing-essentially-useless
stats.stackexchange.com/questions/29731/regression-when-the-ols-residuals-are-not-normally-distributed
-
object
NormalityTest
extends App
The
NormalityTest
object is used to test theNormality
object.The
NormalityTest
object is used to test theNormality
object.- See also
www.seattlecentral.edu/qelp/sets/057/057.html > run-main scalation.stat.NormalityTest
-
object
Q_Q_Plot
extends Error
The
Q_Q_Plot
object produces Quantile-Quantile plots that are used to compare probability distributions. -
object
Q_Q_PlotTest
extends App
The
Q_Q_PlotTest
object is used to test theQ_Q_Plot
object: distribution vs.The
Q_Q_PlotTest
object is used to test theQ_Q_Plot
object: distribution vs. distribution. > run-main scalation.stat.Q_Q_PlotTest -
object
Q_Q_PlotTest2
extends App
The
Q_Q_PlotTest2
object is used to test theQ_Q_Plot
object: data vector vs.The
Q_Q_PlotTest2
object is used to test theQ_Q_Plot
object: data vector vs. distribution. > run-main scalation.stat.Q_Q_PlotTest2 -
object
StatTableTest
extends App
The
StatTableTest
is used to test theStatTable
class. -
object
StatVector
The
StatVector
companion object extends statistics vector operations to matrices. -
object
StatVectorTest
extends App
The
StatVectorTest
object is used to test theStatVector
class.The
StatVectorTest
object is used to test theStatVector
class.- See also
www.mathworks.com/help/stats/skewness.html > run-main scalation.stat.StatVectorTest
-
object
StatVectorTest2
extends App
The
StatVectorTest2
object provides an example of how to use theStatVector
class to implement the Method of Independent Replications (MIR) following a simple two-stage procedure.The
StatVectorTest2
object provides an example of how to use theStatVector
class to implement the Method of Independent Replications (MIR) following a simple two-stage procedure. > run-main scalation.stat.StatVectorTest2 -
object
StatVectorTest3
extends App
The
StatVectorTest3
object is used to test theStatVector
companion object.The
StatVectorTest3
object is used to test theStatVector
companion object.- See also
www.itl.nist.gov/div898/handbook/pmc/section5/pmc541.htm > run-main scalation.stat.StatVectorTest3
-
object
StatVectorTest4
extends App
The
StatVectorTest4
object is used to test theStatVector
companion object.The
StatVectorTest4
object is used to test theStatVector
companion object.- See also
www.itl.nist.gov/div898/software/dataplot/refman2/auxillar/corrmatr.htm > run-main scalation.stat.StatVectorTest4
-
object
Statistic
extends Error
The
Statistic
companion object provides additional values and functions. -
object
StatisticTest
extends App
The
StatisticTest
object is used to test theStatistic
andTimeStatistic
classes. -
object
TimeStatistic
extends Error
The
TimeStatistic
companion object provides additional functions.


... loading makes ...
{{make.name}}
... (loading models)...
| {{model.name}} | {{model.vehicleSizes}} | {{model.vehicleStyles}} |