 I'm just I'm just turning these on right now. I just want to make sure we're not on the stage at once So that's why we have the extra mic in this room So wait are the three handhelds in here too? We're going around So just You know fyi you're the moderator we use the lab On stage We'll see This is a one o'clock I'll be here in this room. It's all connected and stuff. Yeah. Yeah, it makes sense cut to come 10 15 minutes before them Because they're just gonna pass the mic back and forth. Okay to answer questions, but people are gonna come early at that time You think or so? Just so we can be absolutely sure Okay We all just loud enough because there's no audio cable sure I think we'll be fine But if you have some it's not great. Do you have top presentation? No So we've got this audio line hooked up to hit the mixer in the back so that way you can get recorded on the camera They have set up there Well, this will this will play through the room as well so this is your direct Yeah, this is your direct input and we cannot since it's early we can test volume make sure it's not too loud or Where is it? Which should actually be on the user side are tilted more towards the developer side so that was my argument and We didn't want to remove this coupling. So we suggested that why not have a separate person Come as a cynic and provide that additional user perspective to the sprint team So while doing so while doing so I came across this bias called as Curse of knowledge and the curse of knowledge means that when you're talking to someone you automatically assume that people have a Background to understand right? so let's say there is a There is a professor of physics or quantum physics, whatever theoretical physics And he has to teach to kindergarten kids. Is that a good match? It's not right Because at at his level of knowledge He will kind of assume that they have some background of science or physics or something, right? I'm sorry. So This is this is how biases Affect our decision-making in day-to-day life more so in testing All right, let's play a game now So if you look at the screen, there are two jars Jar a has two black and two red balls Okay, so far so good Jar B also has four balls, but we're not aware of the color The only thing I can guarantee you is that jar B also has either black balls or red balls Okay, there is no third color So jar B can either be all black or red three black one red all those combinations okay all right, so now you have a hundred dollar price for a Randomly drawing a black ball Which jar do you think has more probability of drawing a black ball jar a or jar B? a so who do Those who think a here is their hands and those who think it's B here is their hands or Anyone anyone who would like to tell me why it's a Is a better chance so All right, that is one way of looking at it any other any other arguments. Yes Anyone else Just go with what you have All right All right, if there are no other arguments, then I'll go ahead You want to say something All right That is that is a safe way of looking at it So I'll tell you the thing mathematically both the jars have same probability of Drawing a black ball why because there are just two colors Total number of favorable outcomes divided by total number of outcomes Right when you drive ball, it is either black or red in both the jars So 50% chance in both the jars But some people said a Those are the people I don't want to judge But those are the people who put their money in real estate and government bonds And the other people who said be like you they usually go towards stock market Startups stuff like that You get you you understand where I'm getting to So there is there is an There is a tendency in humans to ever the risk some humans Not everyone Some people leave their jobs and start a new thing that is taking this because you know that on the There would be no paychecks first, but There are chances that your business would be successful. Correct So this thing is called ambiguity paradox and How does it impact testing so we are talking about testing and software development here, right? How many people aware of user stories? All right, everyone. All right So take this we are building a software of school management system or a student management system right for simplicity and I am a front-end developer I need the backend team to give me an API where I can create read update delete the student record existing student record with a New Boolean field called needs scholarship Right, so there are various business factors on which a college or a school decides that a particular student will Get a scholarship right, but that has also be maintained in their digital system of records. Correct So now we are adding that Boolean field on the student object that this particular If this is true, then that person will get a scholarship, correct As soon as this story hits a tester These are the questions in his mind Okay, the first thing is releasing story on time What does your product has your product owner promised a date to the stakeholders? Right. This is a big factor. Correct Do you know enough about this change are you aware of the how school works how their Business what their business rules are to impact such a change The third thing is how about you start automating? Whatever you know, you know two or three things about this story You'll start automating so that you at least build the regression suite first Okay And the fourth thing is what systems would be the source of truth And there there would be if it is a multi-tier system There would be either a database or a dumb back-end or an intelligent back-end It would be the source of truth for this this field right where the actual information of this Boolean resides So are you do you want to know about that also or would you just Send some APS and some requests and see whether it's getting populated the responses correct and be done with it So these are some of the Thoughts which a tester would have when the user story hits it so based on the A and B analogy the testers who take risk Will check all four questions Okay, including the last one which is very important Testers who play safe will just do one and two Right, so now that We are aware about this bias we can actually go ahead and do all four correct So the best thing with every bias is to be aware of it right correct, so Again with the investment example If you have a friend you are a safe person who plays safe who invests in government bonds and stuff like that But you have a friend who is earning good at the stock market He pushes you to invest in stock market. He teaches you how it works Slowly and gradually the thing with ambiguity a virgin is that once you start experimenting with it and once you You will fail couple of times, but eventually you will be good at it so the best practice is to Take the ambiguity head on and deal with it Let's say two or three times you may find it difficult, but eventually you'll be good at it All right the second bias Second bias is the congruence bias. It's a brain glitch which Stops us from thinking out of the box Now I'll give you a very good example A couple of months ago. I was You won't get the perspective, but the game of thrones episode actually in India. It comes early morning at 6 Okay, so I came back from the gym. I sat down. I turned on the season 8 episode 5 and Since I was hungry. I needed some post-workout snack I went to the fridge came back and you know that this season was all about it was very dim, right? So I was looking for the remote to turn the brightness on But I could not find the remote and I looked everywhere When I say everywhere I looked everywhere. I could not find the remote because I'm not sure what was going on on the screen Then After 30 minutes or so my wife found the remote in the refrigerator So Can you imagine what happened? So there was an imaginary box of possibilities which my mind created and That box contains all the possible locations where I can keep the remote shelf of the kitchen Couch corner of the couch behind cushion everywhere, right? Inside the fridge is not part of that box It's a brain glitch so if you in Terms of testing if you can go out of that there is no Clear way of going out of that box right, there is no clear way but You can at least try if you are aware that I'm not trying enough But you can make then then you can make a conscious effort All right, let's take this example Successful test engineers. I I have hired a lot of test engineers in past two three years But we look at if this is just my perspective you can disagree I think the person should be very creative online development where you know that okay You created a function. It's working. You wrote two unit s and You know, it's finite and Unlike development testing is more like an art Right, it's not finite you have to stop somewhere. So you can go on and keep testing a function for infinite long time, right and The second quality is persistence. He has to be personally if the developers would usually say it's not a bug We won't fix but if you think it's a bug it will affect the user then it is a bug, right? The third thing is keen observation Like my wife, she can find three more in the fridge, right? All right, let's say we are now building a system we are building a system Where there is a there is a Resource management system, whatever like an organization and the record of every employee in that organization Yeah, their roles can be developers You look at the role Is a tester the second one is also tested, right? The other roles can be developers managers Business analysts stuff like that, okay, and I am now a QE who has to test this API so they are saying that if There are four Boolean fields three Boolean fields is great Esther keen observation and persistent correct, if all three are set to true Then great Esther is set to true All three it's an and gate, okay All three are set to true then great history. This is the business logic resides in API. All you have to do is Send all three to true and see whether the person is returning us the greatest is returning us to correct Can you think of any other corner cases in this? Let's say you are a tester. You are testing this application Where you have been told that there are three fields Three quality fields right the objectives of a person of your employee if these three fields are true The great Esther Boolean should also be true. It's a logic business logic, right? Can you think of any other corner cases? Yes, please Come again Okay, so right so you are saying that eventually we will end up drawing a table Where we will choose all permutations of all these three Booleans, correct and see what other results Right for just one of the combination where all three are true The great Esther should be true for everything else. It should be false correct What else? You're still thinking inside the box Yes, please Not a Boolean good good thinking so she will probably send a free text right Free text ABCDFGH What else you raised your hand? Sorry, I didn't get you can someone can you give him the mic? Missing data free. Yes You just send the two fields and keep one as null correct. Yes, that's the good That's a good test But still inside the box Still inside the box What else think outside the box inside the refrigerator Yes, that's a good security test we can supply the HTML we can supply a special characters multi-byte characters, right? I Yes, yes That's the way to do it, but it's still inside the box. Now. I'll tell you in the interest of time All right, so As I told you there were a lot of other employees, right? Did anyone check that are we turning the CEO of the company into a great tester? Right. He's also a rule Are we turning a developer or a business analyst into a great tester? correct There were other roles which we did not look at so To deal with it. I I created this model Once you get a user story start from the line where code was changed Inside the code base and move your way up outside Like from the code base you go to text tag like there are different years, right? There's a back end there is a mid-tier and there is a front end Then you go towards users workflow. How does user look at it, right? What are their top 20 use cases while dealing with this application? This is not this is not something which is very practical because once you start doing it. There is there is a Risk that you will provide a very late feedback to the developers which is not Reside right because you're starting from inside and going outside All right Any questions so far? All right. Now there is a third kind of bias called urgency bias The urgency bias what it does is Let's say you are you are a developer working on something There's a bigger goal consisting of huge backlog So instead of PO deciding what to do if on a given day I give a developer a chance To decide what to do. He will eventually pick up the shortest users story first Why because There is there is an immediate High of completing the story There is instant gratification The longer user stories like which takes two weeks or three weeks It is wrong. Why you you want to do it, but it does not take you to your goal In a matter of day, right? So what this bias tells us is that we normally Fail to make the distinction between what is urgent and what is important Right, but we think is important is Actually very urgent to do and the otherwise also So I Will I'll give you my example. Let's say you are managing a team and You assume that they will do a couple of things and once the deadline Comes you see that two of those things were not done Then you talk to them and they say that I did not get the time to do those two things right, why is that Because of this bias They fail to prioritize things In a way which which was established by your team or you fail to establish a urgency or Priority of the things right in a correct way, which then led them to get hampered by this bias picking up things which were Urgent but not important All right, so how do we deal with urgency biases? One US president in I think 70s created this Productivity tool called Eisenhower matrix So what it does is it tells you to create these four quadrants As a tester, I will create these four quadrants for my daily jobs If it is important and urgent, I'll do it just straight away Right, if it is important and not an urgent then I will schedule Giving it a timestamp also that I will do it on let's say 4 p.m. Thursday And if it is not important but urgent you don't have the bandwidth to do it But it is urgent then you will delegate it to someone else You have to get it off your plate for someone else to pick because There has to be some accountability on the thing right And if it is not important neither urgent then probably eliminate it right Why maintain two different Sets of for example people who go into e2e bdd like they have feature files Everyone understands feature files Okay, they have feature files as well as regular test cases. There is no need of both of these things, right? So you can then eliminate one of it correct Last time I gave this talk In India there was a there was a joke on this slide We said that at one time US presidents were creating productivity tools, can you imagine all right any questions? Yes, please I have the mic here for the questions You Gave the example of if a dev dev has to choose between a bunch of things they'll do the thing that They can feel they can complete the quickest is that an example then of choosing something urgent over something important Yes, okay, thanks And that happens when there is a decision-maker who does not Who does not implement a Clear understanding of the priority of the things which the group is doing any other questions. All right, then I'll give you back your ten minutes