How To Become a Full Stack Q/A Automation Tester - Inspiring Tester Story Complete Roadmap

How To Become a Full Stack Q/A Automation Tester - Inspiring Tester Story  Complete Roadmap

Show Video

See, I've also seen that some people have doubt that testing profile will be will not be there in coming years. Right! As a developer, I'm writing a functionality myself as well as the test cases. Means I'm unit testing my own functionality. And especially on front-end, there're libraries, chess libraries and other libraries as well.

So, I'm doing that. So, some people have this doubt that if the developer itself is doing this work then is the software testing profile.... I'ev a question from you, sir, even we do development, I'm working as a front-end developer and even you're doing development as well in the testing form. Give me a comparison, example that Ajay, this is our point of view for development and what you do is different.

Can you give us example? I'll divide the Automation tester into levels Level 1 - the one who can write a basic test case. Which consists of basic things like searching X path, CFS and clicking on any element basics and all Alright! So, Level 1 - Automation tester. Level 2 ... Specially for Automation, which tool will you recommend to learn, if anyone wants to start their career in Automation what happens is when you're working in a domain when you go for the interview in 3rd or 4th company and you mention that Sir! I'm working in Healthcare since 4 years & even they're doing the same then you get its benefit. Money wise as well. You'll get to learn because they're bringing expertise with them they don't need to give KT.

The freshers that're watching you, if they've started their career in software testing after how much time should he think about Automation. If he got Manual in the starting, for how much time should he work in Manual then you think that he should start thinking about Automation. Welcome to a new podcast! We've brought a software tester. He started his career as a Quality Analyst he started in a very low salary and his starting companies were - he worked in 2 product based companies after that he joined a service based company. Now, we'll get to know why he chose service based after product based. His domain was Healthcare.

He has an experience of 6 years. He worked for 3 years in Manual, 3 years in Automation you'll get to know about all the experience, his experience in software testing we've asked lot of questions, we compared his profile with a development role. Currently, he's working in a service based company as SDET. What does an SDET do? And how much code does he write while doing automation When is the right time for a fresher to enter into Automation? How much manual testing should an individual do? I've asked all these questions and I've asked a lot. So, watch this entire podcast. You'll get to learn lot of things. Like it.

Comment down. I've kept the like aim to be 5k accomplish it for more such interesting podcasts. Let's talk! With Rahul and understand his entire experience It'll help you a lot. Let's go! So, Rahul! Welcome to our youtube channel.

And I haven't talked about software testing for quite some time on your channel. So, we welcome you. You've 6 years of experience. You worked 3 years in Manual & 3 years in Automation. In total you've 6 years of experience

that is going to help our audience a lot. And I won't take much of your time. Over to you! Let's start first with your introduction. Your academic background where do you belong to Currently, which company do you work in and how many companies have you already worked in, please tell us to our audience. Then, I'll ask you questions in Manual testing & Automation. Please!

Over to you! So! Hello, Ajay! Thank you for inviting me to this platform. And my name is Rahul basically & I worked as an engineer for 6 years and I belong from Ahmedabad. And I did engineering from Ahmedabad itself from Gujarat Technological University.

And after that I started my career in testing profile. So, for the first 3 years I started with Manual testing. It was purely Manual testing & in the second company I started with Automation testing and currently I'm working as a SDET in the 3rd company which is a service based company. So, you can say that my journey is divided in 2 parts. First 3 years in Manual testing and second 3 years in Automation testing.

So, Rahul as you told in your introduction then, the starting two of your companies were product based and now you're working in a service-based So, is there any reason? Why did you think of going in service-based? So, you can say I wanted to explore everytime what type of environment is there. Which type of challenges do you face in service-based companies? So, that was the area which was un explored. You know, from my point of view, so I just wanted to explore it that what happens in a service based company. When people say they've less work or more work but I wanted to have a first-hand experience that's why I joined service based.

