Upendra

I have more than 10 years of experience in testing. Around 9 years of experience in automation testing. And mostly, I worked as a test lead. Around 6 years of experience as a test lead, during which I worked on manual testing, automation testing, API testing, performance testing. I was responsible for creating test plans, test strategies, and sign up documents, as well as providing daily, monthly, weekly status updates. I also worked on terminologies. I worked on implementing scrum methodology and conducting daily stand-ups. I was involved in framework design and development, and mentored teams of around 8 members, focusing on manual testing and automation testing. I also worked with performance testing using JMeter. In terms of tools, I have experience with API testing, using Postman, and other tools like Mocha and Chai. I worked for around 1 year in testing.

Okay. So black box testing, it's nothing but functionality testing, and it's basically testing from a point of view. Whatever functional testing we're doing, that is called black box testing. White box testing, you can see, is actually called black box testing also. Like, you know, developers used to do white box testing, this is what you can say, boundary value analysis and equivalent partitioning, all of which come under black box testing. Whatever manual testing we are covering, that is called black box testing. White box testing, like, structural complexity, then top-down, bottom-up approach, and graph, flowchart, and all coming under white box testing. So, basically, unit testing and all development points of view, whatever you are working on. That's called white box testing. So, basically, all functional things come under black box testing. All technology side development side, it's coming under white box testing. So it's basically, white box means it's transparent, right? It's an example of a glass box. It's not obscure. OPEC testing means it's black, means only we are checking the functionality, that's called edge, black box testing, with testing point of view, we are calling it. Black box and development point of view, it's calling and why we're testing. So all functionality related, like, application testing, smoke testing, radiation testing, sanity testing, all come under black box testing. Thank you.

So regression testing, basically, we are testing the most of the multiple thousands of test cases we are testing. So we are making sure that whenever we are doing revision testing, it should not impact the existing functionality. Okay? That means, for example, we are covering any new features. Right? Like a distinct application media. So management is going on. So whenever support announces something, we are going to test that for specific test cases. For one out of every 20 test cases is related to new applications or enhanced applications, okay, with the existing application. Whenever we're merging within the 1,000 test group or test cases, it should not impact the 900 test cases because of our 100 test cases. So basically, we are making sure there will be no impact on the existing application because of the enhanced test cases of scripts. That is called regression testing. So mostly, we are working in automation or manual testing. We are covering most of the regression test cases. And mainly because of that, we are using automation testing to do the regression testing. Because if you are working on a product or service company, you have to cover 100% of the scripts. So manual side, it's very difficult to achieve. So that's why we are covering automated test cases. And that is the facility definition. That is the thing. So most of the test cases we need to cover in

So, QA improvement each, like, to improve the quality. To improve the naming convention whenever it's part of script design and all. And if you are doing functional testing, manual testing, we need to mix simple and concise manner. We need to write the test cases so that any user can understand very clearly. Okay. That is one point. And quality is the most important. So, a lot of QA in there means making sure that we cover most of the functionality whenever you are writing the test cases. We cover most of the features. We need to maintain the requirements. Okay. All requirements, we need to make sure that for all requirements, we're writing the test cases properly. And the test case should be the baseline. And we need to make sure the quality, first of all, and we need to cover most of the test cases in recent testing, also like smoke testing, and we need to cover that. And, especially, QA is there to take care of UI testing, UI testing, or maybe you already tested that, then I have a functionality testing point of view, all the things, all the functionality to not cover. Right? Then even for performance testing also coming under, as a QA in that we need to do. Okay. So that is the one point. And, basically, I need to make sure we need to maintain the quality with good deliverables. And, that's all currently. I'm just tying things up. That's all.

So, basically, I used to work with multiple tools and technology. Like, I already worked from, like, QTP ten on what I started working for automation ten, automation point of view. So currently, I'm working in UFT 12,022. So basically, I have primarily worked on testing. That doesn't mean that I have not worked on manual testing for banking, finance applications, payment domains, judiciary connected development projects, and commodity trading and analytic trading projects. I already worked using QTP. Even I am aware about the Selenium automation testing, API testing. Okay. By using Postman, feed alerts, cURL, and with Cucumber, I am aware about Cucumber. TDD testing, like, with JUnit. And, even, I'm aware about Tosca. I have not worked in real time, but I'm aware about Tosca. And, obviously, Selenium and you have to automate some testing in Jira, then ELM, JAMA, which is a test management tool. SDLC and GitHub, Git, for version control or configuration management tool. So, I am familiar with these tools and technology terminologies. So, mostly my premise gives us automation testing in the API testing also. Performance testing is said. I have four years of experience. So, basically, I cover most of the things like API, functionality testing, the automation testing, and performance testing as well.

