¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Testdrivendevelopment
  2. Messages
Single Messages Topics Expanded Polls

Re: Classifying tests: problem? solution? something else?

 

I like examples.

WRT naming, I worked at an insurance company. There were problems with churn in API code, particularly around certain domain concepts.

One of those was 'customer'.

To the policy lifecycle team, customer meant 'a person that has bought one of our policies'.

To the sales team, customer meant 'someone who is considering buying one of our policies'.

To the support team, customer meant 'a person who needs help, who may or may not hold a current or expired policy'.

Needless to say, the requirements over what data these teams needed to store about a 'customer' were quite different, although there was (of course) common elements.

Once everyone understood that these were different things, we were able to agree on different language in order to differentiate different groups' concerns.

Fox
---

On Wed, 26 Jul 2023, 15:19 J. B. Rainsberger, <me@...> wrote:
On Thu, Jul 6, 2023 at 8:46?PM Ron Jeffries <ronjeffries@...> wrote:
?
Possibly that is why in XP we called them programmer tests and customer tests. :)

That's one usually-quite-important axis. :) It's one of the ones I continue to consider regularly.
--
J. B. (Joe) Rainsberger :: ?:: ::

Replies from this account routinely take a few days, which allows me to reply thoughtfully. I reply more quickly to messages that clearly require answers urgently. If you need something from me and are on a deadline, then let me know how soon you need a reply so that I can better help you to get what you need. Thank you for your consideration.

--
J. B. (Joe) Rainsberger :: :: ::
Teaching evolutionary design and TDD since 2002

Join [email protected] to automatically receive all group messages.