Thought of first test for minutes, this also means ive decided to make minutes observe the seconds object
assert, setup, then act for minutes test
ticktock test import tidy up
little more tidy up with minutes test
Renamed to minutes from seconds as the minutes calculation is determined from observing the seconds
First attempt at getting test to pass, got some null checks to get rid of
First attempt at getting rid of null, its a statemachine
Optomised imports, however just realised that this design is not worth pursing. The overflow idea, where the lower digit overflows into the higher digit gets bonkers when we come to the days in a month and it dosnt follow a simple rule
added "expiry date", give it two months then delete. Possible value for keeping design would be to illustrate restoration/initialisation of domain state in response to android lifecycle
first passing test for minutes change
refactored to frack
next two tests noted down
first test implemented, now time to get green
time not changing test now green
changed to use a terninary, just for fun
last test written but already green!
Test for minutes presenter sorted, time to get green
Test for minutes presenter  green
minutes presenter looks ok now
discovered i now need to have my ticktock tock multiple ticks