What test scenarios are necessary and sufficient for an exhaustive black box that validates a repeating assignment model?

Question

I have a django model for a meeting on a calendar in which I am trying to write a very complete test driver. A repeated appointment occurs at some point in time and can either work endlessly or be repeated a fixed number of times. The appointment reflects the functionality available for the appointment of Google Calendar (can be repeated monthly / yearly / weekly, every two weeks, every 3 years).

I am trying to come up with a unit test that will exhaustively test the basics of this implementation. I am looking for edge cases that will determine the most basic tests.

I have many basic ones, but I'm looking for suggestions that will help identify the most important cases: 1) Create a single meeting 2) Create a meeting that repeats weekly 3) ... repeats monthly 4) repeats every 2 weeks 5) repeats every 2 months 6 ) repeated annually

Answer 1

Experience the last months of the months, leap years, and whether he will go crazy when there is an extra second during the year (this blow will hit the driver in the zune player).

Check that he is behaving well when years cross.

, , -, . , , , .

Answer 2

29 ;)

Answer 3

, .

/ ( ). , ?

.

, . , , ..

, , "" ( ). "" .

- ( ), .

, , . , . - , , .

, , . . . . . , . -? , Exchange ? - , -? .

.