Gain insights into effective unit and integration testing in Scala. Learn about ScalaTest, Mockito, ScalaCheck, and Docker/TestContainers to enhance testing quality and maintainability.

Effective Unit and Integration Testing in Scala.png

dockerfile.tar.gz

TestOnly matchers.EducativeSpec

TestOnly styles.FunSuite

TestOnly styles.FlatSpec

TestOnly styles.FunSpec

TestOnly styles.WordSpec

TestOnly styles.FreeSpec

TestOnly styles.PropSpec

TestOnly styles.FeatureSpec

TestOnly styles.RefSpec

TestOnly assertions.CourseSpec

TestOnly assertions.EducativeSpec

TestOnly matchers.CourseSpec

TestOnly assertions.AuthorSpec

TestOnly info.EducativeSpec

TestOnly matchers.AuthorSpec

TestOnly matchers.CompilationSpec

TestOnly assertions.CompilationSpec

TestOnly fixtures.EducativeSpec

TestOnly futures.SimpleCourseRepositorySpec

TestOnly fixtures.MutableEducativeSpec

TestOnly futures.SimpleCourseRepositoryAsyncSpec

TestOnly futures.SimpleCourseRepositoryEventualSpec

TestOnly mocks.StateVerification

TestOnly mocks.BehaviorVerification

TestOnly mocks.MockitoTrait

TestOnly mocks.MockitoClass

TestOnly mocks.PurchaseServiceTrait

TestOnly mocks.PurchaseServiceClass

TestOnly properties.CoursePriceSpec

TestOnly properties.MutableEducativeSpec

TestOnly properties.FreeCoursePriceSpec

TestOnly properties.CoursePriceSuiteSpec

TestOnly repository.S3ArtifactRepositorySpec

TestOnly repository.S3ArtifactRepositoryDockerComposeSpec

TestOnly properties.MutableEducativeGenSpec

TestOnly matchers.EducativeSpec-copy-testmarvah

Educative_test

TestOnly styles.FunSuite-copy

Testing is a fundamental part of writing software. Tests should be written with as much care as we put into designing and coding our applications. Still, writing clean and well-organized test cases can be difficult. In many cases, their quality is lower than that of the rest of the application. This can seriously impact the overall quality and maintainability of the project in the long run.

The focus of this course is on unit and integration tests in Scala. First, you’ll learn about the most famous testing framework for Scala—ScalaTest. Then, you’ll move to mocking and property-based testing with Mockito and ScalaCheck. Finally, the course will focus on integration testing, showing how to mock the dependencies on external services with Docker and TestContainers.

After taking this course, you’ll have a more comprehensive view of the possibilities to run different tests in Scala, including practical knowledge of some widespread testing libraries.

Effective Unit and Integration Testing in Scala

Which of the following statements is *true*?

1. ScalaTest provides built-in ways to help us test a Scala `Future`.
2. ScalaTest's async test suites block, waiting for a `Future` to complete.


Which of the following statements is true?
<ol>
<li>ScalaTest provides built-in ways to help us test a Scala <code>Future</code>.</li>
<li>ScalaTest’s async test suites block, waiting for a <code>Future</code> to complete.</li>
</ol>

We don't. Scala doesn't have any way to wait for a `Future` to complete.

How do we block, waiting for a `Future` to complete in Scala?

How do we block, waiting for a <code>Future</code> to complete in Scala?

Can we use the fixture-context object pattern with async test suites?

Can we use the fixture-context object pattern with async test suites?

The test cases of the suite are run in parallel, each one with its own instance of the test suite.

All test suites mixing in `ParallelTestExecution` are run in parallel.

The test cases of the suite are run in parallel, and they use the same instance of the test suite class.

What effect does mixing in `ParallelTestExecution` have?

What effect does mixing in <code>ParallelTestExecution</code> have?

Which of the following statements, if any, are *true*?

1. `FutureConcept` lets us retrieve the result of the `Future` under test.
2. Eventually-consistent systems can be tested in ScalaTest.


Which of the following statements, if any, are true?
<ol>
<li><code>FutureConcept</code> lets us retrieve the result of the <code>Future</code> under test.</li>
<li>Eventually-consistent systems can be tested in ScalaTest.</li>
</ol>

What type of consistency is more suitable for systems where data integrity and accuracy are must-haves?

What type of consistency is more suitable for systems where data integrity and accuracy are must-haves?

Can we use ScalaTest to make assertions on the value of the private properties of a class?

Can we use ScalaTest to make assertions on the value of the private properties of a class?

Does ScalaTest let us tag our tests?

Which of the following statements, if any, are *true*?

1. ScalaTest provides syntactic sugar to access the value wrapped by an `Option`.
2. ScalaTest provides syntactic sugar to make assertions on the value wrapped by a `Try`.

Which of the following statements, if any, are true?
<ol>
<li>ScalaTest provides syntactic sugar to access the value wrapped by an <code>Option</code>.</li>
<li>ScalaTest provides syntactic sugar to make assertions on the value wrapped by a <code>Try</code>.</li>
</ol>

Can we use Scala annotations to tag tests in ScalaTest?

Can we use Scala annotations to tag tests in ScalaTest?

Quiz: ScalaTest Advanced

Quiz: ScalaTest Advanced

Take a quiz to assess your understanding of the advanced features of ScalaTest, including asynchronous testing and tagging.

Introduction

Brief Introduction to Scala and sbt

Writing Tests with ScalaTest

Quiz: ScalaTest

Mocking with ScalaMock

Quiz: Mocking

Property-Based Testing with ScalaCheck

Quiz: Property-Based Testing

Mocking External Services with TestContainers-scala

Conclusion

Quiz: ScalaTest Advanced