Learn Mobile/Web/Manual & Automation Software Testing

Don't worry if you don't like coding :)

The business people, the analysts, developers and testers. All of
them should be in a team, working on a project, or part of it.
They should be working together from the beginning, when
requirements are discussed, explained and written, through the
design, then development and testing.
A collaborative relationship rather than a competitive
relationship with a software team will drive better results for
all, for the project first.

Call it development driven testing, or any other way you wish, as
long as you can see the benefits of such practice and how it can
solve the problems in discussion. let’s go back to them and
review the new process and how it helps:

No time pressure – Testing is done continuously, from the
first phase, never postponed to the end of a development stretch.
It’s done in smaller units, with visible immediate results.
Development and testing move forward simultaneously.
Positive feedback – This is a nice one. In the first case
the process always ends with a negative feedback, but with
testing done while developing (and fixing) the end result is
always success.
Think of code that is written according to an already written
test – it is bound to work, and the test will pass. It just
can’t otherwise.

Responsibility – all of the team is now involved in the
testing process, writing tests, understanding the tests, and
developers are practically executing tests as part of what they
do.

No classes – since not only the testers are testing, the
importance of the testing is now higher, developers are part of
it, accepting it completely different than before. Working all on
the same team, brings more equality, better communication, better
understanding of the qualities and challenges of each team
member.

Less conflicts – the individual tester is now part of a
group, which is not a testers group only, but a group/team which
works to complete a goal of creating a new working code.
Easier testing management – the QA manager has now more
information, from day 1, can better plan the resources, the
tests, what’s need to be tested and how.