[u-u] jobs @ rakuten/kobo

[David Collier-Brown]

The wording suggests a group doing "code first, test whenever".

And with people other than the authors writing the tests, they may 
easily test for a particular implementation rather than a desired 
result. That was endemic at WG.

  My recent experiments with BDD suggest black-box testing at a high 
level for success first, then cautiously for regressions that were 
user-visible.

--dave

On 05/08/17 09:02 AM, D'Arcy Cain wrote:
> On 08/04/2017 10:22 PM, Anthony de Boer wrote:
>> William Park wrote:
>>> I couldn't help notice that this position says "Automation Engineer" 
>>> in title but says "Software Developer in Test" in description.  I 
>>> assume it's similar to "Test Automation Engineer"?
>>
>> Welcome to the 21st century, where more time and effort goes into coding
>> the automated regression testing of a new feature than needs to go into
>> coding the feature itself.  :-)
>
> Which is a good thing.  Better than "Welcome to the 20th century where 
> more time and effort goes into debugging regressions than went into 
> the coding the feature itself."
>

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb at spamcop.net           |                      -- Mark Twain