/how-to-mock-and-unit-test-moment-js/ Always be learning Sat, 08 Sep 2018 00:57:00 +0000 hourly 1 https://wordpress.org/?v=6.1.1 /how-to-mock-and-unit-test-moment-js/#comment-27 Sat, 08 Sep 2018 00:57:00 +0000 http://ec2-52-36-187-147.us-west-2.compute.amazonaws.com/how-to-mock-and-unit-test-moment-js/#comment-27 Thanks for sharing! jasmine.clock().mockDate(time) was exactly what I needed!

]]> /how-to-mock-and-unit-test-moment-js/#comment-18 Tue, 21 Mar 2017 21:04:00 +0000 http://ec2-52-36-187-147.us-west-2.compute.amazonaws.com/how-to-mock-and-unit-test-moment-js/#comment-18 Just stumbled onto this and I have to disagree with this implementation completely.
What is happening here is that the unit test is relying on something which exists outside of the unit’s world which is something that you should never care about. Instead of the unit test using the actual moment implementation you should stub getCurrentTime and return what you want in order to unit test this. This way you can test various scenarios which could be time sensitive.

]]>