Okay! So, its not that when you went for 3rd switch, you were getting more money. Yes! That is also a part of the reason but you can say I wanted to explore basically. Okay! So, are you happy now? If you look at yourself today while working in service based, right! Then, if you compare it to the product based, so are you like fine with it or you experience some differences Definitely, there are differences but you can say, means I've explored that thing so, I find it quite good that I'm confident that I've explored in almost all the types of companies.

And the main important thing is domain was same. In the first company, it was Healthcare and it was product based this had Healthcare as well, so.. Oh! Nice! I got to compare them properly that what are the differences & you can say I'm quite content with where I am.

means the place where I am, I'm quite content from it. Okay! Nice! You told in your introduction that, you're currently SDET I want to know, as, its still a designation, right! Sometimes, people say that I'm a front-end engineer or Manual tester or Automation engineer Who are SDET according to you? Which problems do they solve in a company? What do you do as the SDET engineer? So, you know basically SDET is Software Development Engineer in Test so, ultimately they do development, as I do development in Java Language with Selenium framework. So, ultimately that is development but we've a different purpose that we develop to validate the software that is in front if us.

And the Java developers use Java to develop the software so, our purpose / end-role is different but both of them do development. And yes, as there's SDET ultimately, mostly he would be knowing Manual testing, then he would be Automation testing means Its very less heard of purely Automation testers everyone starts from Manual testing. And I would like to add more, SDET is - basically if I'm a manager and if I had SDET then whichever work assign to this person, he'll complete it with testing purpose, so be it the processes be it improving the process of testing increasing the scope of test case automation testing, manual testing, EPA testing whatever it is, I'll expect from that person and they would have team management skills as well, so that's flexible as well. Let's say he worked in other company as an EPA tester but current role demands him to be to front-end automation he should be flexible as well and the main important thing about an SDET is that generally, the ration of developers to tester is high as in my present company I think it is 5:1 or 4:1 so, handling the work of 5 developers, so he should be flexible as well. he might've to do 4 tasks in a day & that too totally different from each other like the cosmetic task, front-end automation task, so he needs to be very adaptive so, ultimately he's an all-rounder.

Very nice! Means I can say he's a full stack tester. I've a question from you. Sir, even we do development, I work as a front-end developer & you're doing development as well in testing form. Give me a comparison, example that Ajay our development point of view is this way & what you do is different. Can you give examples so that our audience is able to understand.

They should be able to differentiate what a developer actually does and if the tester is also doing development then which is he doing in! And how is it different from what a developer is doing in actual? Okay! So initially, as I told developer have requirements. So, comparing with those requirements they make their software. Let's say a screen was made but its our work is to validate that as per the requirement is it working or not Alright! And we don't want to validate it manually, our rule is to automatically validate it.

So, we make such a script which can perform actions means saving, deleting and normal actions. But the ultimate purpose of a developer is that it should work but there are lot of other things as well. Like, front-end, back-end, API structuring, Database schema so, we've one role that it should work as per requirement, developer has the same goal but means our goal is to find H case, how is it working from a user's perspective, right! So, these things are there.

This is the main difference. So, basically, what I've understood from him that if I'm a developer then I'll write a code for functionality and develop it, right! Now, I've a very emotional attachment with that code. For me that code will always be correct, right! So, we need a tester to test it either that tester would do manual testing by writing a test case regarding that particular functionality there'll be positive tests as well as negative tests in it. There'll be testing from every angle. Second option is to automate, where ........We'll talk with him now

where tools like Selenium exist by which you can automate and test for example, the test case is that user would be logging in so, is the user able to log in successfully? This is the test case. If yes, then test case has passed. If not, then it failed. The testing takes place in such a way, right Rahul! Am I thinking correct? Correct! Absolutely correct! Alright! I saw in your Linkedln handle that you've done database testing as well. As he told us, SDET is an all rounder profile. You get anything. Sometimes, even if you don't know you have to learn & then do it.

