Unit testing Spark transformations in Apache Spark

Introduction

Unit testing Spark transformations helps you check if your data changes work correctly before running big jobs. It saves time and avoids mistakes.

When you want to check if a data filter keeps only the right rows.

When you want to verify that a new column is calculated correctly.

When you want to make sure joining two datasets works as expected.

When you want to test your data cleaning steps on small samples.

When you want to catch errors early in your Spark code.

Syntax

Apache Spark

def test_transformation(spark):
    input_df = spark.createDataFrame([...], schema)
    result_df = your_transformation_function(input_df)
    expected_df = spark.createDataFrame([...], schema)
    assert result_df.collect() == expected_df.collect()

Use small sample data to keep tests fast.

Compare results using collect() or DataFrame equality helpers.

Examples

This test checks if filtering rows with id > 1 works correctly.

Apache Spark

def test_filter(spark):
    data = [(1, 'a'), (2, 'b'), (3, 'c')]
    df = spark.createDataFrame(data, ['id', 'value'])
    filtered = df.filter(df.id > 1)
    expected = spark.createDataFrame([(2, 'b'), (3, 'c')], ['id', 'value'])
    assert filtered.collect() == expected.collect()

This test checks if a new column 'double' is correctly added by multiplying 'num' by 2.

Apache Spark

def test_add_column(spark):
    data = [(1,), (2,), (3,)]
    df = spark.createDataFrame(data, ['num'])
    result = df.withColumn('double', df.num * 2)
    expected = spark.createDataFrame([(1, 2), (2, 4), (3, 6)], ['num', 'double'])
    assert result.collect() == expected.collect()

Sample Program

This program creates a small DataFrame, applies a transformation to uppercase a column, and checks if the result matches the expected DataFrame. It prints 'Test passed!' if the test succeeds.

Apache Spark

from pyspark.sql import SparkSession
from pyspark.sql.functions import upper

def test_uppercase_column():
    spark = SparkSession.builder.master('local').appName('UnitTest').getOrCreate()
    data = [('alice',), ('bob',), ('carol',)]
    df = spark.createDataFrame(data, ['name'])
    # Transformation: make names uppercase
    result = df.withColumn('name_upper', upper(df.name))
    expected_data = [('alice', 'ALICE'), ('bob', 'BOB'), ('carol', 'CAROL')]
    expected = spark.createDataFrame(expected_data, ['name', 'name_upper'])
    assert result.collect() == expected.collect()
    print('Test passed!')
    spark.stop()

if __name__ == '__main__':
    test_uppercase_column()

Important Notes

Use SparkSession with master='local' for fast local testing.

Comparing DataFrames with collect() works for small data only.

For bigger tests, consider using testing libraries like 'pytest' and Spark testing utilities.

Summary

Unit tests check small parts of your Spark code to catch errors early.

Use small sample data and compare actual vs expected results.

Run tests often to keep your data transformations correct.

Practice

1. What is the main purpose of unit testing Spark transformations?

easy

A. To check small parts of Spark code for errors early

B. To improve the speed of Spark jobs

C. To deploy Spark applications automatically

D. To visualize Spark data outputs

Solution

1. Step 1: Understand unit testing purpose

   Unit testing focuses on checking small parts of code to find errors early.

2. Step 2: Relate to Spark transformations

   Testing Spark transformations means verifying each step works correctly before full runs.

3. Final Answer:

   To check small parts of Spark code for errors early -> Option A

4. Quick Check:

   Unit testing = Early error detection [OK]

Hint: Unit tests catch errors early in small code parts [OK]

Common Mistakes:

• Confusing unit testing with performance tuning
• Thinking unit tests deploy code
• Assuming unit tests create visualizations

2. Which of the following is the correct way to compare actual and expected DataFrames in a Spark unit test?

easy

A. print(actual_df) == print(expected_df)

B. assert actual_df.collect() == expected_df.collect()

C. actual_df.show() == expected_df.show()

D. actual_df.count() != expected_df.count()

Solution

1. Step 1: Understand DataFrame comparison

   Comparing DataFrames requires checking their collected data, not just printing or counts.

2. Step 2: Identify correct assertion

   Using assert with collected rows compares actual data content correctly.

3. Final Answer:

   assert actual_df.collect() == expected_df.collect() -> Option B

4. Quick Check:

   Compare collected data for equality [OK]

Hint: Use collect() to compare DataFrame contents in tests [OK]

Common Mistakes:

• Comparing printed output instead of data
• Using show() which returns None
• Comparing only row counts without data

3. Given the following Spark code in a unit test:

input_df = spark.createDataFrame([(1, 'a'), (2, 'b')], ['id', 'value'])
transformed_df = input_df.filter("id > 1")
result = transformed_df.collect()

What is the value of result?

medium

A. [Row(id=1, value='a')]

B. []

C. [Row(id=1, value='a'), Row(id=2, value='b')]

D. [Row(id=2, value='b')]

Solution

1. Step 1: Understand the filter condition

   The filter "id > 1" keeps rows where id is greater than 1, so only id=2 remains.

2. Step 2: Collect the filtered rows

   Collect returns a list of Row objects matching the filter, here only one row with id=2 and value='b'.

3. Final Answer:

   [Row(id=2, value='b')] -> Option D

4. Quick Check:

   Filter id > 1 keeps only id=2 [OK]

Hint: Filter keeps rows matching condition before collect [OK]

Common Mistakes:

• Including rows with id=1 mistakenly
• Confusing collect output format
• Assuming filter excludes id=2

4. You wrote this unit test code:

expected_df = spark.createDataFrame([(1, 'x')], ['id', 'value'])
actual_df = spark.createDataFrame([(1, 'x')], ['id', 'value'])
assert expected_df == actual_df

Why does this test fail?

medium

A. DataFrames cannot be compared directly with '=='

B. The schemas of DataFrames are different

C. The data in DataFrames is different

D. Spark session is not initialized

Solution

1. Step 1: Understand DataFrame equality

   Spark DataFrames do not support direct '==' comparison; it checks object identity, not content.

2. Step 2: Correct way to compare DataFrames

   Use methods like collect() or exceptAll() to compare data content, not '=='.

3. Final Answer:

   DataFrames cannot be compared directly with '==' -> Option A

4. Quick Check:

   Use collect() for DataFrame equality, not '==' [OK]

Hint: Never use '==' to compare DataFrames directly [OK]

Common Mistakes:

• Assuming '==' compares data content
• Ignoring schema differences
• Forgetting to initialize Spark session

5. You want to unit test a Spark transformation that removes duplicate rows based on the 'id' column, keeping the first occurrence. Which approach correctly tests this transformation?

hard

A. Create input DataFrame without duplicates, apply transformation, assert output equals input

B. Create input DataFrame with duplicates, apply transformation, assert output count equals input count

C. Create input DataFrame with duplicates, apply transformation, assert output equals expected DataFrame without duplicates

D. Create input DataFrame with duplicates, apply transformation, assert output is empty

Solution

1. Step 1: Prepare input with duplicates

   To test duplicate removal, input must contain duplicate rows on 'id'.

2. Step 2: Apply transformation and compare output

   After transformation, output should have duplicates removed; compare with expected DataFrame without duplicates.

3. Final Answer:

   Create input DataFrame with duplicates, apply transformation, assert output equals expected DataFrame without duplicates -> Option C

4. Quick Check:

   Test removes duplicates by comparing expected output [OK]

Hint: Test duplicate removal by comparing to expected no-duplicate DataFrame [OK]

Common Mistakes:

• Testing with no duplicates in input
• Comparing only row counts, not content
• Expecting empty output after removal