Thread regarding Wells Fargo & Co. layoffs

Developers not fit for Software Testing

6 Reasons that Developers fail as Software Testers...

  1. Lack of end-to-end perspective.
  2. No experience as tester, no idea on how to find bugs or defects.
  3. Biased towards their code.
  4. Misunderstanding requirements, wrong approach and no apatite to understand testing.
  5. Both are two different specialized professions.
  6. Developers' mindset is positive thinking, build, develop whereas testing mindset is pretty much the opposite who find creative ways to break a product, drill deep to find defects.

This is why we need a Test Team!

What do you think guys?

by
| 1466 views | | 14 replies (last October 15, 2022) | Reply
Post ID: @OP+1j8g8iFN

14 replies (most recent on top)

The quality of code that makes it to production has taken a major hit for many business lines with the elimination of the CTM department back in Nov 2020

by
| | Reply
Post ID: @5nmw+1j8g8iFN

It is disappointing that people do not understand that UAT is still part of agile except that it will be performed by the end users with real life and practical scenarios.

Unit Testing, Automated Tesing, along with manual end user driven UAT will all contribute to the production of good quality software.

QA analysts that do not want to learn Automation simply need to find positions in End User testing arena.

by
| | Reply
Post ID: @3dcw+1j8g8iFN

Well said. You need a team of well seasoned developers, and a team of well seasoned business owners. Additionally, ergonomics specialists. Those special individuals who have an eye and a mind for thinking outside the box. Constant use of an application by many individuals will uncover the design flaws.

by
| | Reply
Post ID: @3frj+1j8g8iFN

Developers do not have the ability to test with a business requirement perspective and neither does automated testing. You need a human business user to catch much of the defects. Now add in the fact that the definitions of the summarized data elements are not understood and data elements are renamed over and over again as they move end to end. How does this process ever result in reduced defects. Years upon years of “no time to clean this up” just keep building on it.

by
| | Reply
Post ID: @2phu+1j8g8iFN

And you think you walk on water…

by
| | Reply
Post ID: @2lhi+1j8g8iFN

On my team the software we write has no bugs.

by
| | Reply
Post ID: @1khq+1j8g8iFN

Remember the millions of dollars spent on a CRM system in WIM, called Client Link? what a load of junk. I’ve never seen so much zombie code in all my life. So many broken processes. The company wasted millions and now it’s slowly being dismantled for something else. Even the brokerage department wasted millions of dollars on software that was never implemented.
Being a public company, I’m really surprised shareholders didn’t have more oversight in all the wasteful spending.
I think technology should be outsourced to the professionals, and really scrutinized by our own internal teams to ensure all gaps are filled. Additionally, we have so many data marts scattered among different platforms, full of broken ETL processes with stale/obsolete/incorrect data. Out of date meta libraries are not helpful. To make matters worse, the company implements new processes, because the people managing the original sources have all but left the company or changed positions.
The company’s unspoken motto,” Let’s rebrand and start over”.

by
| | Reply
Post ID: @fdf+1j8g8iFN

I think OP is in the same boat with the rest of us as far as being informed. Executive management is so coy, I don’t think anyone else really knows what’s going on. All I know is what I see in here. Data lake? It’ll be a data swamp, IMO. I’ve yet to see this company, strategize and implement a tool that actually really truly works. If the clients only knew the millions of dollars this company wastes trying to figure out software development, I think they’d be quite upset about it.

by
| | Reply
Post ID: @ybx+1j8g8iFN

OP is uninformed. The best testers that were called QA Analysts were moved to the development team and learned automated testing.

They are now titled Software Engineers. Those that can not unskilled will eventually be laid off. The warning went out a few years ago.

There are capable software engineers with solid QA experience that are handling the task.

by
| | Reply
Post ID: @yek+1j8g8iFN

The best is rolling out a platform last year to automate digital workflows, then with executive support, not allowing other teams access to APIs to automate workflows.

A year in from the SN roll out, and we still can't use it for what it was promised to do.

by
| | Reply
Post ID: @hkq+1j8g8iFN

Could solve a lot of this by hiring quality developers who don't plan on QA'ing their code after deployment.

by
| | Reply
Post ID: @kip+1j8g8iFN

I love opening JIRAs And trouble tickets. There is so much zombie code in our major systems. It’s pathetic. Would I pop served over the years, is that the people designing the systems and the business are too close to the project. You need a true gap analysis team to go through the processes.
What really makes me mad is when the business and the developers get defensive. Whenever I point out an issue, their excuse is that that was done by design. I don’t care if it was done type of design, it’s wrong, regardless.

by
| | Reply
Post ID: @vut+1j8g8iFN

I used to do a lot of testing. It was my passion, define design flaws in the UI and back end ETLs. The issue we have with this company is that the developers are a part of one group, the owners of the system, a part of another group, and a third group Of testers are rarely brought in. The third group of testers should not be the business or the developers, but a completely fresh set of eyes.

by
| | Reply
Post ID: @rzm+1j8g8iFN

more issues have gone to production since testing teams were disbanded. Test environments constantly have issues, system integration is a mess, to your point, downstream impacts aren’t considered

by
| | Reply
Post ID: @tcj+1j8g8iFN

Post a reply

: