First of all, keep doing that Lucas! You are more brave than I ever was or probably will be! You rawk!!!
> not really for the sake of gaining time to work on something else, but rather that I was felling [sic] in love with the solution. Designing the solution, coding it, testing for all edge cases and... Debugging. A lot.
Lucas has apparently done "QA automation."
Any test dev, the kind you'd want to hire if your managers hadn't already decided to "automate test steps" would tell you not to automate test steps. That's slow and brittle and automation and manual tests are very different.
Do not do manual QA automation, in case that wasn't clear.
A test dev is a frikkin' ninja who follows Wall's 3 Virtues. [1] Lukas, if you can figure out where we are (and the secret knock), you can join us. Honest.
if you join the sibling-hood, you will understand:
> multiple sides to a task and that uncovering every facet
This calls for parameterized or tabular or property-based (synonyms-ish) testing. Look those up for the Language/framework you're using.
> may not be worth it
Well . . . Larry Wall would say if you have to do it over and over we've probably already talked about it for too long . . .
> whatever dull or repetitive task
Yes, automate those. The fact that you're claiming things are not dull or repetitive enough . . . make them seem like a forum. :-P
> if you can figure out where we are (and the secret knock), you can join us. Honest
Best hiring line, ever. Will definitely go look for the hidden circle of test devs.
> tabular or property-based testing
That's interesting, I did not know it was called this way! I have followed this approach in some cases, testing combinations of inputs. It was mainly when trying to automate tracking QA, through passing different dataLayer e-commerce values.
> not really for the sake of gaining time to work on something else, but rather that I was felling [sic] in love with the solution. Designing the solution, coding it, testing for all edge cases and... Debugging. A lot.
Lucas has apparently done "QA automation."
Any test dev, the kind you'd want to hire if your managers hadn't already decided to "automate test steps" would tell you not to automate test steps. That's slow and brittle and automation and manual tests are very different.
Do not do manual QA automation, in case that wasn't clear.
A test dev is a frikkin' ninja who follows Wall's 3 Virtues. [1] Lukas, if you can figure out where we are (and the secret knock), you can join us. Honest.
if you join the sibling-hood, you will understand:
> multiple sides to a task and that uncovering every facet
This calls for parameterized or tabular or property-based (synonyms-ish) testing. Look those up for the Language/framework you're using.
> may not be worth it
Well . . . Larry Wall would say if you have to do it over and over we've probably already talked about it for too long . . .
> whatever dull or repetitive task
Yes, automate those. The fact that you're claiming things are not dull or repetitive enough . . . make them seem like a forum. :-P
[1] https://hackernoon.com/larry-walls-three-virtues-of-a-progra...