“What’s your most ‘this can’t be real’ moment in test automation? 
”
For me, it was an automated test that ran perfectly… but had no checks at the end—just a comment: “Now check the Excel data.”
The Excel file averaged 500 rows.
What about you? Let’s hear your automation horror stories or hilariously unexpected moments!
#TestAutomation #QA #SoftwareTesting devops #AutomationFail #TestingLife #QualityAssurance #AutomationTesting #DevLife #TestAutomationJourney
Your mentioning of Excel reminded me of a project where Cucumber was used to write tests (with step definitions written in Java). So far so good.
However, running the scenarios generated Excel files containing BASIC code that then coud be imported into a test management tool that then could run the tests.
I claim this is qualifies for both categories, horror and hilarious. 
I started at a client in which they said they did UI automation pretty nicely but could have some improvements here and there.
First day I saw that the pipeline took 13 hours a day of UI automated tests.
I was doing presales for a performance testing assignment and they told me “new state of the art restful API’s” – but nothing asynchronous so I thought easy peasy quick and dirty POC of 10 days.
I arrive at my first day and what do I see… they tried to make restful API’s in a 1960’s Cobolframework which was absolute hell. Nobody followed the restful way. But they tried…
Everything was a POST request and EVERYTHING returned a 200 OK.
Even if your request was bad and you would expect 400 bad request… they provided a 200 OK.
Forbidden? Nah 200 OK. but just no data.
GET request for reading? No thanks let’s POST that too!
It was a hell and thankfully I only had to do a POC and I didn’t continue with that company, what a mess
From recent:
Good day @restertest ,
My point of view it is not possible test the real time sensitive data information .
Most Lines of codes also matters without proper planning.
Additionally exhaustive testing is practically impossible for most software systems.