I'm responsible for staging some tests, against some members, namely against the rates that are due for them. After talking about it with my peers, I see the members are a function of three other models:
- member lead
- rate card
They were about to create separate spreadsheet just for the members, manually doing the calculations for them or using Excel formulas to do them, but I saw that they were a function of these three, and argued that we can create these programmatically instead. They ended up liking my idea.
My idea would involve creating some
MemberModel, and a
MemberModelExpectationBuilder that would handle the computation and generate the expected states for each new member, to use in the test cases.
Is that idea a code smell?