We would like to know from you in detail with example what approach did you use there? So, basically, you can say it was a requirement. As I work in a healthcare domain so, we get less access to a lot of things, therefore, let's say the mobile application that we're testing basically, from where the records were coming, we didn't had access to that application so, we had only one purpose that we test it. Therefore, we had to insert data through database. Right! So, my experience in it....

Firstly, I saw the scope that from how many sources is the record coming from how many application is it coming & in which form let's say there's a particular application which has the option to only create but doesn't have the option to edit & which fields are there like, data base is an open book. Ultimately, you can edit any value in any column or delete it. But, I made sure that I test only that which is in the scope let's say we had two applications in our case and both had different forms of data collected in it so, first I analyzed & broke down how the data is being collected which table is it moving to & in which form. I incouded that scope. If I would've done scenarios out of it like, there're lot of applications

that have lot of dependencies that you need email without that the application won't even work. So, if I would've written such a test case that - email means if I keep the email manual or anything else & then test it- then that's an invalid case. Which wastes my time as well of the developer & team, so I made it sure that I perfectly narrowed down the scope of what is there and what should I test. Then, basically, I've an experience in Sequel & Nose sequel. So, basically, I did that & I made sure another thing that there're lot of triggers as well, sequel jobs, so I talked it out with the developer asked him what is it, how does it work and basically why? Why do you require these sequel jobs? So, I validated all of it.

Trigger is like, suppose if a record entered in a particular table then it went to other table in come other form, so those are things that are inside that we won't get from the application so, I explored these things. And, you know sitting with developers and discussing what is it & how does it work so, I looked through these things. I would like to know one thing that here you did testing, but was it manual or automation? Things were.....

It was Manual testing! So, whichever test cases you wrote was manually written, right! For example, if this will be inserted then a trigger will work which will update. Right! This is one test case. This way you did data base testing! Guys, data base is an entirely different world in itself. And we can setup jobs as well. I setup that job, we set up data base jobs and now if suppose, the jobs will work then, if its a night job, then it'll take data from one table to another.

This is the work of a job. There're more such jobs written in database. So, he might be trying to tell, he tested in that way. He wrote manual test cases and then achieved through it.

Very nice! Please correct me, if I'm thinking something wrong. Am I understanding you correctly? You're trying to tell this, right Rahul! You thought absolutely perfect! Even if you're a front-end developer but you should've the knowledge of back-end. Sequel jobs... No, actually... When I was in my old company, I had full stack there. So, there we had support as well.

So, there we got to talk with the data base teams a lot. Okay! Perfect! You interpreted it correctly & thank you for explaining it better. NO! But we're getting to know a lot from you, Rahul. Now we'll talk and converse more! So, as...

We're talking about testing, be it Manual or automation testing. Without testing none of the product can go live, there's a lot of demand of testing in IT companies. So, if you want to become a software tester. Then, Crio.Do is a project based learning platform there're lot of course - Masters program In QA Automation where you'll be taught everything from automation to testing.

even the companies in today's date, that've web UI testing, API testing, performance testing, Dev Ops testing, tools like Selenium. all of those things are covered in this curse. So, this is their 9 month-course. If you take the free trail then after a week you'll be eligible for scholarship. with which you can get extra benefits.

Rest, their minimum package is of 5 lakh. And the maximum package can go up to 20 lakh. Their success related placement is 93%. Their average hike is 89% and they've more than 240+ hiring partners. Guys, this is the project you'll do here.

Because project is very important when you go for an interview. So, you'll gain a lot of confidence. So, I've given the useful links in the description, you can go and check that. You can take the free trail. You can think and decide on that basis. Let's talk forward.

So, as you said that you worked 3 years in Manual. Right! I would like to know more clearly & now you're working for 3 years in Automation Our audience is watching & as a tester everyone wants to go into Automation. Nobody wants to do Manual testing. So, according to you what will be the roadmap, since you worked for 6 years and you won't say anything casual When you were doing Manual, you might've been thinking that when will I be getting Automation, right! So, what should be a clean roadmap & now feshers are wacthing you along with experienced ones.

