minitest
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>rubygems</groupId>
<artifactId>minitest</artifactId>
<version>5.4.1</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<modelVersion>4.0.0</modelVersion>
<groupId>rubygems</groupId>
<artifactId>minitest</artifactId>
<version>5.4.1</version>
<packaging>gem</packaging>
<name>minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking</name>
<description>minitest provides a complete suite of testing facilities supporting
TDD, BDD, mocking, and benchmarking.
"I had a class with Jim Weirich on testing last week and we were
allowed to choose our testing frameworks. Kirk Haines and I were
paired up and we cracked open the code for a few test
frameworks...
I MUST say that minitest is *very* readable / understandable
compared to the 'other two' options we looked at. Nicely done and
thank you for helping us keep our mental sanity."
-- Wayne E. Seguin
minitest/unit is a small and incredibly fast unit testing framework.
It provides a rich set of assertions to make your tests clean and
readable.
minitest/spec is a functionally complete spec engine. It hooks onto
minitest/unit and seamlessly bridges test assertions over to spec
expectations.
minitest/benchmark is an awesome way to assert the performance of your
algorithms in a repeatable manner. Now you can assert that your newb
co-worker doesn't replace your linear algorithm with an exponential
one!
minitest/mock by Steven Baker, is a beautifully tiny mock (and stub)
object framework.
minitest/pride shows pride in testing and adds coloring to your test
output. I guess it is an example of how to write IO pipes too. :P
minitest/unit is meant to have a clean implementation for language
implementors that need a minimal set of methods to bootstrap a working
test suite. For example, there is no magic involved for test-case
discovery.
"Again, I can't praise enough the idea of a testing/specing
framework that I can actually read in full in one sitting!"
-- Piotr Szotkowski
Comparing to rspec:
rspec is a testing DSL. minitest is ruby.
-- Adam Hawkins, "Bow Before MiniTest"
minitest doesn't reinvent anything that ruby already provides, like:
classes, modules, inheritance, methods. This means you only have to
learn ruby to use minitest and all of your regular OO practices like
extract-method refactorings still apply.</description>
<url>https://github.com/seattlerb/minitest</url>
<licenses>
<license>
<name>MIT</name>
<url>http://opensource.org/licenses/MIT</url>
<comments>MIT license</comments>
</license>
</licenses>
<developers>
<developer>
<name>Ryan Davis</name>
<email>ryand-ruby@zenspider.com</email>
</developer>
</developers>
<scm>
<connection>https://github.com/seattlerb/minitest.git</connection>
<url>https://github.com/seattlerb/minitest</url>
</scm>
<properties>
<jruby.plugins.version>1.0.8</jruby.plugins.version>
</properties>
<dependencies>
<dependency>
<groupId>rubygems</groupId>
<artifactId>rdoc</artifactId>
<version>[4.0,4.99999]</version>
<type>gem</type>
<scope>test</scope>
</dependency>
<dependency>
<groupId>rubygems</groupId>
<artifactId>hoe</artifactId>
<version>[3.12,3.99999]</version>
<type>gem</type>
<scope>test</scope>
</dependency>
</dependencies>
<repositories>
<repository>
<id>rubygems-releases</id>
<url>http://rubygems-proxy.torquebox.org/releases</url>
</repository>
</repositories>
<build>
<extensions>
<extension>
<groupId>de.saumya.mojo</groupId>
<artifactId>gem-extension</artifactId>
<version>${jruby.plugins.version}</version>
</extension>
</extensions>
<directory>${basedir}/pkg</directory>
<plugins>
<plugin>
<groupId>de.saumya.mojo</groupId>
<artifactId>gem-maven-plugin</artifactId>
<version>${jruby.plugins.version}</version>
<configuration>
<gemspec>minitest-5.4.1.gemspec</gemspec>
</configuration>
</plugin>
</plugins>
</build>
</project>