WEBVTT

00:04.240 --> 00:08.680
Now that we have covered data quality tests, we can move on to the functional testing.

00:08.880 --> 00:13.800
This is a common practice in software engineering, and even data engineers should apply some level

00:13.800 --> 00:16.040
of functional testing to their code.

00:16.080 --> 00:21.720
We will focus on three primary tests, which are unit integration and end to end testing.

00:21.720 --> 00:26.800
In order to run these tests, we will use the unit test library, which already comes with the Python

00:26.800 --> 00:30.480
installation, and also the Pytest framework for Pytest.

00:30.480 --> 00:35.200
Since it doesn't come in the default packages of airflow, we have already added it to requirements.txt

00:35.240 --> 00:36.560
file as you see here.

00:36.560 --> 00:38.640
So it is part of the base docker image.

00:38.640 --> 00:43.800
To confirm this, let's first make sure that your Docker containers are running by running the docker

00:43.800 --> 00:44.600
PS command.

00:45.240 --> 00:50.360
And then we go inside one of the airflow containers, let's say the airflow worker.

00:51.200 --> 00:53.760
So we run docker exec -18.

00:56.360 --> 01:02.120
And then we run the pip show by test to see if it is actually installed in our base image.

01:04.000 --> 01:04.800
And there you have it.

01:04.840 --> 01:05.640
We got an output.

01:05.640 --> 01:11.400
So that means that Pytest is a part of our base Docker image package installations.

01:11.680 --> 01:16.240
Now that we have all that we need to start testing in the next lectures, we will go over each of the

01:16.240 --> 01:22.320
three functional tests explaining what they consist of and how to implement them in our code base.