Yeah. So, in case PCNC means, for real time, in real time, I face this Jason, for example, you have a lot of test cases, right? So, resources are less. It means the resources are there, and even 25 resources are equivalent to 20 resources. The same job we need to do. Okay. This is a tedious job. Like, for example, in software solutions, you're part of this company. We worked on multiple products. Right? They were on external platforms, and there were a lot of applications. So, thousands of cases are there. To achieve that, it's very difficult, a very tedious job to send repetitive test cases again and again in manual testing. Right? That's when automation came into the picture. So we started working on QTP 11, which came out, and we designed the test cases. Right? And we achieved around 500 to 600 test cases. This, from a reusability point of view, basically, we are using automation testing. Right? We need to cover most of the test cases for regression. So that's why at that time, we needed to cover most of the cases that are feasible in our automation. So that time, we needed to support manual tests as well. They wouldn't have to spend more time in the office doing the same tedious job again and again. Right? So, basically, for reusability point of view, automation came into the picture. Multiple data and all. So, that's the overall thing you can achieve. So, that's the thing. Okay? So, we need to achieve the reusability point of view. Basically, we are using automation. Okay. So, that we can cover most of the test cases.

So when a developer disagrees with the bug we have reported, we need to handle the situation carefully. So for example, if any bug is going, first of all, we need to check the rules. Okay? What we need to cover whenever we are finding the bug is to make sure if you are using QC, ELM, or Jira, any bug-tracking tool, we need to capture the proper evidence. Right? If we did it, we need to capture and attach the like a screenshot. And we need to have a proper discussion and a one-line summary to maintain. And even if it's a network timeout or performance issue, or if it's a screen issue, you need to attach the proper screen so that the developer can understand very clearly where the issue belongs. Okay. We need to put the header also. We can give the color code if the developer still doesn't agree. So it depends on the reliance on the reliance we need to maintain that one. Maybe we need to throw in another communication channel. Okay. Two communication channels. We need to reproduce the same issue and sow them. Sometimes it might not be found or maybe they are not aware of the functionality. We need to sow it. Maybe we need to go to their seat. If you are working in the same organization, you are not working from remote. Or now, with virtual things, if your team is out of, like, in different communication channels, there is. So you can, so that particularly you can reproduce the same issue and see where the issue is actually coming from. Okay? And once they are convinced that this is the gateway issue, so after that, we can go ahead accordingly. So that's the thing. If there is a disagreement, first you need to capture the proper evidence, then you need to go directly, either physically or virtually, and communicate the same thing. That's the main concern. So I have faced this situation multiple times. Okay?

How could we keep able for understanding the knowledge? How do we apply this updates in our work? Yeah. So, in terms of QA, I am thinking that I am the right guy. So I can read the expectation, whatever the current company trends is going on. Okay. I'm a quick learner. So even in my past experience, I learned a lot of tools and technologies. And, again, I'm trying to learn more and more things. So, it's huge, it's an umbrella. Okay? A lot of things process terminologies, which to do performance, we need to do API testing. So, a lot of the database testing, a lot of things come into picture. So I am trying to implement the things. Okay? So, obviously, I told you that I am a quick learner. So, it depends upon the client demand, depends upon the company, whatever it fits. Right? It depends upon the application, which one is suitable so that you can do the POC and you can proceed. Okay? Depends upon the process and rules, regulations. Okay? It's for that. It's for policy. Okay? So that's it. That is the application later things. So, yeah, definitely, you can implement in technology and how you'll apply this to updates in your work. You definitely will implement it, depending on the application or which application we are using? So maybe you can do a preview study. Okay. For example, you are telling me that which application is best for this application. Right? So we can do some POCs. So if you are not implementing, not working on Selenium.

