Sharad Bhatnagar

Yes. My name is Sharad. I belong to Ajmer. I have done my graduation in civil engineering. After graduation, I worked with Larson and DevOps of Quality Quality control engineer, And after that, I have worked with the budget couriers as an operation executive where I used to maintain and No. Create report for Pan India import and exports. After that, I was working for, Aramx International where I used to test the new modules and, used to make the MIS reports for Pan India. And even file the reports into, central government systems. And, It is it was an FMCG, ecommerce company. There, I was working as a QA my job was to, you know, test the the app and their apps. So I've also worked on pause machines where I tested the usability and the performance of Posh Machine. Consumer app, retailer app, and even their warehouse management system. And lastly, I was working with sakan.co. It it is a Kuwait company. The main the related the industry related to, real estate. They they were like the no broker of India. On their platform, you can, list your properties for rents sale, or even exchange. They have, business in 5 countries. Mainly GCC region. And second, I was, assigned a task to, a QA, your consumer app. As well as their front end application. My last project was second was, CRM. It was a customer relationship module. Where I need to, integrate the new APIs and test the new APIs and, create the new model from scratch.

Thank you. For 0 error error framework approach, the test cases should include unit testing, then integration, then system, then regression testing. Because, each I mean, the each type of testing needs to be done to make sure that the error doesn't appear in even a single feature or even in the complete system

Can you take the feature? It's very important. How are you prioritizing the post resolution? In a scenario where a critical feature is failing, How could you prioritize and approach the solution? Okay. So first, I will, you know, try to replicate the Try to recreate the bug or the issue, what is there, and understand its

Steps to make. Okay. So to create a documentation for new feature, the step that, you know, a QA should take is first gather the information for the product team or business team. Then according to those, uh, the BRD business requirement document, we should, uh, I mean, uh, we should make the text test cases. And according to those test cases, we should, uh, calculate the approach, what approach we need, and determine what what type of testing we need to be done, uh, we have to done. And after doing every feature after after testing every feature and doing the related, uh, uh, tested, uh, test the little type of testing around it, we should document it in a such a way that for every feature, there should be a number of test cases, and those test cases should have, uh, the expected and the expected return and what what is the actual return and the remarks if there is, uh, any. And, uh, and the type of test uh, type of test that we have, you know, implemented on it. After doing such I mean, after doing all these test and noting all the requirement, then we will make the document and make then we'll take the document and present it to the, I mean, the stakeholders.

So in agile team, uh, the issue that I faced was, uh, so we had a sprint of 14 days in which we we have to develop the feature then test it and then deploy it. But sometimes because of some business requirement, uh, because some requirement of business side, the development got to stretch at the end moment, and the QA team didn't get much time to, uh, you know, test the feature thoroughly. It should be I mean, the UA was assigned 2, 3 days to test their task, but, uh, in the end, the you you QA got only one day. So that is the challenge. And how I face it? So, uh, the feature that was supposed to release the next day, the QA team got to test it, uh, day before in the evening. So we had to, you know, um, uh, so we had to test the the feature the whole night till morning before releasing it. So yeah.

Example of how do you create a test case to cover a negative scenario. Negative scenario for a feature in the car rental application. Negative scenario. Uh, let's try to explain this with an example. Example negative. Okay. So, uh, the example is in a car rental application, uh, when you want to rent a car, you get options from multiple categories of, uh, for example, hatchback, sedan, uh, and, uh, SUV and MPP and all that. So and the rates were, uh, rates are, you know, determined according to the class of the vehicle. And, uh, so when you select for example, let's say you are selecting sedan and you want to rent it for, uh, let's say, 2 days when you open the calendar. So the calendar should start from, uh, the current date, not from the, you know, uh, the the previous date should not be clickable. If it is clickable, then, uh, we we must inform this to the developer. We need to create test case for this. Like, the, uh, in test case, we need to mention the booking booking date and the dates available before and after the booking dates. So after the booking date date after the booking date, dates available are fine, but, uh, before the booking date, the date should not be, you know, uh, visible to the users. So that's how we should, you know, create a test case around it, and, uh, we should do the testing accordingly.

Okay. So for automating the web, I have used training with Python and, uh, Postman for API, JMeter for load testing, and Jenkins for CICD.

Okay. So for UI and UX on both desktop and mobile platforms, strategies that should that the QA should imply first I mean, the resolution, the screen size, and, uh, different browsers. The app should be tested on different browsers on different mobile platforms, on different mobile sizes. And, uh, for UI, UX, uh, the resolution if if the if the apps, if the device or mobile or desktop allows the I mean, to adjust the resolution, then UI should be tested there also. And, uh, QA And if there is a mode, like dark mode or light mode, the UI, it should be tested for those also. And Uh, for desktop I mean, UI and UX should be tested on multiple browsers. Uh, for mobile, different OS. For example, Android and iOS and etcetera. UI UX. Yeah. And the design should be compare compared with the Figma that we have received from the designers.

How do you approach testing a product that has a significant number of dependents, use of those systems or components. How do you approach your testing when the product has significant? Okay. For such kind of products, uh, we need to first test the feature independent of other system and components. If it passes, then we should integrate 1, uh, integrate the system 1 by 1 system than component 1 by 1. Let's say, uh, I'm testing an app. Uh, I'm testing a new feature. Let's say you can have multiple cards, uh, in an app. Okay. So first, you need we we should test the if if we can add a new card. If this case passes, then, um, we should, you know, work, if, uh, the the the second card should be, you know, able to we should for second card, the customer should be able to, you know, make make payment, uh, kinda like this. So, I mean, first, we need to test the unit, then we should integrate different components, what we have, 1 by 1. Then after integrating all the, uh, components, then we should, you know, do a system testing of of the whole app. And after the after this, we should also do some regression testing around the same feature.

Okay. So, I mean, I tried to learn new technologies that, uh, that got into that have introduced in the market. For example, I have learned Selenium. I have also, uh, learn I'm also learning APM for the mobile web applications. And once I learn these, you know, I try to implement these, uh, learnings in my live projects and see how they're gonna, you know, uh, help the the team and the product and the company as well.

Can you discuss your understanding of the operations within the car and then see how it is informed? Can you discuss your understanding of the operations within the car rental industry? Okay. So car rental is a business. I mean, it's a very, uh, what do I say? It's very lucrative, which is as well as very hectic. You know? When you, uh, giving a car to a customer to rent for rent on rent, you know, you the customer, you don't know you don't know how customer is going to, you know, use it. He could use it in a very, uh, you know, rash manner or, you know, you can use it as, like, it is his own car. So for operations points point of view, I mean, it it gets very, you know, difficult to manage such such such thing because you need to take care of the car. You need to maintain the car. The I mean, the taxes and all, the insurance and everything, it should be paid by the car rental industry. Uh, car, yeah, car rental company and and how it informs your testing. Can we discuss your understanding of operations into the car rental industry? Yes. And how it informs your testing strategies? Okay. Okay. Clearly, this is understanding. Okay. The discus. So the basic understanding that I have about car rental industry is that, you know, a customer can, uh, rent a car on day to day basis, and he needs to pay only the the kilometers for he have used and rest of the thing, like the petrol fuel, uh, insurance, and maintenance will be taken care by the car rental industry. And how it informs your testing strategies, I am not sure about this. So this what you want to, uh, ask how it informs your testing strategies. I would request if you can, you know, elaborate it a little further. Thank you.