o != arg0 is the same as !(o == (arg0)).
o != arg0 is the same as !(o == (arg0)).
the object to compare against this object for dis-equality.
false if the receiver object is equivalent to the argument; true otherwise.
o == arg0 is the same as if (o eq null) arg0 eq null else o.equals(arg0).
o == arg0 is the same as if (o eq null) arg0 eq null else o.equals(arg0).
the object to compare against this object for equality.
true if the receiver object is equivalent to the argument; false otherwise.
o == arg0 is the same as o.equals(arg0).
o == arg0 is the same as o.equals(arg0).
the object to compare against this object for equality.
true if the receiver object is equivalent to the argument; false otherwise.
This method is used to cast the receiver object to be of type T0.
This method is used to cast the receiver object to be of type T0.
Note that the success of a cast at runtime is modulo Scala's erasure semantics. Therefore the expression1.asInstanceOf[String] will throw a ClassCastException at runtime, while the expressionList(1).asInstanceOf[List[String]] will not. In the latter example, because the type argument is erased as
part of compilation it is not possible to check whether the contents of the list are of the requested typed.
the receiver object.
This method creates and returns a copy of the receiver object.
This method creates and returns a copy of the receiver object.
The default implementation of the clone method is platform dependent.
a copy of the receiver object.
A Shell whose run method will pass true for execute's colorparameter, and pass for all other parameters the same values as this Shell.
A Shell whose run method will pass true for execute's colorparameter, and pass for all other parameters the same values as this Shell.
A Shell whose run method will pass true for execute's durationsparameter, and pass for all other parameters the same values as this Shell.
A Shell whose run method will pass true for execute's durationsparameter, and pass for all other parameters the same values as this Shell.
This method is used to test whether the argument (arg0) is a reference to the
receiver object (this).
This method is used to test whether the argument (arg0) is a reference to the
receiver object (this).
The eq method implements an [http://en.wikipedia.org/wiki/Equivalence_relation equivalence relation] on
non-null instances of AnyRef:
* It is reflexive: for any non-null instance x of type AnyRef, x.eq(x) returns true.
* It is symmetric: for any non-null instances x and y of type AnyRef, x.eq(y) returns true if and
only if y.eq(x) returns true.
* It is transitive: for any non-null instances x, y, and z of type AnyRef if x.eq(y) returns true and y.eq(z) returns true, then x.eq(z) returns true.
Additionally, the eq method has three other properties.
* It is consistent: for any non-null instances x and y of type AnyRef, multiple invocations of
x.eq(y) consistently returns true or consistently returns false.
* For any non-null instance x of type AnyRef, x.eq(null) and null.eq(x) returns false.
* null.eq(null) returns true.
When overriding the equals or hashCode methods, it is important to ensure that their behavior is
consistent with reference equality. Therefore, if two objects are references to each other (o1 eq o2), they
should be equal to each other (o1 == o2) and they should hash to the same value (o1.hashCode == o2.hashCode).
the object to compare against this object for reference equality.
true if the argument is a reference to the receiver object; false otherwise.
This method is used to compare the receiver object (this) with the argument object (arg0) for equivalence.
This method is used to compare the receiver object (this) with the argument object (arg0) for equivalence.
The default implementations of this method is an [http://en.wikipedia.org/wiki/Equivalence_relation equivalence
relation]:
* It is reflexive: for any instance x of type Any, x.equals(x) should return true.
* It is symmetric: for any instances x and y of type Any, x.equals(y) should return true if and
only if y.equals(x) returns true.
* It is transitive: for any instances x, y, and z of type AnyRef if x.equals(y) returns true and
y.equals(z) returns true, then x.equals(z) should return true.
If you override this method, you should verify that your implementation remains an equivalence relation.
Additionally, when overriding this method it is often necessary to override hashCode to ensure that objects
that are "equal" (o1.equals(o2) returns true) hash to the same
scala.Int
(o1.hashCode.equals(o2.hashCode)).
the object to compare against this object for equality.
true if the receiver object is equivalent to the argument; false otherwise.
This method is called by the garbage collector on the receiver object when garbage collection determines that there are no more references to the object.
This method is called by the garbage collector on the receiver object when garbage collection determines that there are no more references to the object.
The details of when and if the finalize method are invoked, as well as the interaction between finalizeand non-local returns and exceptions, are all platform dependent.
A Shell whose run method will pass false for execute's shortstacksparameter and true for its fullstacks parameter, and pass for all other parameters the same values as this Shell.
A Shell whose run method will pass false for execute's shortstacksparameter and true for its fullstacks parameter, and pass for all other parameters the same values as this Shell.
Returns a representation that corresponds to the dynamic class of the receiver object.
Returns a representation that corresponds to the dynamic class of the receiver object.
The nature of the representation is platform dependent.
a representation that corresponds to the dynamic class of the receiver object.
Returns a hash code value for the object.
Returns a hash code value for the object.
The default hashing algorithm is platform dependent.
Note that it is allowed for two objects to have identical hash codes (o1.hashCode.equals(o2.hashCode)) yet
not be equal (o1.equals(o2) returns false). A degenerate implementation could always return 0.
However, it is required that if two objects are equal (o1.equals(o2) returns true) that they have
identical hash codes (o1.hashCode.equals(o2.hashCode)). Therefore, when overriding this method, be sure
to verify that the behavior is consistent with the equals method.
the hash code value for the object.
This method is used to test whether the dynamic type of the receiver object is T0.
This method is used to test whether the dynamic type of the receiver object is T0.
Note that the test result of the test is modulo Scala's erasure semantics. Therefore the expression1.isInstanceOf[String] will return false, while the expression List(1).isInstanceOf[List[String]] will
return true. In the latter example, because the type argument is erased as part of compilation it is not
possible to check whether the contents of the list are of the requested typed.
true if the receiver object is an instance of erasure of type T0; false otherwise.
o.ne(arg0) is the same as !(o.eq(arg0)).
o.ne(arg0) is the same as !(o.eq(arg0)).
the object to compare against this object for reference dis-equality.
false if the argument is not a reference to the receiver object; true otherwise.
Returns a copy of this Shell with colorPassed configuration parameter set to false.
Returns a copy of this Shell with colorPassed configuration parameter set to false.
Returns a copy of this Shell with durationsPassed configuration parameter set to false.
Returns a copy of this Shell with durationsPassed configuration parameter set to false.
Returns a copy of this Shell with shortStacksPassed configuration parameter set to false.
Returns a copy of this Shell with shortStacksPassed configuration parameter set to false.
Returns a copy of this Shell with statsPassed configuration parameter set to false.
Returns a copy of this Shell with statsPassed configuration parameter set to false.
Wakes up a single thread that is waiting on the receiver object's monitor.
Wakes up a single thread that is waiting on the receiver object's monitor.
Wakes up all threads that are waiting on the receiver object's monitor.
Wakes up all threads that are waiting on the receiver object's monitor.
Run the passed suite, optionally passing in a test name and config map.
Run the passed suite, optionally passing in a test name and config map.
This method will invoke execute on the passed suite, passing in
the specified (or default) testName and configMap and a set of configuration values. A
particular Shell instance will always pass the same configuration values (color,durations, shortstacks, fullstacks, and stats) to execute each time
this method is invoked.
A Shell whose run method will pass true for execute's shortstacksparameter and false for its fullstacks parameter, and pass for all other parameters the same values as
this Shell.
A Shell whose run method will pass true for execute's shortstacksparameter and false for its fullstacks parameter, and pass for all other parameters the same values as
this Shell.
A Shell whose run method will pass true for execute's statsparameter, and pass for all other parameters the same values as this Shell.
A Shell whose run method will pass true for execute's statsparameter, and pass for all other parameters the same values as this Shell.
Returns a string representation of the object.
Returns a string representation of the object.
The default representation is platform dependent.
a string representation of the object.
Trait whose instances provide a
runmethod and configuration fields that implement the ScalaTest shell: its DSL for the Scala interpreter.The main command of the ScalaTest shell is
run, which you can use to run a suite of tests. The shell also provides several commands for configuring a call torun:color(the default) - display results in color (green for success; red for failure; yellow for warning; blue for statistics)nocolor- display results without colordurations- display durations of (i.e., how long it took to run) tests and suitesnodurations(the default) - do not display durations of tests and suitesshortstacks- display short (i.e., truncated to show just the most useful portion) stack traces for all exceptionsfullstacks- display full stack trackes for all exceptionsnostacks(the default) - display no stack trace forStackDepthexceptions and a short stack trace for non-StackDepthexceptionsstats- display statistics before and after the run, such as expected test count before the run and tests succeeded, failed, pending,etc., counts after the runnostats(the default) not display statistics before or after the runThe default configuration is
color,nodurations,nostacks, andnostats.All of these commands are fields of trait
org.scalatest.Shell. Each configuration command is a field that refers to anotherShellinstance with every configuration parameter the same except for the one you've asked to change. For example,durationsprovides aShellinstance that has every parameter configured the same way, except with durations enabled. When you invokerunon that, you will get a run with durations enabled and every other configuration parameter at its default value.Two other useful "commands" to know about, though not technically part of the shell, are the
applyfactory methods in theSuitesandSpecssingleton objects. These allow you to easily create composite suites out of nested suites, which you can then pass torun. This will be demonstrated later in this documentation.Using the ScalaTest shell
The package object of the
org.scalatestpackage, although it does not extendShell, declares all the same members asShell. Itsrunmethod runs with all theShellconfiguration parameters set to their default values. A good way to use the ScalaTest shell, therefore, is to import the members of packageorg.scalatest:scala> import org.scalatest._ import org.scalatest._One thing importing
org.scalatest._allows you to do is access any of ScalaTest's classes and traits by shorter names, for example:scala> class ArithmeticSuite extends FunSuite with matchers.ShouldMatchers { | test("addition works") { | 1 + 1 should equal (2) | } | ignore("subtraction works") { | 1 - 1 should equal (0) | } | test("multiplication works") { | 1 * 1 should equal (2) | } | test("division works") (pending) | } defined class ArithmeticSuiteBut importing
org.scalatest._also brings into scope the commands of theShell, so you can, for example, invokerunwithout qualification:Configuring a single run
To configure a single run, you can prefix run by one or more configuration commands, separated by dots. For example, to enable durations during a single run, you would write:
To enable statistics during a single run, you would write:
And to enable both durations and statistics during a single run, you could write:
The order doesn't matter when you are chaining multiple configuration commands. You'll get the same result whether you write
durations.stats.runorstats.durations.run.To disable color, use
nocolor:scala> nocolor.run(new ArithmeticSuite) ArithmeticSuite: - addition works - subtraction works !!! IGNORED !!! - multiplication works *** FAILED *** 1 did not equal 2 (<console>:16) - division works (pending)To enable short stack traces during a single run, use
shortstacks:Changing the default configuration
If you want to change the default for multiple runs, you can import the members of your favorite
Shellconfiguration. For example, if you always like to run with durations and statistics enabled, you could write:scala> import stats.durations._ import stats.durations._Now anytime you run statistics and durations will, by default, be enabled:
Running multiple suites
If you want to run multiple suites, you can use the factory methods in either the
SuitesorSpecssingleton objects. If you wrap a comma-separated list of suite instances insideSuites(...), for example, you'll get a suite instance that contains no tests, but whose nested suites includes the suite instances you placed between the parentheses. You can placeSuitesinsideSuitesto any level of depth, creating a tree of suites to pass torun. Here's a (contrived) example in whichArithmeticSuiteis executed four times:Running a single test
The
runcommand also allows you to specify the name of a test to run and/or a config map. You can run a particular test in a suite, for example, by specifying the test name after the suite instance in your call torun, like this: