Upendra

I have more than 10 years of experience in testing Around, uh, 9 years experience in automation testing. And, uh, mostly, uh, I worked as a test lead. Uh, around 6 years experience in, uh, as a test lead, I work. As part of my goals and responsibility, like, I worked on, um, manual testing, uh, automation testing, API testing, performance testing, I put an, uh, for an estimation, test plan, test strategy creation, uh, sign up document preparation, and, uh, daily, monthly, weekly status. Um, uh, then I I already I already worked on the terminologies. Like, uh, I worked on, Uh, I, actually, I watch part on, uh, in scrum methodology and doctrize call, then scrum meeting, uh, daily stand of call. Uh, I worked in, like, framework design and development, mentoring the teams of around 8 team member, uh, especially in manual testing and automation testing. Okay. So, uh, I worked, uh, and, usually, in performance testing using JMeter. So, uh, basically, like, APA testing, Um, Beijing Postman, Mooka and chess as some Liberty. I worked around 1 year. If we testing

Okay. So black box testing, it's nothing but, like, functionality testing, and it's it's basically testing point of view. Uh, like, whatever functional testing we are doing that is called black testing. Uh, OPEC testing, you can see. White box testing, it's called a black box testing also. Like, uh, you you like, developer used to do white box testing, like, this, like, what you can say, boundary value on AC. So equivalent partitioning, it's all from calculated, uh, terminal is coming under black box testing. Whatever manual testing we are covering, that is called lag box testing. White white box testing, like, sacromatic complexity, then top down, a 4, bottom up approach, and, uh, um, like, graph, k, flowchart and all, all coming under white box testing. So, basically, unit testing and all all development point of view, uh, whatever you are working. That's called white box testing. So, basically, all functional things, uh, coming under black box testing. All, uh, technology side development side, it's coming under white box testing. So it's basically, like, uh, white box means it's it's glass. Right? It's example is glass box. It's not so order. Uh, OPEC testing means it's it's black means only we are checking the functionality testing that's called edge, uh, black box. 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, uh, like, application testing, smoke testing, radiation testing, uh, sanity testing, all coming under blast testing. Thank you.

So regression testing, basically, we are testing the uh, most of the multiple thousands of test case 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, uh, for example, we are covering any new features. Right? Like, a distinct application media. So management is going on. So whenever support some announcement, whenever we are going, we're going to test that for specific test case. For the only 1,000 test case is there out of this 20, uh, out of this 100 test case related to new application or enhanced application, okay, with the existing application. Whenever we're merging within the 1,000 test group or test cases, so it should not impact the 900 test cases because of our 100 test case. So basically, we are making sure there because of, uh, enhanced test cases of scripts, uh, scripts, it not impact the existing application. So 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 only, we are using in automation testing to do the regression testing. Because, uh, if you are working on products company or services company, that's a 100 and subs scripts we need to cover. So manual side, it's very difficult to achieve. So that's why we are covering autonomous test cases. And that is facility definition, whatever I told already. So that is the thing. So most of the test case we need to cover in

So, uh, QA in your improvement each, uh, like, to improve the quality. Okay? To improve the, uh, naming convention whenever, uh, it's part of, like, script design and all. And if you are doing functional testing, manual testing, we need to mix your 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, in quality is the most important. So, like, a lot of, uh, QA in there means make sure that, we'll cover most of the functionality whenever you are writing the test cases. We cover most of the features. We need to maintain the requirement. Okay? Like, all requirement, we need to make sure that for all requirement, we're writing the test cases properly. And test case should be 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, wind to cover. And, especially, QA in there to take care of, like, uh, UI testing, UI testing, or maybe you already testing, then, uh, um, then I have a functionality testing point of view, all the things, all the functionality to not cover. Right? Uh, then even for performance testing also coming under, uh, as a QA in that we need to do. Okay? So that is the one point. And, uh, basically, I need to make sure we need to maintain the quality with good deliverables. And, yeah, that's all currently. I'm just, uh, binding. That's all.

So, uh, basically, uh, I used to work, uh, 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. Uh, so basically in, uh, I have primarily worked, you know, Thomas on testing. That not mean that I have not worked on manual testing for banking, finance application, payment domain, uh, judiciary connected development projects, and it's on commodity trading and analytic trading project. I already worked, uh, using QTP. Even I am aware about like, I have already exposure about the Selenium automation testing, API testing. Okay. By using postman, feed alerts, cURL, and with the Cucumber. I am aware about with the Cucumber. TDD testing g, like, with driver. And, uh, even Tosca, I'm aware about that. I have not worked in real time, but Tosca, I'm aware about that. And, obviously, Selenium and to Selenium and you have to automate some testing Jira, uh, then ELM, JAMA, that is test management tool. SDN and GitHub Git for, uh, version control or configuration management tool. So I am ever where about these tools and technology terminologies. So mostly my premise gives us the automation testing in the API testing also. Performance testing said. I have 4 around experience. So, basically, I cover most of the things like API, functionality testing, the, uh, we have the automation testing, on performance testing back inside as well.

Yeah. So in case in PCNC means, like, for real time, in real time, I face this Jason, for example, you have lot of test cases is there. Right? So, uh, resource are less. It means the resource are there, and even 25 resource are 20 resources. The same job we need to do. Okay. This is tedious job. Like, for example, in software solution, uh, you're part of this company. We worked on multiple product. Right? They were on, etcetera, external, and a lot of application was there. So thousands of cases are there. To achieve that, it's very difficult, very tedious job to send repetitive test case we need to do again and again in manual testing. Right? That's the automation came into picture. So we started working on QTP 11 that came, and we designed the test cases. Right? And, uh, we achieved, like, How 500, 600 test cases. This, uh, for 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 we need to cover most of the cases with which one is feasible in our automation. So that time, we need to, uh, so that is it's support to manual test also. They they can't level to they're no need to save multi, more time in office and do same tedious job again and again. Right? So basically, for reusable two point of view, autonomous time into picture. Multiple data and all. So that is the overall things so you can achieve that one. So that is the thing. Okay? So We need to achieve, uh, uh, reusability point of view. Basically, we are using automation. Okay. So that we can cover most of the test case.