Yeah, so basically, automation test framework from scratch. So, to do automation framework from scratch means first, you need to create a proof of concept. Currently, I'm working on a library application. Or we are using Angular or HTML5. So, it depends upon our UI or desktop application. That's why we need to make the POC. As we need to check 11 basic features, like 11 small features, including happy path test cases. We need to create them anyway. And we need to begin the framework for particular test cases of specific small features. If that is working, for example, we can identify whether we can locate elements properly, and then you can write the scripts. We need to check which browser is supported or not. We need to make the POC. Whether it may be Selenium, UFT, Robot, or any framework, any automation tool may be used. So, after that, we need to create a small demo. So, the demo is for supporting or not supporting the application. If it supports, then we need to record a video. Okay? And we need to show it to the client or my manager. So, once they are convinced, then we can go ahead to work on the automation framework. This is anyway supporting the happy path. Any cool features, we need to use whatever tools features are there, and we need to meet the POC. If that is satisfying, then we will go for the test framework. We can follow some design patterns, like maybe you can go for the keyword approach, or a hybrid approach, or if you are going for Serenity, you can use page factory terminologies.

So product, how to decide which when a product is ready to be shipped. Okay. So portal ready to be shipped means whenever we are bringing a zero-defect product, for example. Like, whenever we are creating a sign-up document. So we need to maintain that part also, like, how many defects are there. So it's a video detector or one defect is also there. What is the region is it's really defaulted. Means we need to fix that one initially. So we discussed with developers. So it's for the company's developer or development manager. We need to finalize that one. Okay. So delivery should be complete. It should be deliverables with quality. Okay. And all test cases should be baseline. That means we already added the test cases. So we need to make sure that there should not be any bottleneck. We need to make sure that all functionality will be covered. Okay. That's part of the product. So once the product is covered, then only you can go ahead for delivery. Right? So, yeah, how do you decide when a product is ready to be shipped? To be shipped. Okay. So that's the thing, so that means, Once the baseline is complete, we cover about most of the features. We are ready for UAT. Okay. So these are the basic terms this company uses. So, basically, the time only ends should not be any bottleneck issues so that we can go ahead for production. Okay. And, like, in memory and all other things for human testing, we need to check all the things we need to check.

Yes, obviously, I have a load testing experience. I have around 1 year of experience in load testing. I've been testing for around 5 to 6 years, and I worked with load runner, but normally I wish to work on load runner for 3 to 4 months. With VU generator and our codeless and things. But actually, most of the time, I work in JMeter. So load testing I used to do with JMeter only. So load testing is to assure the system performance. Yeah. We use a monitoring tool, data trace, and load testing, like, CPU and all that. If you're doing memory or Internet load testing, we are using JMeter. Like, JMeter, we are creating a recording of the test case, and we need to actually discuss the test case with developers. So we need to check particularly how many users need to hit the application to the server, how many concurrent users. Right? So how many companies are involved? So that one decides whether the developer, stakeholder, or whoever is taking care of the application development. So after discussion and finalization, we need to create a test plan and export it. You need to go through that. There are also a lot of system monitoring tools available. Performance: How is your performance going on? Like, for monitoring purposes, you're using JMeter as well as an extension engineer. And, you can use that. Then it's what I told you. And I said, I'm not that much aware of that, but I know you can check the CPU set and all. Right? And memory. But load testing, yes, obviously, it worked. Like, a lot of features if they are in load or not. So we need to create a test plan.

Are you calling it cloud testing? Yes. Cloud testing moment. I obviously work, but, Like, whenever I'm not deeply involved in this. But, yes, obviously, it's like an on-premise setup, for software and its platform, I think that's a PaaS or SaaS application. So even I think when I used to work in cloud enrollment. But, with the sandbox environment, like, in. But I'm not that much of an expert, and I'm not an expert. Not that much error about that. But, yes, obviously, it's a software edge platform. Okay? And, it says the fastest is there. So I think I used to work for, 1 or 2 of the applications. Okay? So testing, like, in a sandbox environment, connector, web method project loop back connector, API testing, using Moq and Jai, used to work, in that. Actually, for cloud enrollment. Yes. Obviously, this is not a big deal. So, I used to work on 1 or 2 episodes. Right? So it's basically all the, features like, organization, URL, all the things combined together to the active cloud. So, that's it. Altogether, it will be available.