Is there an easy way to stub out time.Now() globally during test?

by

With implementing a custom interface you are already on the right way. I take it you use the following advise from the golang-nuts thread you’ve posted:

type Clock interface {
  Now() time.Time
  After(d time.Duration) <-chan time.Time
}

and provide a concrete implementation

type realClock struct{}
func (realClock) Now() time.Time { return time.Now() }
func (realClock) After(d time.Duration) <-chan time.Time { return time.After(d) }

and a testing implementation.

Original

Changing the system time while making tests (or in general) is a bad idea.

You don’t know what depends on the system time while executing tests and you don’t want to find out the hard way by spending days of debugging into that. Just don’t do it.

There is also no way to shadow the time package globally and doing that would not do
anything more you couldn’t do with the interface solution. You can write your own time package
which uses the standard library and provides a function to switch to a mock time library for
testing if it is the time object you need to pass around with the interface solution that is bothering you.

The best way to design and test your code would probably be to make as much code stateless as possible.

Split your functionality in testable, stateless parts. Testing these components separately is much easier then. Also, fewer side effects means that it is much easier to make the code run concurrently.

More Related Contents:

  1. Mock functions in Go
  2. Fill os.Stdin for function that reads from it
  3. Is it possible to mock a function imported from a package in golang?
  4. Testing os.Exit scenarios in Go with coverage information (coveralls.io/Goveralls)
  5. How to unit test a Go Gin handler function?
  6. Proper package naming for testing with the Go language
  7. Is it possible to mock a function imported from a package?
  8. Example code for testing the filesystem in Golang
  9. What Makes a Good Unit Test? [closed]
  10. What’s the difference between unit tests and integration tests? [duplicate]
  11. Should one test internal implementation, or only test public behaviour?
  12. What is unit testing? [closed]
  13. Should Private/Protected methods be under unit test? [closed]
  14. Visual Studio 2015 or 2017 does not discover unit tests
  15. Unit Tests not discovered in Visual Studio 2017
  16. Unit testing Anti-patterns catalogue
  17. How to test my servlet using JUnit
  18. Configuring IntelliJ IDEA for unit testing with JUnit
  19. Do MSTest deployment items only work when present in the project test settings file?
  20. Updating input html field from within an Angular 2 test
  21. Junit5 mock a static method
  22. How to avoid multiple asserts in a JUnit test?
  23. How do you mock a Sealed class?
  24. Example invalid utf8 string?
  25. Should it be “Arrange-Assert-Act-Assert”?
  26. Dependency Injection: Turtles all the way down?
  27. How to do TDD and unit testing in powershell?
  28. Testing route configuration in ASP.NET WebApi
  29. how do I mock sqlconnection or should I refactor the code?
  30. When is a Test not a Unit-test?

Leave a Comment