How do we handle this situation? Where the developer disagrees with the bug we have reported? So yeah. So for example, uh, 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, uh, box. So make sure if you are using QC, ELM, or bug Jira, any bug tracking tool, we need to capture the proper evidence. Right? If we did is we need to capture and, uh, attach the, uh, like a screenshot. And we need to proper discussion and one line summary we need to maintain. And and even propelling network time out of performance time or the proper screen also you need to attach so that a developer can understand very clearly that there is that issue belong to which place? Okay. We need to put the header also. We can give the color if still developer not agree. So depends upon reliance on reliance on, we need to maintain that one. Maybe we need to throw chart channel. Okay. 2 communication channel. We need to um, uh, reproduce same issues, and we need to sow them. Sometime that it should not finding or something that maybe they are not aware about the functionality. We need to sow. Maybe we need to go to their seat. If you are working in same organ, you are not working from remote. Or now already virtual things are there, like, if your teams call out of, uh, in different channel communication channels is there. So you can, so that particularly that we can reproduce the same issue and so this is the issue actually coming. Okay? And, uh, once he or she will be convinced, okay, this is the gateway issue. So, uh, after that, we can go ahead accordingly. So that is the thing. If not disagree, so first you need to capture property within, then you need to go directly physically or virtually. You need to communicate the same thing. That is done main concern. So already I face this situation multiple times. Okay?

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

Yeah. So, basically, automation test, uh, test framework from scratch. So To do automation framework from scratch means first yeah. So currently, I'm working on library application. Right? Or we are using Angular JS or HTML five. So it depends upon our UI, right, or desktop application. So that's why we need to make the POC. As we need to check 1 basic features, like, um, 11 small features, like happy part test case we need to create anyway, And we need to begin the framework for particular test case of specific small feature. If that is working, like, for example, Only look at the identifying or not, whether we can able to achieve locate properly, and you can write the scripts and that Whatever browser is there that is supporting or not, we need to next year, we need to make the POC. Like, whether it may be Selenium, UFT, Roleskhar, Autodesk complete, any framework, Any automation tool maybe. So after that, we need to create 1, uh, small demo demo. Right? So demo for, Like supporting or not the application. If it support, then you need to maybe we need to record the video. Okay? And need to show to client or, um, I don't need to show to company, uh, whoever my manager is there. So so once ERC will be convinced, Then you can go ahead to work on automation framework. Okay? This is anyway supporting. So happy path you need to do. Any, like, cool features, you need to Whatever tools features in there, h for that, and you need to meet the POC. If that is satisfying, then we will go for a framework. Test framework begin. Right? We can follow some digging patterns like maybe you can go for keyword. Do you want it? Do you want it? Do you want it approach? Or or hybrid or if you are going for serenity on-site, you can page factory, uh, terminologies,

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

Yes. Obviously, I have a load testing experience. Um, I have around 1 year experience in load testing. I've been testing even in my, uh, around, Uh, 5 years, 6 years back, uh, I worked in, like, uh, programming testing the load runner, but 3 to 4 month normally wish to work on load runner. With VU generator and our codeless and things. But actually, most of the year, actually, most of the time, like, around more than 1 year, I work in g meter JMeter. So load testing I used to do with the JMeter only. So load testing to assure the system performance. Yeah. Monitoring tool, data trace, and load testing, uh, like, like CPU and all that. If you, uh, are memory or Internet load testing definitely for load testing, we are using the uh, g meter. Like, g meter, uh, we are creating recording the test case, and, um, we need to actually discuss meeting with developers. So we need to check particularly how many user are, uh, it it need to hit the application to server, uh, the concurrent user. Right? So how many companies? So that one decide whether whoever the developer or stakeholder or whoever taking care of the application development and all. So after discussion and finalized, we need to create a test plan and exporting. You need to go through that. So lot of, uh, system monitoring tool is also there, Uh, okay. Okay. Performance. How is your performance is going on? Like, for monitoring purposes, you're using even g meter side also an extension engineer. And, uh, you can use that 1. Uh, then it is what I told. And but then I said, I'm not that much aware about that, but I know, Uh, you can check the CPU set and all. Right? Um, memory. But load testing, yes, obviously, worked. Like, a lot of features if they are in load or not. So we need to create a test plan.

Yeah. Are you calling it cloud testing? Yeah. Cloud testing moment. Yeah. I obviously work, but, Like, whenever, uh, I'm not or deeply, uh, enter into this. But, yeah, obviously, it's like on premise and premise Set up the idea, like, for, uh, like, software, its platform, I think that's some PAS SASS application. So even I think when after the project, I used to work in cloud enrollment. But, With the sandbox environment, like, uh, in. Uh, but I'm not that much, Uh, and moment. Uh, not that much error about that. But, yes, obviously, software edge platform. Okay? And, uh, it says fastest is there. So I think I used to for, uh, 1 or 2 of the application. Okay? So testing, like, in sandbox environment connector, WM project loop back connector, API testing, using Mooka and Jai used to work, uh, in that, Actually, for for cloud enrollment. Yeah. Obviously, this is not a big deal. So, uh, I used to work on 1 or 2 episodes. Right? So it's basically all the, uh, features like, organization, URL, all the things combined together to the active cloud. So, uh, that's it. Altogether, it will be available.