1 Miscommunication or no communication

Quite often, the requirements from the business is not communicated to the devel
opment team. Product owners have an idea of what the feature should look like an
d how it should behave, but if not communicated properly to developers and teste
rs, the finished product might not be as expected. The requirements should be co
mmunicated clearly to all stakeholders so everyone has the same understanding.
2 Software complexity
The complexity of current software applications can be difficult to comprehend f
or anyone without experience in modern-day software development. Multi-tiered ap
plications, client-server and distributed applications, data communications, eno
rmous relational databases, and sheer size of applications have all contributed
to the exponential growth in software/system complexity. programming errors prog
rammers, like anyone else, can make mistakes.
3 Changing requirements
The end-user may not understand the effects of changes, or may understand and re
quest them anyway redesign, rescheduling of engineers, effects on other projects
, work already completed that may have to be redone or thrown out, hardware requ
irements that may be affected, etc.
Best Software Testing Quotes
If there are many minor changes or any major changes, known and unknown dependen
cies among parts of the project are likely to interact and cause problems, and t
he complexity of coordinating changes may result in errors. Enthusiasm of engine
ering staff may be affected.
In some fast-changing business environments, continuously modified requirements
may be a fact of life. In this case, management must understand the resulting ri
sks, and QA and test engineers must adapt and plan for continuous extensive test
ing to keep the inevitable bugs from running out of control.
4 Poorly documented code
It s tough to maintain and modify code that is badly written or poorly documented;
the result is bugs. In many organizations management provides no incentive for
programmers to document their code or write clear, understandable, maintainable
code. In fact, it s usually the opposite: they get points mostly for quickly turni
ng out code, and there s job security if nobody else can understand it ( if it was h
ard to write, it should be hard to read ).
5 Software development tools
Visual tools, class libraries, compilers, scripting tools, etc. often introduce
their own bugs or are poorly documented, resulting in added bugs.
shares
Facebook
Twitter
Google+
LinkedIn
Pocket
You may also like:
Top 8 Open Source Bug Tracking Tools
Q: Are we not testers? A: We are QA!
Should Software Testers get the Blame for Live Production Bugs?
Why We Test Software
Automated versus Manual Testing Make an Informed Decision!
Severity and Priority What is the Difference?
Saas App Testing Major Challenges & How to Overcome Them?
Did you enjoy this article?

Subscribe to get notified when a new article is added to our site.