[Music] hey guys welcome to resting academy my name is pramod and in this video we're going to talk about a very interesting topic which is what exactly is exploited testing how to do it properly and i'm going to show you practical example how to test a particular web application suppose there it is given and what are the different tools that i personally use and that you can use also and i'm going to show you some practical example where we will be testing a particular web application and we'll basically noting down exactly what we have found and that will help us to understand better what exactly is exploited testing and they're different to it with practical example all right so let's get started i'm going to give you one download link also a particular guide about the activated testing also in the end so make sure you watch till the end all right so let's get started all right so before we start guide i just wanted to give you that if you want to become a better qa if you are someone who is basically trying to switch from manual to automation or if you are serious about the automation testing do check out the different playlists that i have created it's a 30 days list trust me you can finish them in probably seven days if you are serious about it it's basically i've created 30 days of automation testing uh selenium with framework with api testing postman as well as i just showed karate api testing right and all of that you can check them over the sd dot live slash 30 days so make sure you open that link and subscribe to the channel and make sure you pay attention all right so let's jump into the video all right so uh first of all the question is what exactly is a exploited testing right if you uh if you know what uh exploit testing basically comes from a person with basically the cam kernel who basically coined this term in 2000 uh i think it's very old it's around 25 years back right he has coined the term it's basically a style of software testing where if you see they emphasis on the personal freedom and responsibility uh a individual tester basically try to explore the application by and they don't have any kind of a requirement for the for the application so basically uh they will be given a particular web application or it can be another it can be any kind of application right they will explore it and uh based on that they will basically have uh increase their understanding they will learn from it and they will note it down what exactly they have done and uh it will help them to find the bugs early but the problem sometimes drawback is that since you don't have requirement you will understand a certain feature as a bug right so that can't be the issue all right so uh let's uh quickly jump exactly with the definition of the exploratory testing which is very important sometimes people ask you this interview right it's basically a style of software testing that emphasis only personal freedom and responsibility of an individual tester to continue optimize the quality of his work and traced and treating test uh test related learnings test design execution so basically it basically means you are provided with a application right suppose it's a web application right you will learn that application you will basically understand based on your previous understanding you will understand it you will explore it you will play around with the application that will show in the practical example wait for it and based on that you will basically design your test case and whatever the learning that you have you will note it down if you find any inconsistency you will note it down as a bug right so there may be a chance where you uh it's a feature but you are understanding it as a box so you can do that right or in the agile models it basically means discovery investigation and learning what you are doing with the product right exploited explore the system while testing in a very simple manner right and sometimes it is also called as on the fly testing right there is no test case right test cases generally are determined during the test case when you're doing it right you will determine it focus is only exploring the application that's it so you will provided a application you will just explore your play around you don't do monkey testing which is basically click click click click no you will understand for example let's say uh crm right it's a particular for example a user is created right there's a particular form right you are basically trying to understand what exactly it does right what are different fields how they behave when i do it so you are exploring it learning it right no requirement i would say there's uh sometimes there's no requirement that there is uh there is known as very less requirement if someone is saying there is no requirement it doesn't mean that uh it can be like it can be very have very less requirement in that case right check the functionality in a very ad hoc manner right objective is very simple it's just to find bugs early right so that's what you want it's an approach not a technique okay so make sure you pay attention and according to the atlantean which is basically a very good tool which provide test management tool jira and other things uh it's exploited testing is suited for the specific specific testing scenarios such as when someone needs to learn about the product so if you want to learn about the product you can do the exploratory testing in that case okay so i hope that is clear right now that you have in a very simple manner it's just about discovery investigation and learning about the product that you are doing and finding the box as quickly as possible okay so what exploited testing is not it's not a random or a mecha testing okay so make sure you pay attention sometimes if you do click click click you do stress testing that is different thing it is about learning discovery and uh investigation okay how to do it uh prepare notes it's very simple you can have a time box where you will just have a session base for example i'll take 60 minutes i will explore the application i will create these are things that i have done and i'll note it down the box straight forward right learn observe and then come up with the new test cases that you can also do practical example i'm going to show you the same simple example right uh tools different tools you can use for fluid testing it can be bug magnet right so let me show you what but exactly it is these are basically some chrome extensions uh let me see if i am able to open it okay okay [Music] right so okay it has open so bug magnet is basically in chrome extension i believe yes so you can basically use it uh and there are a couple of like free uh there's a video recorder that you can use to basically whenever you are exploring the application if you need any kind of uh if you found certain bug you can uh basically present to the developer exploited testing chrome extension that you can also use uh spira capture exploratory testing tool that you can use so you will find these links in the description so make sure to let's be download before uh jump into it i'm gonna show you the practical example okay so let me move myself here let me make a little smaller so suppose this is a orange crm okay this is a crm application and here i'm basically adding a new user okay so this is the application that is presented to me and i have to do explorer testing right so what i have understood is that so i'm i'm going to use the test body it's a if you know it's a session basic testing for exploited testers so what exactly is happening is i will just note it down i will do this testing for 10 minutes and in the planning i just noted down that i have to test the application this application so i'm going to just open the uh i can add my nodes like testing uh testing this link okay that's a very simple way and now i start exploring and i had a time and note so i just noted down what exactly i have found okay so if you see i have opened my developer tools also so what i am i'm able to find is that if you hover over it here i found that it's it's a form and there's a post request the form name is fr system right so i'm doing exploited testing and i'll just note it down that note session has started so basically now i can mention that okay it's a form this is i have explored the application right and this the name of name is uh so i have given name is this right and it's a post call okay so that i have noted down now i'll just mention that okay this is the name so if i do this if i do if there's no found i'll get this employee doesn't exist so i have explored the application and learned that it is giving us error if uh use if we are not able to find any user right and it's a required field so i can mention that here so at a note that employee must exist and known exist employ uh gives error okay so something like this i'll just keep on adding and i can also add media for example suppose i have taken some screenshot i'll just add a random screenshot right now and this will add a screenshot also so this is my exploratory testing going on it's a session based and if you see uh i'll take 10 minutes to test this application and i'll basically figuring i am just learning about this application so username i can take any username for example if you see uh a it's it should it should be more than five characters so i have explored the application and figure it out right and let's see how much how much it can take so if you do you can see the maximum character also see let's see if they have maximum so they have max length of 40 right so let's do one thing let's copy paste and try to save it uh so we can use a suggest part word and see right so it's saving right so it is working fine so i have saved successfully so let's do one thing let's quickly add another so that's what the eventually you got the point right i mean now let me make myself little bigger so my point here is that very simple you are just exploring this web application right you're learning about it how to add a particular person and you are basically figuring out what are the required checks what are different things are there how if we are able to add the add it or not if you are not able to add it like what are the api requests going on so if you see in the network tab uh suppose i have entered uh suppose i have selected this username any this so it's giving us already exist right so i'll just enter a few things so just a strong password and i'll just add uh qqq right and if i hit save so if you see there's a particular request going on right so that request that you're able to see for example the request was save right save user right it's a post request uh where you are sending these information right so that's how i'm exploring the application and i'm basically noting down somewhere like what exactly i have found okay so this is a wrong uh wrong uh i mean say photo but uh eventually you get the point right so you'll just take the photo and add it so that's exactly is how uh the so exploited testing works okay so what are the benefits it it basically means you need less preparation because you are eventually get it directly you will find important bugs whatever the different bugs there uh it's very intelligent and simulating uh process uh detective reasoning based on the results so you can deduct the results what's happening so i have added a user right now if i use another same name it's basically saying that it already exists so i have basically uh know that okay based on my previous data it's basically responsing responding back uh most of the bugs are discovered in some top exploited essay most of the time the disadvantage are that the tests are intended and performed on the flies so they cannot be reviewed so it basically means i'm testing a little exploratory way i'm not going in a scripted way step by step right i'm just testing here and there and just says adding it so uh they can't the test cases that i'm writing are can't be reviewed but only my session can be reviewed that i have tested this as exploring the application right i would suggest download this guide about the exploited testing if you want to know more about it i'm going to give you certain more links in the description make sure you check this out okay so that's what all about starting getting started as explorer testing and doing it with a practical example i hope you have learned something new all the links are in the description you can download the mind map you can check out how i've done it using test body or you can use other tools like for example it can be a simple video recorder duck magnet another tools like for example exploded testing chrome extension or speeda capture to basically capture all the details for your exploratory testing all right session based i mean thanks for watching i hope you learned something do make sure you if you are new to the channel make sure to subscribe right now because i create lots of awesome videos about software testing and development right and uh make sure you like the video so that it helps algorithm and it'll help other people all right thank you for watching i'll see you in the next video thanks it's your host pramod welcome to the resting academy bye