What advice will you give to them, that do Manual for some time because Manula is there & nobody can automate. Where you need manual intervention you'll need to apply manual there. Effort is needed there, even the ones who're automating are humans, he isn't a machine Right! So, what is your take on this ? What will be the roadmap if anyone wants to transition from manual to automation? Please tell us. The initial part of the question - Manual testing, so if I think now at this point If I would've been simply an automation tester, then I wouldn't have that quality in me. Now, why do people know the name of Rahul- they know me due to his manual testing. Even the current company that I'm working in I've been doing Manual testing since 6 years, so manual testing was very important for me and my profile.

So, I'll always suggest all to first start with manual testing then automation. Means as we say - cherry on top it would be the same thing, so I've experienced the same thing. So, when I did Automation I gained quite a good experience. Yes! Coming to the point of how I started Automation I'll divide it into 2 parts - Learning and Execution. In Learning phase - firstly you've lot of things with you like Youtube means there're lots of videos, websites. I started in a smilar way as well but

basically I got stuck that where should I start from I studied one article but it was unrelated to other article so, I used to get stuck that what should I do? Right! So, Ultimately I sat one day and narrowed down that there are 4 options these are 4 resources from where I can study I prioritsed it - 1, 2, 3, 4 I started with the first one, so I got so much of confidence that this resource is good for me & it'll guide me on the correct path. So, I stuck to that. Neither did I study any article nor any youtube video I stuck to that only. Alright! So, if we want to switch from manual to automation, then its important to stick to one particular course. Then, Execution comes.

While executing, its very important to -- I'll divide Automation tester in 3 levels Level 1 that can write a basic test case to log in so, basic things come under it like finding X path, CFS then clicking on any element, send keys and all. Alright! So that is Level 1 - Automation tester. Level 2 Frame Work Level we've 10 test cases but how can we run it in optimal way. Which frame work do we've to use and which not? If not, why? If yes, how? So, there are frameworks like Cucumber that you can use So, this is 2nd level and 3rd level is CI /CD Pipeline like Gen Skills, Azure DevOps, So, you should go in these 3 levels step by step.

If you'll think from the first day itself that I want to make CI/CD pipeline on Azure DevOps. Then definitely you'll be confused and won't be able to map. So, its very important that you go step by step Alright! Don't jump directly on any step and follow one resource. Yes, I would like to add one more thing. I did the same course twice. Firstly when I did it, I didn't note anything down. I didn't have anything, so whenever I used to be in that situation that I've learnt it earlier.

So, I couldn't remember it properly that I did study but how should I implement it. When I did that course 2nd time, I noted each and every detail & I have that with me even today. Now, if there's nay scenario that I need to look into it, then I just have to open a particular sheet navigate it and I've written it in my words so, I'll be able to directly map it so that was very helpful for me.

Now, specially for Automation, which tool will you recommend to learn. If anyone wants to start their career in automation? So, which tool should they start from, it would be best for you in future for automation career growth As per the market trends, if I take the data for last 10 years then Selenium has been the king of Automation testing. So, if anyone is watching from audience then I will suggest that they should start from Selenium because as there's Play wright, I had tried it one or two times as well. but many things got simplified in it. The things that you struggle within Selenium for setup, even for basic setup where you need to bring chart files.

Alright! So, you should learn that, if you directly jumped to such tool that is easy then you won't actually know it, you can go from difficult to easy but then you'll face comparison let's say Selenium has been working for 20 years and this Play wright / Cyprus went on then it can be that scenario therefore Selenium is a little tough. As compared to Cyprus and Play wright So, I want the audience to follow it and start with Selenium basically. And if anyone is interested in mobile, which tool will you suggest for him? I haven't explored much in mobile but I have done Appium so I've explored only one tool. So, Appium is ten times less used than Selenium because there's so much unstability in it. There's less support so the build remains unstable in it.

