Jest Describe Block Implementation

This challenge focuses on understanding and implementing the describe block in Jest, a crucial component for organizing and structuring your tests. The describe block allows you to group related tests together, providing a clear and logical hierarchy to your test suite, making it easier to understand and maintain. Your task is to create a function that generates a Jest describe block string based on a provided title and an array of test descriptions.

Problem Description

You are tasked with creating a TypeScript function called generateDescribeBlock. This function will take two arguments:

1. title: A string representing the title of the describe block. This title should be used as the first argument to the describe function in the generated Jest code.
2. testDescriptions: An array of strings, where each string represents a single test description within the describe block. Each test description will be used as the first argument to the test function.

The function should return a string containing the complete Jest describe block code, including the describe and test functions. The generated code should be properly formatted and ready to be included in a Jest test file.

Key Requirements:

• The generated code must be valid Jest code.
• The describe block should have the provided title.
• Each test function within the describe block should have the corresponding testDescription from the input array.
• The generated code should be well-formatted for readability.

Expected Behavior:

The function should return a string that, when executed by Jest, will define a describe block with the specified title and tests.

Edge Cases to Consider:

• Empty testDescriptions array: The describe block should still be generated, but without any test functions inside.
• title is an empty string: The describe block should still be generated, but with an empty title.
• Invalid input types (e.g., testDescriptions not being an array of strings): While not strictly required for this challenge, consider how your function might handle such cases (e.g., throwing an error or returning a default value).

Examples

Example 1:

Input: title = "My Component", testDescriptions = ["renders without errors", "displays the correct text"]
Output:

describe('My Component', () => {
  test('renders without errors', () => {
    // Test implementation here
  });

  test('displays the correct text', () => {
    // Test implementation here
  });
});

Explanation: A describe block is created with the title "My Component", and two test functions are added with the provided test descriptions.

Example 2:

Input: title = "", testDescriptions = ["test 1", "test 2", "test 3"]
Output:

describe('', () => {
  test('test 1', () => {
    // Test implementation here
  });

  test('test 2', () => {
    // Test implementation here
  });

  test('test 3', () => {
    // Test implementation here
  });
});

Explanation: A describe block is created with an empty title, and three test functions are added with the provided test descriptions.

Example 3:

Input: title = "My Group", testDescriptions = []
Output:

describe('My Group', () => {
  // No tests in this describe block
});

Explanation: A describe block is created with the title "My Group", but no test functions are added because the testDescriptions array is empty.

Constraints

• The title string should not exceed 255 characters.
• Each testDescription string should not exceed 100 characters.
• The function must be implemented in TypeScript.
• The generated code should be valid Jest code and should not include any unnecessary whitespace.

Notes

• You don't need to implement the actual test logic within the test functions; just generate the Jest code structure.
• Focus on correctly formatting the describe and test functions.
• Consider using template literals for easier string concatenation.
• Think about how to handle edge cases gracefully.