Damn this humidity! Also, there is no snow. 😆
@matigo I won’t do that. I am writing the tests to make the framework to do the thing it is supposed to do, nothing more, nothing less.
@matigo Kind of, but testing a test framework with itself requires the whole thing be in somewhat representable shape and in working condition before those tests can be written. 😆
😬 Of course the tests are not providing 100% coverage, far from it, and it is my next job to write them in order to have the bare-bones 0.1 version ready. Technically it is ready, but it makes sense to have those tests in place to show that you can rely on that version already.
@matigo That is true. I usually don’t do any coding after the workday, which also means I can make progress with my pet projects rather slowly, so yesterday was a very rare exception.
@matigo Yep. Though I did not intend to spend so much time on that pet project. I should have gone to bed at least a couple of hours earlier to get enough rest.
Oops. It’s almost 1 am… 😬 Spent the evening coding away my pet project as I am home alone with the kids until late tomorrow. Completely lost the track of time while having fun. 😆
@matigo It is. It was a pure lucky guess that we found out that the device identifier was the root cause. Should we have not had this chance to test with the real device this issue would have remained a mystery.
@matigo Indeed. And all we had in our logs was just socket creation errors. Luckily we got one of those devices and were able to figure out why we have these issues.