tomevault-io Write unit tests
Best practices
- Unit tests should go into tests named for the functions being tested.
- If you have a function
Foo, you should have a test function namedTestFoo. - Methods with receivers should include the name of the receiver's type. A
method like
func (f *Foo) Bar() {...}should have a test namedTestFooBar.
- If you have a function
- Tests should only test the behavior of the function. Don't exhaustively test every possible input.
- Each behavior you test should have a test case. If you have more than two test cases, use table-driven tests.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.