Nullables Livestream 16 Eventful Tests

James Shore: Testing With Nullables

James Shore: Testing With Nullables At the end of the last episode, we introduced a way to track which games gamedatabase had saved, but it doesn’t clean up the tests as much as we’d like. In this weekly livestream series, i pair up with ted m. young, aka jitterted, to look at nullables and a frame architecture as an alternative to mocks, spies, and hexagonal architecture. each episode combines a healthy dose of architecture and design discussion with hands on coding. in this episode what is “good design?”.

James Shore: How Are Nullables Different From Mocks?

James Shore: How Are Nullables Different From Mocks? We looked at nullables and a frame architecture as an alternative to mocks, spies, and hexagonal architecture. each episode combines a healthy dose of architecture and design discussion with practical, hands on coding. the source code is on github. Live, stream of consciousness programming using test driven development and incremental design. The “nullable” testing patterns offer a way to incrementally write tests on legacy code and to avoid mocks and design changes for testability, by allowing any class, to implement in addition to the production code a “nullable” implementation that just outputs smart logging events. “nullables” are a novel technique for isolating production code from external systems and state. although they also have production uses, they’re particularly valuable for creating fast, reliable tests. this page connects to you resources for using nullables in your code.

James Shore: Testing With Nullables

James Shore: Testing With Nullables The “nullable” testing patterns offer a way to incrementally write tests on legacy code and to avoid mocks and design changes for testability, by allowing any class, to implement in addition to the production code a “nullable” implementation that just outputs smart logging events. “nullables” are a novel technique for isolating production code from external systems and state. although they also have production uses, they’re particularly valuable for creating fast, reliable tests. this page connects to you resources for using nullables in your code. Output tracker is a utility for writing state based tests using nullables instead of mocks. it can track the state of dependencies which can then be asserted in the test. In this talk, you’ll learn how nullables work, see examples of programming with nullables, and get access to free resources and training so you can implement them in your own code. There it makes sense to test methods in isolation in addition to a happy and a sad path test. but i've also seen a dysfunctional system that had only mockist tests of single java classes. The most safe option is to disable nullable reference types in the unit test project regardless of the setting in the project being tested. this way you are protected if the setting is changed.

James Shore: Testing With Nullables

James Shore: Testing With Nullables Output tracker is a utility for writing state based tests using nullables instead of mocks. it can track the state of dependencies which can then be asserted in the test. In this talk, you’ll learn how nullables work, see examples of programming with nullables, and get access to free resources and training so you can implement them in your own code. There it makes sense to test methods in isolation in addition to a happy and a sad path test. but i've also seen a dysfunctional system that had only mockist tests of single java classes. The most safe option is to disable nullable reference types in the unit test project regardless of the setting in the project being tested. this way you are protected if the setting is changed.

Nullables Livestream #16: Eventful Tests