Deepak kumar

Basically, I work at grid. Currently, I'm working at grid. I have, like, total 5 in both back end as well as mobile as well as web testing. I started my career at Kinvey Technology, uh, formerly known as Covium Technology. So I started as an a manual over there, and then gradually move to, uh, like, uh, like, uh, gradually converted to software development engineering test. Uh, so, basically, my day day to day job over there was, uh, like, testing both mobile as well as back end, back end APIs. Uh, I used to handle some of the back end ports over there. Then I moved to, um, Baidu's technology where I was a, um, mobile as well as web automation engineer over there, and I learned mobile mobile as well as web automation over there. Then gradually, uh, after after that, I moved to Navi Technologies in 2021 at December, and I worked as a lead as the SDET over there. So after in in in February 2023, I moved to great technology, which I'm currently working over here. So, basically, I'm currently, I'm leading a port, which is a win port. So this is it this is a port for playing games inside the CRED app, and we, like, give rewards to the user who who, like, whoever wins inside the game. So, basically, my day to day job over is handling the port features, all the features that are coming in the sprint and as well as automating all those scenarios, uh, for mobile app as well as as as well as

Uh, we we have used, uh, Jira technology. So we used to create tickets, uh, as well as we I have used, uh, like, uh, Confluence mostly also. So we used to create tickets, and those tickets used to go to develop, uh, different development, uh, cycles, like, uh, different site process cycles, like development to the product manager and then finally coming to the QA, and we used to close those tickets.

Black box texting, uh, testing is generally we can say that, uh, the when you don't know the context of the code, like, uh, if whatever the if you know what is the code, and then it is called white box text. And so, basically, if you are doing, let's say, q unit testing, it is a white box texting because, uh, when you need testing, you are annoying what the code is inside the development inside the development code. Uh, it is done generally in inside the development code, while this white book text texting. Coming to the black book texting, we consider that the regression testing, smoke testing and what it is called sanity testing. These kind of testing are like a black box testing because we don't know what the code is inside the double code is there. So, uh, these are black box

So, basically, I have worked with product managers as well as development team. So, basically, uh, we used to grasp all the testing scenarios, what output of the product is and how it is gonna, like, uh, influence the customer as well as our business values. Then you we used to write the test cost cases, and you'll be used to Get it reviewed by developers and as well as product managers. And after the after this, we used to constantly check Or, like, uh, we used to give some improvements, uh, in the product also, like, uh, or knowing the product Product architecture, how it can be faster, how it can be more better, uh, when it is coming to, you know, use users You just perfect perspective. Sometimes you used you used to get, uh, like, missed by the product managers and developers. So we used to add some values over there. So, basically, uh, like, I can say that, uh, I have mostly worked with, uh, like, product managers teams and as well as, uh, developer teams, mostly with them with them and used to, like, work on the whole release cycle as well as after um, even after the release has happened, we used to work uh

The Okay. I'm not aware of this Industry standards. Um, what is

Script language, I used Python before this. We used BDD for making the framework inside for Python And we used Selenium and all in Python only. When it is coming to the script language, I am also well aware in Java. So we also use TestNG as well as Java, uh, and Cucumber, and let's sorry. Or in Selenium, Nappy, and or test Java. So Python, when it is coming to script language, I use Python mostly.

Uh, basically, uh, if the all the p naught, uh, p 1 and p 2 are covered, uh, and user is not blocked. The when it is coming to the product, user is able to use the product, uh, then we can say that, uh, our product meets the regulatory compliance standard. So, basically, uh, in our current company, if the UAT, your acceptance users, acceptance test scenarios as well as some p p ones are meet met, then we are, like, we are okay with their compliance standards.

