The custom frequency requires a timezone configuration, forcing it
to run in the integration test scope.
Running the integration tests requires a database connection in the
build process. It enables other case tests.
The API Tests cause interference in other tests, requiring isolating
them.
This change reveals a bug in the Monthly calculation date where the
difference between more than one month was discarded. The new calendar
calculator was prepared to avoid overflow at the end of the month.
It encapsulates some date operations like sum. The result will be the
calculated date when calling the nextDateByInterval method, given the
date, periodicity, and skipInterval parameters.
For example, given a date of 2019-12-31, monthly periodicity, and skip
interval 0, the results will be 2020-01-31. Also, if the skip interval
is 1, the result is 2020-02-29. This is because the next date will add
another month to the current range.
All these strategies encapsulate how the Carbon library adds the
interval to the current date.
Monthly, Quarterly, Half-Yearly, and Yearly explicitly use the
overflow control to guarantee the end of the next month or year
adequately.
It is responsible for calculating and manipulating Dates in financial
organization is a very important feature, and requires significant
coverage.
The first test case is just to create an understanding of how it
works.
