A unit test verifies that a single unit of work, usually a class method, works correctly. Unit tests should generally avoid accessing the file system, database, or network resources. Types requiring this kind of access ideally rely on an abstracted API and have the types used in production substituted with stubs or mock types during testing. Unit tests should execute rapidly and cause no side effects that affect other unit tests.
3.147.76.135