Test, automate, test, automate

[smara-codes]

This came up in an Automated QA meeting a while ago so I summarized it here. This is not intended to go into details regarding how to automate tests, what tools to use but if people feel like that would be helpful to capture I feel like that would be more of a USM coding guidelines / proven technologies topic.

[levijackson]

👍 👍

It is expected for a team to go a little bit slower while ensuring quality is built into the code.

I like this is expressed. One area I still don't know that I can feel comfortable is determining when tests get written. By that I mean, do we wait for tests to close a story? do we write a tech story (tech debt) and do it in the future?, or something else. Ensuring they are written in a reasonable timeframe of the feature is important to me though.

[smara-codes]

One area I still don't know that I can feel comfortable is determining when tests get written. By that I mean, do we wait for tests to close a story? do we write a tech story (tech debt) and do it in the future?, or something else. Ensuring they are written in a reasonable timeframe of the feature is important to me though.

In my opinion, the default should be tests are part of the definition of done for a story. If in the interest of time, as an exception, code does need to be released without tests that are acceptable as long as we pay off that technical debt sooner rather than later. It's easier to stay up to date than to catch up.

[andriytam]

Remember, badly written tests are always better then no tests :)