Signs you are doing continuous testing wrong

Re:Signs you are doing continuous testing wrong by nobody271 on Wednesday November 07, 2018 @10:57AM (#18399932)

I like test recorders (Selenium IDE). They aren't brittle if you manually enter your selectors. Plus you can hook a test recorder up to your own code to fill in any gaps. I do wish they showed mouse movement, though.

One I'd like to add is to keep it simple. When I hear the word pipeline I immediately think "oh no". I'm telling you man, some shops add a mind blowing amount of unneeded complexity with their pipelines.

[ Parent | on HN ]

Re:Signs you are doing continuous testing wrong by weliketocode on Wednesday November 07, 2018 @01:22PM (#18401023)

'not brittle' if you 'manually enter' isn't exactly a glowing review.

There's definitely some good with selenium, but I and others find it is often brittle and doesn't catch errors as reliably as would be ideal.

[ Parent | on HN ]

Re:Signs you are doing continuous testing wrong by alex__c on Thursday November 08, 2018 @10:39AM (#18406994)

The objects under test are brittle and bound to change dramatically. Selenium can't offer you insurance against this.

I now remember a test suite we had on my project (automotive). We tested against the code structure... that is, we would follow a variable's lifetime and check that its value is correct throughout execution. Two releases later, guess which function got slightly refactored and threw off some 20 testcases?

[ Parent | on HN ]