Developer role in QA testing
Hi,
I want some info regarding how a change or fix or feature in a software is tested.
Suppose the developer has done the coding. After that a QA is assigned to test the code.
how much a developer has to be involved in QA.
Once the feature has been delivered to QA for testing.
Is the QA job to test it from all scenarios and finally mark as passed ?
And the developer deploys it to production.
what are the exact and actual steps that should be done.
developent complete ----> movement to staging environment/preprod ---> QA testing--> QA certified ---> move to production
My question is how much a developer should be involved in QA testing. Or he shouldnt be at all
Thanks
I want some info regarding how a change or fix or feature in a software is tested.
Suppose the developer has done the coding. After that a QA is assigned to test the code.
how much a developer has to be involved in QA.
Once the feature has been delivered to QA for testing.
Is the QA job to test it from all scenarios and finally mark as passed ?
And the developer deploys it to production.
what are the exact and actual steps that should be done.
developent complete ----> movement to staging environment/preprod ---> QA testing--> QA certified ---> move to production
My question is how much a developer should be involved in QA testing. Or he shouldnt be at all
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Depending upon the work environment the developer may create the tests while they code and other times the QA people get the code and write the tests.
Normally the tester should not be the person writing the code. The developer has too much of themselves invested in the code and the tester has nothing invested in the code other than ensuring that the tests work or fail. Two eyes looking at the same item is better than one. Sometimes when coding you can't see the trees because the forest is hiding them. The second set of eyes may see the missed semi-colon quicker than the developer themselves.
In my coding days If I was stuck on something while debugging my approach was to walk away and look at it later with fresh eyes. Most of the time the problem jumped out at me.
Normally the tester should not be the person writing the code. The developer has too much of themselves invested in the code and the tester has nothing invested in the code other than ensuring that the tests work or fail. Two eyes looking at the same item is better than one. Sometimes when coding you can't see the trees because the forest is hiding them. The second set of eyes may see the missed semi-colon quicker than the developer themselves.
In my coding days If I was stuck on something while debugging my approach was to walk away and look at it later with fresh eyes. Most of the time the problem jumped out at me.
Everything should be documented by the Dev , so anyone who will work with the application will be aware of the changes and logical, uses case, bug fixes, entire application logical, role etc... When you fix something more detail you give about related interface or function more easy this will be to find the bug or maybe find a possible new scenario. Is any DB changed, which field.... More details you document more easy will be to find possible bugs.
I do document every single bug fix, so later that will be easy to recall what I did and why.
I'm using an excel sheet when developing and find my own bugs during dev phase.
I'm using Mantis for bug tracker once the first version is ready to be tested by a tester.
The main problem is when fixing something it may break other code on another interface.
And this may break the entire logical or data integrity.
So I would say as a dev you should test your code thoroughly and document everything, it may sound long to do but in fact this will save you lot of time. Plus your code quality will be impressive and your coworker happy.
The tester should make several tests that may cover the bug fix and depending the bug he may need to retest everything.
And if you have validation, the validation need to be done once again.
So yes the dev should be involve in QA