So lot of errors occur in it. So, I've only explored Appium therefore I can suggest that only. Okay! But yes, initially If we talk about web then Selenium is suggested. Yes! Correct! Okay! Rahul, I've also seen that some people have doubt that software testing profile will be will not be there in coming years. Right! As a developer, I'm writing a functionality as well as test cases myself. Means I'm unit testing my functionality.

And specially in front-end there're libraries - Just Libraries and other libraries as well. So, I'm doing that work. Some people have doubt that if the developer itself is doing the work then software testing profile will..... No! Definitely No! Because as much as I've worked, let's say I'm an automation engineer so, I Automate as well therefore as new features arrive in existing software or if new software is made then let's say a new software has been created & I think depending on the scope of the software Automation testing isn't not possible for 2-3 months if you'll automate something, the design will change, requirements will change accordingly. So, you'll come back at ground 0 so, only manual testing will work in it.

Be it new features in existing software or new software altogether and I think I've worked 6 years in new software so, I know the struggles that If I automate something from my end. And let's say its design changes the next day, obviously because of the requirement as we're in the development phase. So, it means I cannot even say anything as, it'll be very costly.

When we think from the perspective of the company such things because automation is definitely costlier so, manual testing is done. Alright! And second main reason is, Developers. Its not that developers will stop making mistake. Even they are humans. So, as new features develop, its not that they'll develop according to the requirement so that's also a reason.

And yes, the automation scripts that we write, is ultimately a machine. Right! And the machine will do what we'll tell it to do. It won't have any common sense, right! So, common sense & logic comes from manual testing.

One person thinks that, while sitting in one corner of the world a person - 50 years - old is using this software, then how will he be feeling these things doesn't come from automation testing, so manual testing.... Manual testing will be required as the development increases You answered perfectly. Rahul! And yes guys, very important, software tester isn't going anywhere.

As there's developer, there's a tester. Now I'll talk about the salary growth as well you earn money in both, sometimes the tester is earning more money depending on their experience and switches. Okay! So, tell us as you mentioned in your introduction that you've worked in healthcare you were lucky Rahul, that in the starting product based companies that you were in there you were in healthcare and now you're in healthcare even in service based. Did you think that you want to be in this domain? Sometimes, it doesn't happen because as earlier I was in airline domain now I'm working in Adidas, things are totally opposite. So, didn't you switch due to this in service based that I should go there since its healthcare. Was that the reason? Yes, definitely! You can say that because, I had very good domain knowledge.

So, I was inclined towards finding a healthcare company because I wanted to use my existing knowledge & experience, basically there's a terminologist Alright! So, it can be beneficial for the company that I would join and for me as well In terms of me knowing the domain quite well. So, as soon as I joined this company they were using the basic terminologies that I already knew from the first day itself even I knew ten times more than them. So, I used to put forward my points confidently I definitely know that there's another angle that I should explore something knew but I had a plus point that I used, you can say See, let me tell you another reason. He hadn't told this but I'll tell that.

What happens is when you're working in a domain when you go to give interview in 3rd or 4th company and you mention that - Sir, I've been working in healthcare since 4 years and they're also working in it, then you get benefits from it. Money wise as well. You'll get to learn as he's bringing the expertise. They don't need to give the KT as they know how healthcare works.

Then, this is also an advantage that sometimes you can play well on the basis of domain. And if the skills are a little bit here & there it works. Sometimes, when people are retained in the company, the skills are fine they've a fine knowledge of domain it gives them an advantage. Now, sir tell us the future scope of automation testing according to you. And salary wise, although I've talked about a lot but what is your take on it? That how do you the salary growth in software testing profile.

Right! Then, be the job in manual or automation, it depends on each experience but what is it? What'll be the future scope in Automation testing? Please tell us. So, basically as new technologies are emerging like AI, ML, Blockchain I've heard about them as well but currently in mind what is it and how is it done? So, the advance technologies that're coming So, the developers would be advanced as well. And to understand, analyze & validate the advanced developers Right! There's the thing to develop, validating it, right! Means I need to review it, then the software tester needed should be equally stronger. Right! Its not that he should verify anything rubbish. Alright! So, there're such technologies in the market So, these are the things which increase the scope of testing and the level of testing is increasing comparatively day by day As I've experienced it myself, the first company I was in, the features that I tested and the features that I'm testing now is very advanced like there are new technologies, as there're different technologies that're developed, so this is the main reason with which everyone's growth will increase. Be it BA, Designer, Developer, or Tester Okay! And what about Salary growth, Rahul? Yes, definitely! As there'll be salary growth because as I told that level will increase, you would need expertise.

