Deepak kumar

I work at Grid. Currently, I'm working at Grid. I have total 5 years of experience in both backend as well as mobile as well as web testing. I started my career at Kinvey Technology, formerly known as Covium Technology. So I started as a manual tester there, and then gradually moved to software development engineering test. So, basically, my day-to-day job over there was testing both mobile as well as backend APIs. I used to handle some of the backend ports over there. Then I moved to Baidu's technology where I was a mobile as well as web automation engineer over there, and I learned mobile and web automation over there. Then gradually, after that, I moved to Navi Technologies in December 2021, and I worked as a lead SDET over there. So after February 2023, I moved to Grid technology, which I'm currently working here. So, basically, I'm currently leading a port, which is a win port. This is a port for playing games inside the CRED app, and we give rewards to the users who win inside the game. So, basically, my day-to-day job is handling port features, all the features that are coming in the sprint, as well as automating all those scenarios for the mobile app.

We have used Jira technology. We used to create tickets, as well as Confluence. We used to create tickets, and those tickets used to go to different development cycles, like different site process cycles, development to the product manager, and then finally to QA. We used to close those tickets.

Black box testing is generally when you don't know the context of the code, like if you know what the code is, and then it is called white box testing. And so, basically, if you are doing unit testing, it is a white box testing because when you need testing, you are looking at what the code is inside the development code. It is done generally inside the development code, while white box testing. Coming to the black box testing, we consider that regression testing, smoke testing, and sanity testing. These kinds of testing are like black box testing because we don't know what the code is inside. So, these are black box testing.

So, basically, I have worked with product managers as well as development teams. So, basically, we used to grasp all the testing scenarios, what output of the product is, and how it's gonna influence the customer as well as our business values. Then, you would write the test cases, which would be reviewed by developers and product managers. After that, we used to constantly check and give some improvements in the product also, or know the product's architecture, how it can be faster, how it can be more better, when it comes to users. You had a perfect perspective. Sometimes you got missed by the product managers and developers. So, we used to add some values over there. So, basically, I can say that I have mostly worked with product managers' teams and as well as developer teams, mostly with them, and used to work on the whole release cycle as well as after the release has happened, we used to work.

The industry standards. I'm not aware of this either. What are they?

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 comes to script language, I am also well aware in Java. So we also use TestNG as well as Java, and Cucumber, and Selenium, Nappy, or TestNG. So, Python, when it comes to script language, I use Python mostly.

If all the p values, p 1 and p 2 are covered, and the user is not blocked, then when it comes to the product, the user is able to use the product. We can then say that our product meets the regulatory compliance standard. So, basically, in our current company, if the UAT test scenarios, as well as some p values, meet the requirements, then we are okay with their compliance standards.

It depends upon what type of framework we are developing. If it is a back-end only, we will approach it by considering how many services are being called inside this framework and how many teams are working collaboratively. These two things are the most basic things, and how many API calls, services, and database access are needed will be evaluated. We will also be evaluating truth cases, like if something is coming from the response, how is it expected to be. So, basically, we will try to model and modularize all these things inside our back-end test framework. When it comes to UI, let's say mobile, we will develop a framework where both mobile and UI can be handled inside the same framework. We can create an interface which can be implemented by both mobile and web, and all the scenarios are the same in mobile and web. However, web should have different methods when it comes to implementation. So, basically, all the test cases will be the same, but the implementations will be different for both things. We try to develop a framework that is

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

So, basically, the role of QA is the, like, one of the most important roles inside the development and the process of improvement. It is because mostly it ends the development process with the QA, and QA are the, like, owners of the product after it is developed and advanced to the users. So, basically, we can say that we are the holders. The QAs in India are the holders of the product. It should not break after that. It generally starts with the business team and product managers, and it ends with the QA only. So, we, as QAs, have a very important role in the product development cycle, and notice the role of QA in the engineering process improvement. And when it comes to process improvement, QA has a very different, very good role because QA interacts from the beginning of the product development, like, when the product is being made and all the portfolios for the product and new designs are being made. Then only the QA process can try to be a mediator between product managers and developers. So that time as well as the efficiency of the process can be improved. So, basically, Qwik handles all the process cycle, and it can mitigate a lot of issues if, like, it can increase a lot of efficiency if you can see, it can mitigate a lot of issues.

Yes, I have worked in load testing for a service which is a gamification service. So, basically, we used to have a lot of events called 10-10, 11-11, 12-12 in my first company. So, basically, what we serviced was events. We used to create events. So during those events, like, even 10,000 users would be simultaneously playing the games. We used to check the number of ports that needed to be there for the system. It needs to be installed, and any additional parallel ports need to be installed for the system to handle those numbers of current users. So, basically, what we did is, we would hit create in our QA environment. What we did is, we checked the number of ports used and checked the performance of the port when we checked the eligibility of the user. You would then play the game, and all the processes were there, making a replay of the actual production environment that existed. In case when it was in case, when the production was going on.

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