Closed ikr closed 6 years ago
There are time zone specific tests in the test suite. So you are running them in a zone that happens to have some suites empty.
An Empty suite is better than a failing test for something that won't success in your time zone in my opinion.
Next time I am in the code base I will see if i can remove the suite entirely if it has no tests so it won't fail.
Id like to have some way to automate it running the suite in each time zone in some specified list but it is a fairly complex thing to setup believe and is not a high priority for me.
Alright, I see. Thanks for your answer! Here's the initial problem that made me run the tests https://github.com/rluiten/elm-date-extra/pull/62
Had a simple idea to address at least those empty test suites you referenced I have addressed them now. Just pushed 9.2.2.
Running tests with elm-test (installed with
npm -g
) 0.18.12 results inLooks like tests are conditionally included. When the condition isn't met, a stub tests-set gets registered for execution. Those stubs make elm-test unhappy, it seems.
It all started for me with finding a problem with Duration.diff, and wanting to write a reproducing test. However I failed in making the tests run.