 You must all be wondering why are we even talking about this topic, automation testing problems? Is there anyone here who has been in such questions? So before we move ahead, I'd like to introduce myself. I've been testing from 2005. I recently started blogging in 2012 and I saw myself but from 2005 while I was working in my last incorporation or the startup, I saw that I was not following a process which they are just standing to follow or they were forcing me to follow. So I kind of felt myself that I'm being a rebel against this topic. But there were few things which I later and point in time learned that some of these are essential and this helped me become agile. So agile for me means flexibility in what I do rather than follow what is being said. So that is about me and I'm also the editor at womancustoms.com. I don't know how many of you have heard about it. We started this magazine in 2014 in association with testing circles, another magazine. And this is a portfolio magazine which also takes articles not just from the interviews but also contentment. We also have a guest post section where you can all teach people on the subject. And this is my blog address. Transits of testing can be found. Finally, there are writings on topics that interest me. And the problems that I face and most of your testing are at R&D. And I've seen people at Starbucks. You can see we have all been at ease with pictures of kids going here. So at home also if you have kids you will have found them doing something. Some surprising element is there and they are happy that they explored something. So how many of us have been in such situations in the span of your career? Found something and were happy. And you found something by yourself and not by the test cases that were written by others. So is there anyone here that were really happy that they did find something in their home by not following these tests separate from the others? What made you happy? You learned something new and that made you happy. How many of us are happy when we learn something new? What was it? What did you learn? Cycling, swimming, anything. It could be anything, right? You learned it for the very first time and were overjoyed by learning it. So I feel that testing is all about learning. I don't know what makes the money or where the money is coming from. I don't care about where it is coming from or where it goes to but for me testing is about learning. So learning about what? So even before we understand experimentally testing, let us understand what testing is. So it is very important for us to even segregate testing as easy automation testing. Some very new term that I heard today, we check up in your manual automated. I am still confused with all these terms. So even before we get ahead with experimentally testing, let us understand what testing is. Testing is about giving information which is valuable to your client or it could be any user. New Yorkers can be a user in this case. So how do you even get to know that I need to provide this information? What is your path when you are looking for information for the application that you download and start moving? What do you look for? What you are trying to do is you are trying to understand the product. You are trying to learn the product. That is what you are trying to do. You are seeking information. So how do we seek information? This is how we seek information. So more on the next slide. So when I was introduced to exploratory testing, they told me this and I bought it. And as you can see, when I might say, well, I am interviewing some testers. When I ask them what exploratory testing is, they give me some definition. I still can't buy it or it's all available on the internet and anyone can go and read it up. But still the definition that they give us exploratory testing is something that is done after your test case execution is done. So I would want at least two or three of the volunteers up here to come up and say what exploratory testing means. Anyone who has heard of exploratory testing has heard earlier as well that we said it was being done. So most of the things that exploratory testing is are off testing and I have even heard something about multi testing. I don't know what it is. And so, does anyone know what my key testing is? I think there was another definition which was about smoke testing, as you said. But I think you are in the right workshop then because it is not something around either one and not smoke testing. Exploratory testing is very well structured and as you can see, the term exploratory testing was coined in 1883 before most of us were born. And even today we are still finding it difficult to put it into words on what exploratory testing is. So doesn't this make you think that we are not trying to learn what it actually is and we are assuming our own definition? I think we are trying to do that. And as you can see, it is also an approach to learning and while you do that, parallely also you are trying to create the cases. You don't call it cases, but the term here is 5 yards. So when you start writing your test cases, you are told to write them and then you are asked to send it for review and there is also a sign-off. So after that sign-off is done, it is like a theme which is stamped on your test cases and not that you don't need that system. And how many of us have felt the need or the urge to add some more test cases or test ideas? And we are not allowed to do that. Are there questions? Yes. And the main reason for this is you are supposed to estimate. And most of us forget that estimate is just nothing but destination. You are just in the number and writing a value that you need to do these test cases with the amount of sign. But when that number increases or decreases, your manager or you yourself can panic. So here the approach is not about feeling and signing of these test cases. But while you are involving yourself as a tester, you start preparing ideas or leave them put it in a mind map or it could be on an extra sheet to be in there. So irrespective of where you capture them, you continuously keep adding on to them and you are not signing off and telling us over and done. So it's a parallel way of learning also forming your strategy where you learn and also test execution. So it involves all of this. And here are some myths about experience testing. As you said, there is one structure we don't know what we are doing but we are clicking somewhere and if we are lucky we do find parts and we report it. And here's one other funny definition that I heard. I was doing the same presentation earlier in 2012. Since then the definition has remained the same. So I asked the person what is the experience testing because they told me that it's something and if they have time. So the definition from 2012 to 2016 has remained the same. Even today I am interviewing people, testers and they gave the same definition. But it's not so. It has no test cases and there is no documentation. It's just again not so and we will see how it is not done. Here is another perspective of what experience testing is from Dave's point. It's about the X-ray v-test practitioner who is today practicing X-ray v-test and so on and so forth. So as a reference maybe you can join me. So coming to session-based test management. So this is the approach which is used or which is being followed to X-ray v-testing. So what is session-based test management? So instead of following a test case you come up with a mission for example it is also time-bought. So you don't test for 4 hours or 8 hours. I was in an organization, an inventory where you have been given the last 2 days for your friends, say if it is a 15-day sprint the 14th and 15th day you are testing and the first 13 days you are on different projects. How many of you? Because you have 3 from day 1 to 13. That's not right. So how about you? Are you free on day 1? That should not be the case. When you are involved you have to be involved in a trial again from day 1 to 15. But even I have faced that I am involved only day 15 and 15 and what I am doing is in that 15 hours you are running 120 test cases in data and you have to meet that target. So what do you do? You don't look here and there but just follow the test cases as you please. Even the test data is there in your test cases. You are not allowed to try any other different set of data. So you are sticking to that and a time being frustrated that when do I get to test what I think should be tested. So here is your chance to do that. And I am not telling that you can go and start doing this already but you know take this learning and maybe if it is applicable to you and if you can really think about this thing in your workplace when you can try this out. So session based test management you might be wondering what MBTS is this is for the manager some of them think that you are wasting my time telling you will test only in session whatever the other time model is. So this term is for them so this management based test they know that we are also managing these sessions and not wasting the other time that we have. It demands for us to understand what the mission is before we will start testing. So for example you have an application which you have to test. You start with the URL testing you type it and then you automate it and then it appears on the screen and then you click on it then you go back click back button or there is something else that you want to do. So for example if you have this first what you need to do is state the mission what you want to do if you just want to perform functional testing or if you want to perform door testing or something else you state that mission and then your time box you know that you want to finish this we will call it duration you know that you have you have a lot of time it can be come 15 minutes plus to 30 minutes or 45 minutes or 1 hour depending on how far you can go when you want to stop and these are maintained in something known as session box can I give it to my client is this the question that is running in your head anybody has this question something which you capture it could be in a notepad as well you state the mission and then you start date, end date start time and end time and then you start capturing what you observe what you see and how you know the bug ID and capture these bugs there and then at the end of the designated time you stop testing and then you do something how many of you eat even when you are full I want to know nobody right so why are we even testing for 4 hours, 8 hours without even putting rcc into these tests this was the approach that I followed for 7 years from 2005 up until 2012 I have answered the tests that were written by others and I was so frustrated I wanted to do something and I did get a chance to do and I did present the series of the bugs which I found which were not in the test cases first person how did you find it who told you to find it then I went to the client then the client asked why was it not found earlier and what the others were trying to do was they are following the test cases they provided the same inputs obviously they got the expected result here it gives you a scope to understand what you are trying to do and also after when you are full eating what you want to do you want to let your body convert this food into energy life so all that learning that we are taking you want to convert into knowledge and share it with others shouldn't we think that we should allow ourselves to let this learning deepen and then learn something else or what else can we do with this question log is it is a reflection of what a tester knows and what we need so as you are performing the test with this mission that you have said earlier on you might find that there is a security or your goal playing as a blind user and you see that there is an accessibility to further testing you may want to take a note of that and say that this is what I want to learn if in case I want to become an expert if I want to become a security tester or an accessibility tester so halt there and make a note of this in the testing so testing is not just as your manager says you are trying to do this and then by the end of the day you complete it and go back home and get your pay and that's it but most of the testers that I speak to have been telling me that just go board of testing they are doing the same thing over and over again how many of the teams here that we are doing the same thing anybody here is bad speed to speak of where I thought that is so boring I am doing what the test cases are run by others and I am not having the hope to do my own thing so that's when this came to my rescue and I started doing testing and setting a mission then I followed the steps that were but I wanted to follow and not something that is there in the testing so why do you want to do that this is an important question that I have for all of you do you also think that a developer also is given a guide and he follows it and does the same thing over and over again and he repeats it what he has in the department spec as you said similarly we also need to where we are not school fed like a new tester comes and everybody says let's give AP to him let's follow the test yes of course yes it is but also you need to give the tester to learn on his own and give us hope for him give a meaning to why he is given in this organization important frankly but take that boredom away from him rather than telling him telling him what to test given that purpose that is the mission why are we testing this how this information is valuable to the client or the user what we are trying to do is we have been taught that texts are our knowledge so you have been schooled that way and when you come to your workplace you still want to be educated in a similar way this was a revelation for me I don't want to be this I want to learn it myself and this was an approach that was like an eye-opener for me where I still then want to be given some book and told you know this is your limitation stick to the syllabus and not beyond the syllabus because the questions will come only from this so that's not the way if you want to learn and do things beyond what is there in the test also should equip yourself and leave skills to do those things so that is where this comes into picture so what else can your session notes be so at the end of 45 minutes or 90 minutes that you want to test you have tested and you have captured all the necessary information that you want to put it there and there there will also be an observation that you made what you want to do about that you want to go back and investigate it how many of us in that 8 hours stress that you have given in the last 2 days of your life when you want to investigate you are done for the day you don't even go and investigate it for them so you don't have that time so if you are a use this note now just to execute those tests but understand where are you or where do you stand as a test so as I said you are performing the testing based on a mission so stick to that mission during those 90 minutes that you want to test for and then after that 90 minutes end you have also made a note of choosing which you don't know of which you wish to further investigate learn further you can also use it as a basis for your learning any questions here anybody will get to that by you of course so if you are in a sprint cycle and then you know what are your requirements so during the first 13 days of the sprint you before you even get the bill to test prepare for what needs to be tested so you use it for writing test tests to capture your test ideas what you want to test about so in a sprint for example if you want to test subscription or unsubcription so your mission could be that test the subscription for the sprint base unless and until you are using this somewhere else out of your workplace for your own learning then the scope can be so the mission can expressly test you you are not limiting yourself after you have completed running a few set of tests and then do regression test and then do integration test approaching or looking at the product as a whole so with that vision plus this mission that you have after this I will get to what to do so why do we have to leave as we said once we are full we need to stop eating and then give some time to a body to digest and take so the session can serve as all of this with any questions regarding what can do with this session so your bug is also going to this report it can also serve as an investigation report your observations questions also going here which you can later take it up to the client it's like a journey you are going to the product what are the more factors to make an order test as a tester I don't think you should only be critiquing your product because you want to take an instrument in another product we can also do that as well so what do we learn by this I know that as a tester you are allowed to only log part and you have a system to log part and you are paid to log part and nobody is paid to log the work factor but it is a learning for us to take this learning and instrument to see that I saw the percussion working for this particular and clicked on this page it worked like this which had a beautiful message information on your hand subscribe now with this email id and the publication is valid from so many these are some information which is all by testing and you thought it was good to be instrumented elsewhere as well so you tap to them but the main focus of course is for you too, by the end of this note you have a bug reported which you may want to transfer into your reporting tool it could also serve as an experience report because you are not only tapping the bug but also questions that you have what is the morning or the rest of the day all this goes into this these we think can also like this is just I am talking from one test of perspective imagine that there are other testers in your team work testing the other aspects of the product it could be a different page or a team page or it could be pair testing that is testing together both of these are much different ideas so you can try that out and then you can also build your domain knowledge well working together then if you have this question this is applicable for a project or my domain is this and then you can try this it is left to you you can try and answer it for yourself whether you want to really try it out and if you are in agile mode of working then it becomes easy for you to even try and just because I am telling this you don't have to follow this but it is up to you to do your own thing and it suits you and better model as it is you have learned this you still want to learn more about it share up your links that you can go to and learn more about it these are just random bits that I have taken from top results from Google but if you want to learn further you can keep that and get to because as well as that I was introduced to this world of test until then I have my knowledge but so limited to my immediate test manager and the document before I it kind of docked me also from the outside world you have this document share you read it you understand and that's it but then I got to know that there is a world of testers outside of you every day adding on to this sign of test that you can learn from them as well I was also told by a friend of mine that you can use social media as well as learning me as a knowledge group Facebook or Twitter wherever if you follow or subscribe to write resources you can get to know this is someone who has tried it actually in her organization and she has written this article on how she tried and introduced this and this is the link this is not the last time but when people hear about this they wonder what is test early what is test early by the way by the role you are a tester what do you wish to do in the first day one to day 13 and what are your roles in the responsibility somebody else not paying what that early means to me so when I have been given the requirement I also am equally responsible for the product quality so I also test the requirement if there is something that I don't understand because the developers are asking all the questions you also are in the team and you can contribute as well so let's not limit ourselves to the roles just because we have been the goal of a tester let's not limit ourselves to that role but also test the requirement and then log all these questions in one of the clarifications of where I capture all these questions and it is always shared with the client whenever they can they can come back and fill in the blank sheet so there half of my work is done and then we start capturing the best and the last so before that we mentioned about design we also need to find those bugs early on why wait until for the design to be incorporated and then you know log 10 bugs you can have done a great job but it is of no use until we wait so the next print for all these changes to be fixed so why not do it early that is what I mean by that early that is the design as well you can ask the wife you can ask them as well as the design that page ask to the A&B prototyping as well you can also make those decisions but we developed those skills and mindset in order to help this why wait until for the product to be deployed and test environment for us to start acting like a tester so let's just early type in the requirement phase design phase and then even coding you can contribute there are many who are interested in coding as well you can contribute at that stage and then when you come to test what do you do I want you to do your testing here is an interesting point he said that whatever clarification he has he completes them all answered and coding and finding don't you think as you learn and go with the product we will have new testing so this is where the idea of you know the strategy where to accurately testing not telling them that they are already gone by then as he said they will not have further questions as the product goes in the shop definitely when you are integrating with other systems you will have different questions should it be here like the back button I am using this et al dongle at home there are three pages the back button is placed in the top right hand corner on the first two pages and then on the third page so as a user I just want to you know go to page 1 and 2 and page 3 has not yet been used like I don't want to even go to page 3 but the day I went to page 3 I realized that the back button is placed somewhere else it's like you are customing the user to click on our right hand corner and then on the third page suddenly goes somewhere else so this revelation came up when I tried to do something different so I can have this clarification coming at any time so that's why we have this clarification box which is shared with the client you can answer at a time of their convenience so did that answer your question have a specific question maybe you can be creative with it so we go to the interview I come to you for feedback the QA team or you also for call QA are you all testers as well with a free question to ask yes it is a free question to ask because quality assurance but for QA stands for right so why testers only are the quality assurance only testers are the quality assurance so here he is introducing another term gatekeeper it's a very challenging job right it's not an easy job we all agree that testing is not an easy job coming back to you know we are in a constant and we are talking about all this and we thought about this fact that when there is some error in the media projects why is it so why is it not a human error what is a computer error have you ever wondered what glitches and why it is associated with computers but actually it is a human error does it make sense what you are doing is for this to be a drop down so when a tester is testing this what he checks is again something which you think as for a gender example we are a female and you see it and then you pass it the same thing as Cripp does it sees that we are a female what does it do what have you captured as input values or what you should see as expected or how we see for it but when a tester, a thinking tester like everybody is a thinking tester recently Paul Seaman wrote an article on how we should not differentiate testers as thinking testers and not thinking testers we all are thinking testers so what do we do when we test we don't look for gender as male and female we also want to capture other gender so we add this value which is not there and then what if your drop down is so long that for example select country and you have a list of long list of countries so what happens when a user is there and he sees this page select a country he sees that it's a long list what is your script or the machine does because if the page is so long and then you know I have to crawl further down the machine is doing it versus a human is doing it for a real person checking because he sees something if the machine doesn't do that how many of us are we doing since we also have these roles like repeat testers or these skill sets this is the example that I could come up with is there anybody else who can come up with any other example I recently was attending a session and I was attending a conference and there was a talk about designing and this lady she was presenting she had 15 years of experience in designing and there was a website where in there was a username field and a password field and a submit field this was A and similarly there was a username, password and there was another field here instead of submit there was something called mismatch this is not something which we can train somebody else who can agree to whether this is good or bad we can't skip shooting so what we also need to inculcate and develop is this you know mind press when you say you are a tester you are also adding some value which is the reflection of your in the product so when you are testing and you see that two things are getting fixed in the product and then you see the final product you see that yes I can't do this you also get that you know the genuine value add that you are presenting in this case why I gave this example is because I was testing an application which was being developed for Dancers and we had this similar kind of login page where they said username, password and instead of submit we conducted another AB test like this and instead of submit we said let's jump so this was a page which was being designed for Dancers who entered dance competitions and all that they will do after the login and work for this company when you say less dance that brings the Dancer close to just to me or instead of rather saying submit if you add less dance it does bring a different value so these are something which you will understand when you start thinking from your own perspective rather than script or execute test that are written by others you may not agree with me now but when you see the result of this and as a Dancer if you really tend to get to use this application then you will see the result Managers who tell that you know by the end of this print I want 0-1 anybody? I have had such a growing up as a dancer nobody? the end result of software is not a perfect software and here is someone who proves it I don't know if you have heard about Freeman Dyson can you guys read this? can one of you volunteer to come up and read this? this is something very important which Freeman had to say I need a volunteer to come up and read this anybody? fix the mic please can we get out of technology without an enormous number of people it's a universal good if you look at biker's there were thousands of weird models built and tried before they found the bar that here the bar you could never design a bicycle theoretically even now after we have been building them for 100 years it's very difficult to understand just by a bicycle bar it's even difficult to formulate it as a mathematical problem but just by the trial and error we found out how to do it and the error was ensured you guys get the sense out of this does it even make any sense? so what we are told thank you so much when we are told you have to test this or build this product we all are given some set of requirements and we are running towards getting it right the first time building the right product for this it depends like verification and validation very famous question of the interview what failure means to us and what failure means to each of us whatever it means we know that we all are here for a learning we not just take a paycheck and go we could be doing anything for that matter so that's part and think over what we are here for what should we be even doing when we hear the term zero bar or a perfect software we really know such things yes we are progressing always not halting you are on the path of progress but there is no such thing as zero bar so the question to you guys the next time when you hear zero bar what will your answer be still alive because these are something which are not taught in school and you are answerable to your manager and they will ask you this question even buying the stuff that is doing the rounds when we call ourselves as testers it's in our capability to also educate this client because client is just one perspective of what you see as a product it could be the product owner or anybody but as a tester when you also develop this skill or mindset of some testing on different perspective you are more than one person it could be role playing as a hacker one day it could be extensively testing to be told and let's not limit ourselves when you call ourselves as testers to functional testing let's build this capability that provides quality when you say quality is not just sticking to the requirement of there are several things that goes uncaptured in your requirement of when I joined the testing I was told that even a test fail or a pass could also perform testing so I think what they are thinking when they said testing is an easy job I want to learn from you all what you think is surprising compared to testing time I just need three answers to take time to test so one day I took time out to actually write down what testing time meant for me and what all it covers the piece of this news here in the project field that is J-1-2-3 what you are supposed to be doing or what you are doing assuming that you are free is all this you are testing of course yes but you are also testing the requirement for many of you are testers more than you have but you forget to tell or convey that you are also investing your time and effort in this why I am telling all this is because when you next time go and estimate when you are sitting in a sprint planning meeting I need two hours to do this your manager should also be educated and they should know that you need also your time and effort invested in all of these activities so that they know that testers can be used on four or five different projects in a single sprint but rather use all 15 days of your time to do all of this what if you are automation testers here right when you call yourself as the automation testers I think you also learn what the limitations of the tools are you do them right and what you are doing when you are using the tools you are also testing the tools right say for example if you are testing the tool and you found the limitation you want to speak to somebody who developed this tool and you want to communicate with them do you also capture that as you are testing time most of the time it gets lost you think that this is out of my role or responsibility to do this but at least all of this is not so these are few things which you have to make a note of unless and until set your mind to write down what you do as a tester these things may get lost so this is when I took time out to understand that you know these are other things that I am doing as a tester which I am not telling my manager or I am forgetting to tell them and this is a trend which is followed from ages I don't know many people who will let their testers do more than test execution and test case preparation or automation so there is much more that to do other than all of this you are also clarifying your assumption while you are doing this and while testing you also do these activities and interaction also is a part of this so do you also tell that you want to further investigate so you need time for that and you also learn but do we convey this all all this while we are estimating and giving some random numbers how many hours we want to test we say 8 hours, 4 hours, 2 hours but let us consider this when we next test so that you know we are well aware of and the team or the next generation of testers does leave you because you forgot to capture all this and the interactions are very much essential it could be anyone from your client product owner to the user itself I know a friend of mine invites users, random users into our organization and she captures the emotions of the feelings that they are exhibiting when they are testing a product are they annoyed, are they happy or are they sad she calls it emotional testing but whatever name you know label it, you are interacting with a real user here and while you wait for a feedback to appear on your page and then realize instead ask for an immediate feedback by doing this it is also very much part of that and when I said knowledge sources let us not limit it to immediate feedback you are trying etc but go beyond and seek other reliable references so when I speak about this I recall an instance when I was testing with ISB there was a website which quoted that starting from this digit to this digit you can use it for books or other products I performed there was an error in that page itself so it was a third party and we were testing it and you could see that you know a product while you are doing all this testing you do not have to limit your requirements because it is not stated in the requirements they are not capturing as a bug so today also when I was at the bug there were a lot of people who came I was not against Selenium but on third party too how is this helping us all if those bugs get fixed then I will start using Selenium on different browsers and different versions so let's try and build our capabilities to an extent that we are not limiting but extending it to learn more learning, attending conferences is also your testing time sure I think you all have been marked present today so this is very much part of the testing time so let's experiment in time you are a tester you need a program so here it all goes you have a tester and a programmer they are not facing each other and they are given a requirement and so they are trying to convert it into readable code and if the tester is trying to resolve it and while they are doing it they are not talking to each other so this is the iteration one so one of you can both of you can you guys have you did read this exercise so I will read how you can take where it is test to get the drawing which needs to be replicated test to tell the programmer what to draw all its time so here is the first picture you need to explain this to him and he has to capture this later you will get to test this and you will tell him what to draw what to draw what to draw what to draw what to draw what to draw what to draw what to draw and you will get to test this and you will tell all this in one go so that he understands it and captures where they appear, how they appear and how close his code to your understanding anybody else who wants to participate we have another picture what involved right from the beginning you will get to see the results so now you I think you are coming to understand why it is important for us to be involved in all meetings and ask the right questions And most of the time, the manager tells, you know, since you're free, why don't you get into another project and start doing something else. This is just for us to realize that, you know, we are also as much involved in a project right from phase one until phase n and not just, you know, just for our role, need not be, again, limited to what we call ourselves or whatever SQA, QA, Quality Engineer, SBEB. Let's just not limit ourselves to this role and stick to what we are repeatedly doing. We are setting a wrong example for our future generation of directors. Many of them, you know, even I read it recently on, I think it was an, a blog, yeah, it was by Lalit, he runs the magazine called He Time the Tester and he wrote it on his dog that, you know, who becomes the tester or who are the people who are the, who want to do testing and why they want to do testing. It's basically someone who wants, who's been developing for a while and that's been frustrated, you know, long hours at work. And now things that testing is so easy that they want to do testing. That was one of the examples that she gave. The other example was a lady who has gone in maternity leave and she wants to come back and she thinks testing is so easy that she wants to do it. And there was this other person who had a computer degree and they didn't know, you know, to go but they thought that testing was the next best choice. Or they thought that, you know, you can make money while you are doing all this by not putting extra effort or as much effort as you think should be done. Another example. So we as, you know, test leaders or testers need to break this motion. And why are we not paid as equals with developers? I myself have seen, you know, it could be some random number, some number for developers and even testers hesitate to go up to that number and say that, you know, this is my experience and I need this number. What is your role, developer? What are you earning, some number? Then they assume that it's required for me to ask two lakhs less than that. So let's not, you know, degrade ourselves. Let's respect the profession that we are in. Let's learn to, you know, educate art which is a nation of testers to know what it actually is and what we should be doing. There are several test leaders around the world who are already starting to do this for people from India and not as well who are, you know, trying to do this. They're not doing this because their role entitles them to do it. And they're not doing this because they want to, you know, be famous. But they think that it is their responsibility to set up. So was this in any way useful to you guys? Say I, it doesn't mean that I personally have gone through these experiences because I didn't give scope for myself to undergo this torture. I was a rebel since 2005 till today. So when I suggested some changes or when someone told me to do this, I did questions. So questioning is so important. For example, I was new in the team and I was asked to perform some, do some performance testing. And the lead gave me some instructions. It was a room full of 50 people and nobody asked the question because they thought that this is coming from a lead and we all should follow this. But there are some people who love questioning and why do they love questioning? Because they want to know more. And what do they do with knowing more? What makes you, when you know more what it makes, it makes you wiser, right? So it could be that or it could be, you know, also there are several books and videos and tech talks on questioning and how you should question. So how should you ask questions? So why am I giving so much importance to questions is because questioning is about questioning the bottom. But you are, you know, it is under there. Why you are questioning in order to seek information? Why do you need this information to present to your client or anybody who needs this information? That's all. You are in the job of information business where you are collecting and giving. So while you are doing this, don't be scared that, you know, should I do this or shouldn't I do this? You are looking, you know, looking at a product only as to enhance the quality of it. So let's not hear or, you know, be overcome by any kind of hesitation to question. So if you feel that questioning makes you vulnerable or something, many people think that if I ask questions maybe I may be sad or someone bold and unapproachable or something else that you might have fear within. So there are a lot of things, the incident which you can read and understand, like some tech talk, art of asking. Just beautifully explained on how you should be approaching in several books written. So question and then do, just don't do. Arjuna learnt a lot because he questioned Krishna on what, you know, what he is trying to tell. He had a lot of questions like that. So his intention was not to, you know, gauge or measure the level of intelligence of Krishna but to learn himself. So this is what we need to make sense out of. When you question, you are not hurting your feelings nor you are measuring your success or failure. This is what happens in interviews a lot of the time. You are called in for an interview and people, the interviewers need to be skilled, you know, to know that, you know, we are not critiquing here or I am not allowing you to be low or keep myself high. So that is for the other topic. Can we see, can we see the picture back to now report about it? This is your perspective of what quality is. Let us call somebody else, not the boss. Mark it differently to that interviewer. So again, why I say this is her perspective of quality is because she is seeing from the skills, experience and the knowledge that she has. There is somebody who thinks high of, you know, what we see on the, you know, that has to be a discomfort for me. So the meaning of quality can differ from each person. Somebody can, you know, even fail all of the tests over there. I was saying till the end, really appreciate it. So what testing means to me is when I recently attended a session myself in Atthari. There were three testing gurus, Michael Bolton wins back and John back, the back brothers. They told me that you have to videotape yourself while you are testing. And they, you know, did I really even be doing that? And how does that add value to what I am doing here at Atthari? Tell me that, try videotaping yourself. Look at your, you know, how you are utilizing that time in a session, for example. Are you entirely, you know, focused? But when I was in that session, I saw that there was a lot of disturbance even to these three great gurus. People were, you know, kept disturbing, distracting them. And how they managed it. And why my last slide captures these points? I really want you guys to not just do testing, but perform testing. When I say perform testing, you also make a note of what you are trying to do. Try to put it in words. Example, like I am standing here and I ask you a question. Say for example, what is activity testing? I get some answers. If I ask an yes or no question, people mostly say yes or no. They are giving you two options when you have to select yes or no. And then you do that. But when I tell you to write it down, you start thinking from a different, go in depth and you try capturing it. So here's something that I did. Still have two minutes, but I think I can do this. I kept it to the end because I didn't want to bore you guys right in the beginning. So when I start, when I thought that I am coming for this workshop and you know, even before I start reaching about exploratory testing, I should know what it is for myself. And here is a note that I made for myself on what exploratory testing means to me. And I take this opportunity to read this out to you all. Here is what I have written. Explode the system under test with an intention to learn about the product. Learn by using the product as a user. Learn by questioning the status quo of the product. Learn by challenging the status quo of the product. Learn to make sense out of the product. Learn about who will, who can, who must and should, who would have used, who could use the product and how, why, when, where, how else can they use it? Why not and when and where else can they use this product under test? So are we even thinking so much when you are performing testing or are we just running the script or, you know, trying to perform, read out the test steps and the smart parts and things. There is so much more to use in the role of a tester that you can do. And that's not just that value to you, your profession, but in the eyes of you, you also can go as a stronger leader or as a tester. There's more that I have written. And maybe can share it with you on Twitter or elsewhere where you can read about it. So the intention of this slide was for you to realize that you are not doing testing, but you are actually performing testing. And who does well to do that? Observe every activity that you perform as a tester. Note it. Because you need to convey it to someone. Question it. Whatever you do, question yourself before even someone else questions your work. Why did you do this? Why did you perform this kind of testing? Why did you miss out this? Why was this found in production and not here? Do what is relevant and please don't do what is relevant to doing such a big time wasted. So feel that it's not in the scope of what you're doing. As in when you learn and try and capture all this, you will also learn that what should not be done and what you should not be teaching others to do. Define it and please share it with others so they can learn from your learning from their experiences coming this year. Thank you all.