Unit testing Spark transformations in Apache Spark - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of unit testing Spark transformations?

The main goal is to verify that each transformation on Spark DataFrames or RDDs produces the expected output for given input data, ensuring correctness before running on large datasets.

beginner

Why do we use small sample data in unit tests for Spark transformations?

Using small sample data makes tests fast and easy to understand. It helps quickly check if the transformation logic works without processing large datasets.

intermediate

Which Spark feature helps to compare expected and actual DataFrames in unit tests?

The 'collect()' method gathers data to the driver as a list, which can be compared with expected results. Also, libraries like 'assertDataFrameEqual' help compare DataFrames ignoring order.

intermediate

How do you isolate a Spark transformation for unit testing?

You write the transformation as a pure function that takes a DataFrame as input and returns a transformed DataFrame. This way, you can test it independently from the rest of the pipeline.

beginner

What is a common tool or framework used for unit testing Spark code in Python?

Pytest is commonly used for unit testing Spark code in Python. It allows writing simple test functions and integrates well with Spark testing utilities.

What should a unit test for a Spark transformation focus on?

A Testing Spark cluster performance

B Checking the output for a small, known input

C Running the transformation on the full production dataset

D Verifying Spark version compatibility

Unit tests focus on verifying correctness with small, controlled inputs, not on performance or full dataset runs.

Which method is commonly used to bring Spark DataFrame data to the driver for comparison in tests?

A write()

B show()

C collect()

D cache()

The collect() method returns all rows as a list to the driver, useful for comparing test results.

Why is it important to write Spark transformations as pure functions for testing?

A To isolate logic and make testing easier

B To improve Spark cluster speed

C To reduce memory usage

D To enable caching

Pure functions have no side effects and depend only on inputs, making them easier to test independently.

Which Python testing framework is popular for Spark unit tests?

A Pytest

B JUnit

C Mocha

D RSpec

Pytest is widely used in Python for writing simple and effective unit tests, including for Spark.

What is a good practice when creating test data for Spark transformation tests?

A Avoid creating test data

B Use random large datasets

C Use production data directly

D Use small, simple datasets with known values

Small, simple datasets help quickly verify transformation logic and make tests clear and fast.

Explain how you would write a unit test for a Spark DataFrame transformation.

Think about input, transformation, output, and verification steps.

Why is it important to isolate Spark transformations as pure functions for unit testing?

Consider how pure functions behave and why that helps testing.

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