TryValues
Related Docs:
object TryValues
| package scalatest
Wrapper class that adds success and failure methods to scala.util.Try, allowing
you to make statements like:
Wrapper class that adds success and failure methods to scala.util.Try, allowing
you to make statements like:
try1.success.value should be > 9 try2.failure.exception should have message "/ by zero"
Implicit conversion that adds success and failure methods to Try.
Implicit conversion that adds success and failure methods to Try.
the Try to which to add the success and failure methods
Trait that provides an implicit conversion that adds
successandfailuremethods toscala.util.Try, enabling you to make assertions about the value of aSuccessor the exception of aFailure.The
successmethod will return theTryon which it is invoked as aSuccessif theTryactually is aSuccess, or throwTestFailedExceptionif not. Thefailuremethod will return theTryon which it is invoked as aFailureif theTryactually is aFailure, or throwTestFailedExceptionif not.This construct allows you to express in one statement that an
Tryshould be either aSuccessor aFailureand that its value or exception, respectively,should meet some expectation. Here's an example:Or, using assertions instead of a matchers:
Were you to simply invoke
geton theTry, if theTrywasn't aSuccess, it would throw the exception contained in theFailure:The
ArithmeticExceptionwould cause the test to fail, but without providing a stack depth pointing to the failing line of test code. This stack depth, provided byTestFailedException(and a few other ScalaTest exceptions), makes it quicker for users to navigate to the cause of the failure. WithoutTryValues, to get a stack depth exception you would need to make two statements, like this:The
TryValuestrait allows you to state that more concisely: