popy-dev / popy-calendar Goto Github PK

When initially making the tests you'll notice I only check the date component. For some reason, the time on the machine running is injected to the DateTime / DateTimeImmutable. That seems to violate the principle of least surprise to me.

• ensure when creating date from year only that month, day, hour, minute, second, microsecond are a configured value
  • minimum value
  • maximum value
  • system value (current behaviour)
  • specified value
• ensure when creating date from year & month only that day, hour, minute, second, microsecond are a configured value
  • minimum value
  • maximum value
  • system value (current behaviour)
  • specified value
• ensure when creating date from year, month & day only that hour, minute, second, microsecond are a configured value
  • minimum value
  • maximum value
  • system value (current behaviour)
  • specified value
• ensure when creating date from year, month, day & hour only that minute, second, microsecond are a configured value
  • minimum value
  • maximum value
  • system value (current behaviour)
  • specified value
• ensure when creating date from year, month, day, hour & minute only that second & microsecond are a configured value
  • minimum value
  • maximum value
  • system value (current behaviour)
  • specified value
• ensure when creating date from year, month, day, hour, minute & second only that microsecond are a configured value
  • minimum value
  • maximum value
  • system value (current behaviour)
  • specified value

Pretty sure this is an epic 😆

Now you have tests you can get them to run automatically on commit using a tool like travis-ci. This will mean when people submit PR's you can know ahead of time if they break the software.

Looks like with all the changes packagist hasn't been bumped so nobody can use the changes, the license isn't present.

convert the examples & samples from docs into tests