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 TSB as a Quality Control Engineer. And after that, I worked with Budget Couriers as an Operations Executive where I maintained and created reports for Pan India imports and exports. After that, I was working for Aramex International where I tested new modules and made MIS reports for Pan India. I also filed reports into central government systems. It was an FMCG and e-commerce company. There, I worked as a QA, testing the app and their apps. I also worked on POS machines, testing the usability and performance of the machine. I worked on the consumer app, retailer app, and their warehouse management system. Lastly, I worked with Sakan.co, a Kuwait company in the real estate industry, which is like a no-broker in India. On their platform, you can list your properties for rent, sale, or exchange. They have business in five countries, mainly in the GCC region. As part of my task, I was assigned to QA their consumer app as well as their front-end application. My last project was a CRM, a customer relationship module. I had to integrate new APIs, test the new APIs, and create a new model from scratch.

Thank you. For a zero error framework approach, the test cases should include unit testing, integration testing, system testing, and regression testing. Each type of testing needs to be done to make sure the error doesn't appear in even a single feature or 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 a new feature, the steps that a QA should take are first gather the information for the product team or business team. Then, according to those, the BRD (Business Requirement Document), we should make the test cases. And according to those test cases, we should calculate the approach, what approach we need, and determine the type of testing we need to be done. And after testing every feature and doing the related testing, we should document it in a way that for every feature, there should be a number of test cases, and those test cases should have the expected result, the actual return, and the remarks if there are any. And, we should also note the type of test implemented. After doing all these tests and noting all the requirements, then we will make the document and present it to the stakeholders.

In an agile team, the issue I faced was that we had a 14-day sprint in which we had to develop the feature, then test it, and then deploy it. However, sometimes due to business requirements, the development got delayed at the last moment, and the QA team didn't have enough time to thoroughly test the feature. The QA team was assigned 2-3 days to test their task, but in the end, they only had one day. That was the challenge. The feature that was supposed to release the next day, the QA team had to test it a day before in the evening. So we had to test the feature all night until the morning before releasing it.

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

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

So for UI and UX on both desktop and mobile platforms, strategies that the QA should imply first, I mean, the resolution, the screen size, and different browsers. The app should be tested on different browsers on different mobile platforms, on different mobile sizes. And for UI, UX, the resolution if the app, if the device or mobile or desktop allows the I mean, to adjust the resolution, then UI should be tested there also. And QA, if there is a mode, like dark mode or light mode, the UI should be tested for those also. And for desktop, UI and UX should be tested on multiple browsers. For mobile, different OS. For example, Android and iOS, etc. UI UX. Yeah. And the design should be 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, using those systems or components? How do you approach your testing when the product has significant dependencies? For such kinds of products, we need to first test the feature independently of other systems and components. If it passes, then we should integrate one system at a time, and one component at a time. Let's say I'm testing an app. I'm testing a new feature. Let's say you can have multiple cards in an app. Okay. So first, you need to test if you can add a new card. If this case passes, then we should work on the second card. The customer should be able to make a payment, kinda like this. So, I mean, first, we need to test the unit, then we should integrate different components one by one. Then after integrating all the components, then we should do a system test of the whole app. And after that, we should also do some regression testing around the same feature.

I tried to learn new technologies that have been introduced in the market. For example, I have learned Selenium. I have also learned APM for mobile web applications. And once I learned these, you know, I try to implement these learnings in my live projects and see how they're gonna help 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 the car rental industry is a business. It's very lucrative, which is also very hectic. You know? When you give a car to a customer to rent, you don't know how the customer will use it. He could use it in a very rash manner or use it like it's his own car. So from an operations point of view, it gets very difficult to manage such a thing because you need to take care of the car. You need to maintain the car. The taxes and all, the insurance and everything, should be paid by the car rental industry. The car rental company needs to consider these costs. Can we discuss your understanding of the operations in the car rental industry? Yes. And how it informs your testing strategies? Okay. Clearly, this is an understanding. The discussion is. So the basic understanding I have about the car rental industry is that a customer can rent a car on a day-to-day basis, and he needs to pay only for the kilometers he has used. The rest, like the petrol, fuel, insurance, and maintenance, will be taken care of by the car rental industry. And how it informs your testing strategies, I am not sure about this. So what you want to ask is how it informs your testing strategies. I would request if you could elaborate it a little further. Thank you.