From scratch. So, well, it depends upon what type of, uh, what type of, uh, the framework we are developing. If if it is a back end only, so we will better approach it by, like, uh, how many services are being called inside this, uh, like, how many services are being called and how many teams are uh, working collaboratively, uh, inside the this framework. So the these 2 things are they're, like, most basic things, and how many API calls, uh, like, how many services and do we need database access or how will be yeah. Like, we'll be evaluating the uh, truth, uh, truth cases, like, uh, if something is coming from the response, how is it how is it expected to be? Uh, so, basically, we will try to model modularize all these things inside our, uh, inside our back end inside our back end test framework. So basically, uh, when it is coming to UI, when it comes to UI, uh, let's say mobile, we will develop a try to develop a framework where it is, like, uh, both mobile and UI can be handled inside in the same framework. So, uh, we can create, uh, like, interface, uh, which can be, uh, like, which can be implemented by both mobile as well, web, and all the scenarios, which are same in mobile. And web uh, should have different methods when come come when it implementation method, when it comes to, uh, when what do you say? From web and mobile. So, basically, all the implementations will be the test cases will be same, but the implementations will be uh, for both the things. So, basically, we try to, like, uh, develop a framework, which is

Security. So, basically, uh, in terms of QA, Basically, the most important thing is, like, learning what's happening around the globe in terms of QA. There are many such things, like, in in AI also, we need, um, a lot of QA. Uh, and now there has been, like, a very good notion coming over here for AI Testing. So for, like, model testing, what are the models being developed? So big basically, the plans would be, like, we learn and develop because this is a, uh, like, Very new field when it comes to QA. Uh, it, uh, technologically, it is growing very newly. Like, it's a revolution inside currently, it's a revolution inside, um, the way, uh, QA. You can see it. So, basically, uh, we should learn and grow according to the current industry trends. So, basically, we should try to, like, implement I keep trying things, implement things which are coming in the market, and see what

So, basically, uh, role of QA is the, uh, like, is one of the most important, um, role inside the development and the process in improvement. It is because mostly because it ends the, uh, the development prop the product development scenario ends with the QA, and QA are the, like, you know, owner of the product after it is developed and, uh, advanced to the it goes to the users. So, basically, we can say that, uh, like, we are the holder. The QAs in India are the holder of the product. Uh, like, it should it should not be breaking after that it is related. And it generally starts with the business team and product managers, and it ends with the QA only. So we like a QA is has a very important role in product development cycle, and notice the role of QA in engineering process improve. And when it comes to process improvement, uh, QA has a very different very good role because QA interact start from the beginning of, like, uh, when the product is being made and all the portfolios for the product and new designs are being made. Then only, like, QA process, like, QA can, uh, will can try to be mediator between product managers and uh, developers. So that that are time time as well as the efficiency of the process can be mitigated. So, uh, basically, uh, Qwik do handle all the process cycle, and it can miss mitigate a lot of if like, it can increase a lot of if you can see as well, it can mitigate a lot of

Yes. Like, I have I have worked in a load testing for a service which is game a gamification service. So, basically, we used to have a lot of like, we used to have an event called 10, 10, 11, 11, 12, 12 in my first company. So, basically, what we used to service. Like, we you, uh, we used to create events. So during those events, like, uh, even, like, 10,000 of users We are simultaneously playing the games. So we used to check the number of ports that need to be there. Uh, like, it needs to be installed um, for the system. And any parallel ports needs to be installed in this for the system to handle those, um, and those number of, uh, current current users. So, basically, what we how we used to do that, we used to hit, uh, create in inside our, uh, QA environment. What we used to do is, like, Here, the number of ports used we used to check the performance of the, uh, port when we actually used to check the eligibility of the user. Uh, you then used to play the game, And all the process used to be there, uh, making the replay of the actual production environment that used to be inside. In in case when it was, like, in case, uh, when it it was the production, uh, was going on.

I have worked on GitHub workflows by creating, like, automated automated automated, uh, triggering of automation scripts. I have worked on Jenkins as well. I have worked on GoCD also. I don't have much experience in GoCD, but uh, used already configured GoCD pipelines. I have configured GitHub workflows myself only. And I have worked on Jenkins uh, Microsoft only. So, uh, I have created many pipelines in Jenkins using, uh, and I have worked on AWS also.