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

Can we define custom matchers in ScalaTest?

Can we define custom matchers in ScalaTest?

Is it advisable to define Scala objects by extending the trait containing custom matchers?

Is it advisable to define Scala objects by extending the trait containing custom matchers?

Does ScalaTest define assertions and matchers to write tests involving exceptions?

Does ScalaTest define assertions and matchers to write tests involving exceptions?

Is it advisable to use `Try` to write tests involving exceptions?

Is it advisable to use <code>Try</code> to write tests involving exceptions?

Is it advisable to use `println` to show log messages in a test case?

Is it advisable to use <code>println</code> to show log messages in a test case?

Are messages printed with `Informer#info()` shown right away?

Are messages printed with <code>Informer#info()</code> shown right away?

The `info()` method prints the messages at the end of the test, whereas `note()` and `alert()` print them as the test runs.

They behave the same. Messages are logged as info, debug, and warning, respectively.

What's the difference between `info()`, `note()`, and `alert()`?

What’s the difference between <code>info()</code>, <code>note()</code>, and <code>alert()</code>?

Can we have ScalaTest generate coverage reports?

Can we have ScalaTest generate coverage reports?

This is code we have to run before each test case.

This is a value we need in one or more test cases in one or more suites.

This is code we have to run after each test case.

This is code we have to run before and after each test case.

It tells ScalaTest to create a new instance of the test suite for each test case in that suite.

It tells ScalaTest to create a new instance of the test suite for each data fixture in the suite.

What does <code>OneInstancePerTest</code> do?

Yes. The actions will be run before and after each test case.

Yes. The actions will be run before and after each test suite.

Can we use the `BeforeAndAfterEach` trait to perform setup and teardown actions?

Can we use the <code>BeforeAndAfterEach</code> trait to perform setup and teardown actions?

Does ScalaTest define style traits with facilities for using fixtures?

Does ScalaTest define style traits with facilities for using fixtures?

Quiz: ScalaTest Proficiency

Quiz: ScalaTest Proficiency

Take a quiz to assess your understanding of some more advanced use cases in ScalaTest.

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 Proficiency