Fix failing unit tests related to time widget

[LucianBuzzo]

Reasons for making this change

It appears that due to the recent change from 2018 to 2019, there is one additional year in the select list, which caused the unit tests to fail.

Checklist

• I'm updating documentation
  • I've checked the rendering of the Markdown text I've added
  • If I'm adding a new section, I've updated the Table of Content
• I'm adding or updating code
  • I've added and/or updated tests
  • I've updated docs if needed
  • I've run npm run cs-format on my branch to conform my code to prettier coding style
• I'm adding a new feature
  • I've updated the playground with an example use of the feature

[edi9999]

For some reason this failed on travis

[LucianBuzzo]

@edi9999 Strange, I'm going to try and debug it

[edi9999]

One idea of mine is that for some reason new Date().getFullYear() returns 2018.

Can you add a console.log(new Date().getFullYear()) and console.log(new Date()) for this ?

[LucianBuzzo]

@edi9999 The test passes when using .only, and the available options appear to be the same in both cases:

• https://travis-ci.org/mozilla-services/react-jsonschema-form/jobs/476279908#L2190
• https://travis-ci.org/mozilla-services/react-jsonschema-form/jobs/476277009

[LucianBuzzo]

@edi9999 I was being stupid, it was actually another test that was failing -> https://github.com/mozilla-services/react-jsonschema-form/blob/master/test/StringField_test.js#L1007 I'll update it with the same fix

[edi9999]

Thanks @LucianBuzzo !

[cyplo]

A nitpick - but would it make sense to extract a function that provides this, to avoid duplication between tests ?

[edi9999]

That is imo not really necessary, in tests duplication is not so bad.