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 equivalence relation:
x
of type Any
,
x.equals(x)
should return true
.x
and y
of type
Any
, x.equals(y)
should return true
if and only
if y.equals(x)
returns true
.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 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.
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.
A
Formatter
that indicates reporters may wish to suppress reporting of anEvent
. "Suppress" means that the event won't be reported to the user.An example is that specification-style suites, such as
Spec
, generate output that reads more like a specification. One aspect of this is that generally only a single event should be reported for each test, so that output can appear like this:ScalaTest suites should generate two events per test, a
TestStarting
event and either aTestSucceeded
or aTestFailed
event. TheSpec
trait does report both events, but passes aMotionToSuppress
along with theTestStarting
event. As a result, TheTestStarting
events have no effect on the output. EachTestSucceeded
orTestFailed
event, which is sent with anIndentedText
formatter instead of aMotionToSuppress
, will generate output, such as "- should be empty
".Reporters may choose to ignore a
MotionToSuppress
. For example, an XML reporter may want to report everything about every event that is fired during a concurrent run, so that the events can be reordered later by reading the complete, but unordered, information from an XML file. In this case, the XML reporter would actually report events that were fired with aMotionToSuppress
, including indicating that the report included a motion to suppress.