Why is testing so important in SDLC (system/product) because the developer always tests his/her system before it is deployed into the test/production environment. Why testing again?
Thanks in advance.
[/ QUOTE ]
Very simple. Not all developers test properly. Some do unit testing, some do integration testing... some assume their code is great and don't test (I have one of those here). Some run out of time to test....
Beyond that there is the fact that another set of eyes is always good on someting AND that QA and Development look at things different. With dedicated testing resources time is spent planning on how to most thoroughly test a release.
Testing is very important for many reasons. Above is only a small fraction of them.
The statement "because the developer always tests his/her system before it is deployed" is not correct" everywhere.
I have worked on apps where developers were tasked with unit testing and claimed they did unit testing. Due to the poor quality of the code deployed we initiated a dialog to find out that the company doing the development considered peer code reviews to be unit testing.
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison
Also, when developers test on their own, they do what they are 'supposed to do' and testers do whatever users may do. The developer knows the application from his own point of view, but the user doesn't see it that way.
Just a qucik note shanti...just elobarate the terms in SDLC and ready each word by word..probably ur dbt will be cleared..
Software Development Life Cycle..its the LIFE CYCLE os software development ..so in life cycle we need to knwo whether it 's the right software we have built or prepared and test it..so obviously there comes the question of testing...hope u got it ina a general way....
and reply on this...u r half way right..abt the dev u r true but when u take the case of testers they only know the application but doesn't know exactly what users need..so they work as a bridge between developers and end users..
So testers try to find as many as bugs and errors possible and int he end there will eb user acceptence testing...which clears of the doubts from users and ready for more bugs if the software is not build as per the user requirements...
Developers only build and they are always in their own way of thinking while building the software...
Our developers rarely if ever run the actual application. I've had many times when I launch an app and it crashes on the first try. When you ask the developer about it, they almost always reply something about kicking off the stored procedure and the SQL returned the expected data. Well that's all well and good, but the application itself doesn't work. Very frustrating, but I like to think of it as job security [img]/images/graemlins/smile.gif[/img]