Coding 2022-12-16

Tags:
By Max Woerner Chase

The next step for increasing test coverage for MOTR, is to refresh my memory. I see that the next stuff I want to exercise is currently, in existing code, kind of just tossing around FlexIn objects in a way that isn't quite satisfying, according to my gut reaction.

Like, this shouldn't be relevant to the tests, but it feels a little weird to have the same FlexIn object appear twice in the expressions going into the command... Like... the FlexIn and its derived LessFlexOut should always be paired, but I guess I don't have enough examples to decide on how to do it generally. Although, it doesn't have to be general. It could just as well be a function that returns a sequence of Parts, and I just call it like .add_parts(*func(...)).

When I have time to work on the tests, I'll have to experiment with making interfaces like that, and update the existing code if the result is satisfying.

Anyway, I let things go way too late again, so I have to cut this off here. I'm not sure I'll get anything done tomorrow, so let's see how the weekend goes.

Good night.