Welcome to your second lesson in this course dedicated to practicing Test Driven Development (TDD) utilizing Ruby and RSpec. In this unit, we will continue adding features to our calculate_discount function. We have five more requirements for you to implement!

In this course, the emphasis is placed on hands-on practice, where you'll receive requirements through tests, one at a time. Your objective is to implement code that makes each test pass, simulating a real-world TDD environment. As the course guide, it's akin to being your pair programmer, providing test-driven prompts to hone your skills as you progress.

As a reminder, the Red-Green-Refactor cycle is central to TDD, guiding your development process:

• Red: Start by writing a failing test to define the next step.
• Green: Implement just enough code to pass the test, focusing on functionality.
• Refactor: Optimize the code for clarity and efficiency without changing its behavior.

In this section, you will enhance the calculate_discount function by implementing five additional requirements:

1. Non-Numeric Price Input Handling: Learn how to validate inputs and handle errors for non-numeric price values.

2. Non-Numeric Discount Input Handling: Understand how to ensure discount inputs are numeric and manage invalid cases effectively.

3. Handling Very Small Prices: Discover techniques to manage very small prices and ensure they adhere to a defined minimum value post-discount.

4. Minimum Discount Percentage Application: Implement logic to apply a minimum discount percentage when provided with a lower percentage.

5. Capping Maximum Discount Amount: Explore methods for capping the discount at a maximum dollar value, ensuring the discount does not exceed this cap.

Below is the calculate_discount function that you will enhance by implementing five additional requirements:

• Description: The function should validate that the price is a numeric value and raise an error if a non-numeric input is provided.
• Test Case:

• Description: The function should validate that the discount percentage is a numeric value and raise an error if a non-numeric input is provided.
• Test Case:

• Description: The function should ensure that very small prices do not fall below a defined minimum value after discounts are applied.
• Test Case:

• Description: The function should apply a minimum discount percentage of 1% if a lower percentage is provided.
• Test Case:

• Description: The function should cap the discount at a maximum dollar value of $500, even if the calculated discount would exceed that cap.
• Test Case:

Here is the complete calculate_discount function after implementing all the requirements:

In this section, you explored testing advanced requirements for the calculate_discount function. These included handling invalid, non-numeric inputs; managing very small prices to ensure minimum price thresholds are met; and applying specific discount constraints, such as enforcing a minimum discount percentage and capping the maximum allowable discount amount.

As you proceed with the practice exercises, keep the Red-Green-Refactor cycle in mind to guide your process. In this unit:

• Each test prompts you to refine the function's robustness, beginning with the Red phase by writing tests for additional edge cases.
• In the Green phase, aim to pass each test by incrementally adding necessary logic, such as input validation and boundary enforcement.
• The Refactor phase offers the chance to simplify and optimize your code after passing all tests, ensuring that it is not only correct but also clear and maintainable.

These exercises deepen your TDD skills by applying practical constraints and validations, simulating real-world requirements where robustness and reliability are essential.