When we talk abt psychology- a different mind set always to find mistakes- for dev its difficult to find mistakes in his own work, its same for any author or creator to find mistakes on his own product.
So we have a separate team with the mindset of finding issues or try to break the system see or bring failures and developer has mindset of creating the content
Generally – developer as a positive approach to the system and its difficult for them to accept the system has a defect, and the tester comes with negative approach to the application.
With few practices- realization of working together in long term , the tester may see all the things negatively and see the people in negative way as well, as if one starts pointing fingers on some one else- one may forget the common goal of the org towards the application
one must have the positive attitude towards people and negative approach to the application- there are few good practices in org in a mix team of dev and tester working together.
Overall +ve mindet and approach wit the colleagues in the team so any issue so the defect created will not create any rift or criticism, WE need to collaborate rehter than battles saying this must have been taken care!
Miscommunication must be avoided- all parties must confirm that the understanding of the issue and all are in same page!
Testers and Developers Mindset
Developers- constructive and complete the functions created on time.
Testers: destructive towards the application- find all possible defects so the end user does not face any challenge!
Advice to developer/tester/BA- reduce mistakes and make use of the static testing so the app is not created wrongly i first place- time, money is saved.
Add lot of value to quality of product.
In the right mindset dev can test their own code- and in general they do not come int heat mindset for ex: Dev may consider the app created as his baby and will not be int he mindset of finding the issue!
Key momnets- no personal rivalry – certain reports must be generic and no pointing fingers that defect is due to the dev work done in a wrong way kind off- instead it must be the issue was noticed ont eh application , need help in this from the developer to fix it!
Being positive with DESTRUCTIVE approach.