testers and developers mindset in this tutorial we are going to learn in general what mindset means uh or what it refers to and then we'll see how the testers and developers mindset are different in the way they approach to the problem solving so let's first see what exactly a mindset is so mindset reflects an individual's assumptions and preferred methods for decision making and problem solving so this is a generic definition of mindset so what this means is if you are working as a tester in an organization the way you approach to a problem to a problem and how you are going to solve that problem will be different from the person who is in a different role so for example a developer will will approach to the same problem with a different mindset or a different approach so his preferred method would be different as compared to your method if you're working as a tester and this is true for all other roles and responsibilities that people play because it's what you are doing or what sort of role you are playing defines the way you will approach to solve a particular problem if a person is in army uh or military he'll approach to the similar problem in a different way um if you're working in an iit industry you'll you'll approach to similar problem in with a different mindset and different way uh and this is more driven uh because of the way or the amount of time you have been spent spending in that particular field uh and the way you have been approaching to solving those sort of problems so that's in general uh what a mindset is all about now we'll see what is a mindset uh for testers and developers so if you see in this slide we have listed some of the tester's mindset so he should be playful um curious uh so why playful because if you're not playful you'll be sort of uh not be able to tell very well with the team and it's in testing and development it's more about working together to come up with the best solution for your client or for the end user so playful have being playful is very important doesn't matter whether you are a developer or a tester it doesn't matter what your role is but being playful as a tester is very important then the next one is curiosity so you should be always curious to learn new things because in the current age of technology uh it changes so rapidly that you have to make sure that your skill set is always up to date and you are able to solve the uh tricky problems or complex problems with the right set of tools that are available in the market nowadays so you should be curious to learn new stuff and curious to keep exploring and [Music] coming up with the better solutions for your customers and clients then the next one is professional pessimism pessimism now why pessimism is important as a tester because you should be questioning the build or the application that you're testing that this what all different ways are there that i could figure out that this might not work or this might not fulfill the end user uh needs so that pessimism is important in terms of um figuring out what might not work in a product or what might go wrong in the product so this is known as professional pessimism and it's very important when you want to figure out what might go wrong and what might be the defects in this current system so that is very important then the next one is good communication so communication is very important so it be verbal or written communication so when you're documenting a defect or having a chat with the developer to explain the problem or identifying the root cause and then explaining it to the developer it's very much important so next one is the motivation motivation is very important as well uh if you're working as a tester so you should be always motivated when working in the project and that will give you an opportunity to figure out or give your best in the project while you're working as a tester in the project the other ones is um other ones are the critical eye and attention to detail why these two are important because if you're not providing or if you're not very attentive while you are testing anything you will miss out certain combinations or certain workflows which might be really important to the end user so having those all details or providing attention to detail and critical eye is also very much important when you are working as a tester in any project now let's go back uh let's go forward and see what are the some of the developers mindset um so developers mindset playful curiosity these are sort of common it doesn't matter what role you are in you should be playful you should be curious to learn new stuff in this technology age fast-paced technology coming through so you should be very curious to learn new things always then the next one is system thinking system thinking is very important for the developers and what exactly is mean this means is uh basically the developers should be having a clear understanding of the system as a whole rather than being just concerned about the components that he's developing so if the developer doesn't have the system thinking he won't be able to figure out what are the user scenarios or the end users how the end user is going to interact with the system he'll be just concerned with his component and once he's done with with his component he won't give it a thought how that component is going to integrate with other components so having the system thinking is very much important for the developers usually when you're working in a testing role you always have the system thinking because you see the system as a whole you explore the system as a whole you understand what are the user scenarios and based on the requirement you come up with those user end user scenarios but most of the time this system thinking is sort of missing when you are working as a developer so having this system thinking for developers is very much important now good communication is another uh important one so a developer should be having the good communication so that he can communicate properly be it written or verbal with the other members in the team if he has any any doubts for any requirements or any defects then the next one is he should be problem solver wherein he should be able to explore what all available tools or the documentation is available and figure out what could be the solution so basically should be very curious to learn and solve the problem then he shouldn't be fear or shouldn't have fear to seek help so should always be um going for help to the other members in the team uh because everyone can't know everything so it's it's good enough to reach out to people who can help you so that you can achieve the goal as a team that you are looking for and then always keep learning so um developer should always be curious to learn and have the ability to keep learning the new technology so that he can come up with the better solution for the client and better architecture for the product is working in so these are some of the mindsets that we have discussed for developers and testers now we'll see what are the key differences between the mindsets of developers and testers in the same project or the problem that they are approaching so in any software development project the end goal of any member of that particular project is to deliver value or the end working product which is fit for use for the end user or the customer that you're working for now the way a developer approaches the same problem or figuring out the solution for the same requirement and the tester approaches the uh the problem is kind of different so when a developer is working on that particular requirement his mindset or the approach to tackle that particular requirement is he will ensure that he covers all the aspects of the requirement and makes sure that he has that all the possible combinations are working so he's more of a optimist sort of um mindset wherein he ensures that he figures out that all the possible combinations are working and he has coded for all those possible combinations whereas when it comes to the tester he and he his mindset is different he is more of a pessimist for that same requirement he'll ensure uh he'll try to figure out what all things might go wrong when he is going to test that particular component or that particular piece of code that is developed by the developer so when tester will approach he'll figure out all the possible combinations or the use cases that might go wrong while he is testing the application so these are some of the differences in the mindset of developer and tester thank you