Now, such people have decreased from the market who had worked on block chain for development purpose. And there might be very less in testing as well, so if the company has decided that they need 10 people in any case then they won't pay attention to those 10-15 people when the question comes to salary So, definitely. Its hand in hand as the level increases of development and testing, as the level of testing increases, salary increases simultaneously.

So, Yeah! Okay! What I understood from is that - if the technology is changing, you're also changing yourself with it, then testing scope will increase automatically. That when technology will increase, developer is enhancing his knowledge, developing the app then the tester is doing that as well. And he's testing it, supporting it, maintaining it therefore, automatically you'll have growth. Rest, as you switch, those experiences build them up. If you don't switch then you'll keep sitting at 5 lakh that can even be for 5 years.

You can even reach 7 lakh. But if you switch, you can reach 12-13 lakh or even 15 as well by countering. Alright! Rahul! it was nice getting to know you 7 your testing experience. I talk with lot of testers every one of them have different experiences. And your experience was different in itself. Now, as you go, since freshers are watching you, experienced people are watching you what will be your advice for them, if they want to enter into the world of software testing and make their career? Please tell us.

So basically, first & the most important advice with which means I am me, Rahul is Rahul due to his logic, so stick to the logic. If anything is coming logically & we've to see that be it experienced person or the ones who're aspiring in software testing we need to stick to the logic, right! And secondly, crack WHY for each thing. that why is this thing. Why has this thing been developed or the new thing that we're developing why are we developing it in this way. So, become a small child, ask questions. A normal human being will validate it but

become a small child for the time being that why is it this way, ask if you don't understand ask 4-5 times from whoever you want to. because more the questions, the more we'll grow and in the initial phase things will be validated. Let's say, it was developed later on. Then it was validated, so the cost will increase as we'll have to repeat the entire cycle. And the most important thing, designers have the design. Developers have the code, BA has the requirement document.

We've our voices, so we should raise our voice whichever product we're working on, assuming it to be our own let's say, I'll share an example that if it would've been my product and I would've been spending money on it then which type of product do I want? Work while thinking it as your own product and then the team has to work according to priority its their call, means every team has its own call according to the priority. Its the clients call, definitely. But you give your 100% Raise your voice because we've these things as a tester, so we can showcase the manual testing, automation is also the code, but as a manual tester You should raise your voice, take good suggestions and assume the product to be own & then take suggestions so, this is it! Perfect! As you go I would like to ask you a question, the fresher that're watching you might've started their career in software testing after how much time should he think about automation testing? If he got manual in the starting how much time should he work in manual, then you think that now he should think about automation? So, there are 2 cases in it. As I'm working on such a product which is good I'm working with such a company, such a team which is growing. If this is my case, then 1.5 -2 years is the perfect time.

But, if you got the confidence that I've explored manual testing that I had to do. Now what should I explore? When this question arises in your mind then switch to automation, ideally its 1 and half to 2 years. You should do manual testing for atleast 2 years. It was nice talking to you, Rahul! Thank you so much for sharing so much of your experience.

I personally believe, guys, it'll help you a lot. You'll get to learn a lot. And thank you so much Rahul for coming. And guys, if you loved this podcast, then do like it. Share it & comment to the most what you all think if you've a question in your mind, then do comment it down. And mention what interesting did you find in the podcast, Rest, I've kept the like aim to be 5k, do it for more such interesting podcasts.

I'll meet you soon next in any other interesting podcast. Till then, take care! Thank you so much!

2023-05-16 06:42

Show Video

Other news