kellatirupathi · December 25, 2025 05:07
diff --git a/transcript_1QJuNSb3IudJB3QdDfhvHMGOFb1sLGSo1_0_8628.txt b/transcript_1QJuNSb3IudJB3QdDfhvHMGOFb1sLGSo1_0_8628.txt
 [00:00:08]  Hello.
 [00:00:09]  Hello.
 [00:00:18]  Yeah, Shishpal, just a minute.
 [00:00:20]  I'm audible.
 [00:00:22]  Yeah, you are audible.
 [00:00:24]  Yeah.
 [00:00:25]  Hi, Prashant.
 [00:00:26]  Hi.
 [00:00:27]  Yeah.
 [00:00:28]  I'm just a loving one by one.
 [00:00:30]  Should I share you the sheet or like you having the sheet already?
 [00:00:35]  I have it open like who are the ones that I am going to interview now?
 [00:00:44]  Shishpal, Shishpal.
 [00:00:47]  I just scheduled for the first
 [00:00:48]  green.
 [00:00:51]  I just marked as a green color
 [00:00:52]  candidates. So for those people
 [00:00:55]  I have scheduled it.
 [00:00:57]  then I think I'm referring to a different sheet. I don't see any color updates.
 [00:01:01]  Okay. Okay. Now I see that. I'm just sharing. Basically, I'm able to see it after refresh.
 [00:01:07]  Got it. Got it. Fine. I actually filtered for the most recent password base the other day.
 [00:01:14]  So that was mostly with 2025 password base.
 [00:01:20]  I guess it started with Prashant Bankru.
 [00:01:24]  No, actually, I just got update from Aria like for the best candidates to be scheduled.
 [00:01:33]  Okay, should be fine. Can you give me a overview like what these guys are?
 [00:01:38]  Yeah, all these are from the automation testing based and like selenium related and someone like manual related part.
 [00:01:47]  Yeah, so we asked our work would primarily be on manual testing.
 [00:01:57]  Yeah, these people have some what knowledge upon it.
 [00:02:00]  Yeah, so they are okay with that also, right?
 [00:02:03]  Yeah.
 [00:02:04]  Okay, fine.
 [00:02:06]  Once Shishipal interview completed, I will just discuss with you, Prashant.
 [00:02:10]  Sure, sure.
 [00:02:18]  Shishpal, can you turn on your camera and like...
 [00:02:23]  Yes, ma'am.
 [00:02:24]  Yeah.
 [00:02:25]  Prashant, you can continue.
 [00:02:26]  Thank you.
 [00:02:27]  Yeah, Shishpal.
 [00:02:28]  So just turn on your camera and can you give a brief about yourself?
 [00:02:31]  Yes, sir.
 [00:02:32]  Thank you so much, sir, for giving me this opportunity to introduce myself.
 [00:02:37]  My name is Shishpal Singh and I live in Indore.
 [00:02:40]  I recently graduated from Renter Institute of Science and Technology, Bhopal.
 [00:02:46]  Previously, I am in a map quality solution where I am involving in manual testing as
 [00:02:51]  well as automation testing including test case creation defect test case creation defect tracking
 [00:02:57]  and reporting which helped me to build a strong foundation in software testing methodology
 [00:03:02]  i have hand on experience on manual testing techniques such as sanitary smoke regression
 [00:03:07]  functional usability exploratory to insert the software quality we have to mark and i am
 [00:03:14]  proficient in test case management and i write the automation script using selenium with java
 [00:03:24]  So as part of your internship, can you tell me like any one of the critical bug that you came across or that you identified?
 [00:03:34]  Yes, sir. Like many works like I'm working on a project.
 [00:03:39]  So in my internship, there is a live project. Actually, I am working on that.
 [00:03:45]  So in that, like many critical work that I found, there should be a functionality in which user can add and delete their like if the new user can register himself for the access the new things that he or she wanted to explore but unable to do that.
 [00:04:06]  and the dashboard data all the dashboard data functionality that are incorrect inconsistency
 [00:04:13]  of the data and there is a one functionality also for creating the report so all the part
 [00:04:20]  like there will be 10 10 candidates in that but it it is not consistent like it's showing six
 [00:04:28]  or five this type of things many works that i found that
 [00:04:32]  Thank you.
 [00:04:34]  No. So which one you yourself would rate as the highest severity issue?
 [00:04:41]  So how I can rate the severity of the issue?
 [00:04:47]  No, based on the internship which you took,
 [00:04:50]  what would be the most critical issue that you identified?
 [00:04:54]  Sir, most critical issue is the data is not consistent on the dashboard
 [00:05:01]  because that project I am working,
 [00:05:04]  the main priority of the client is via dashboard part.
 [00:05:08]  like the dashboard be smooth for that actually the client having took all the knowledge from
 [00:05:15]  the dashboard how much like that project i am working it's via name of the shubho fidahot so
 [00:05:21]  in which many organization be affiliated like they are providing the food so they having the
 [00:05:29]  knowledge they wanted to check all the data from the dashboard so what i am checking like the
 [00:05:35]  the dashboard is inconsistent, dashboard is not showing the correct data.
 [00:05:39]  So that's the higher severity and high priority issue at that time that I found.
 [00:05:45]  So data being this severe in your application, right?
 [00:05:49]  How did that even cross the development team and was handed over to QA?
 [00:05:54]  When there was an inconsistency in the display?
 [00:05:57]  Yes, there is an inconsistency in the display.
 [00:06:01]  Like it's not a consistent if the new user can create some data, but data we created successfully.
 [00:06:09]  But if the higher user is making inconsistency of the data, it's not showing the correct data at that time.
 [00:06:19]  Okay, so what was the fix given for that?
 [00:06:23]  So fix given for that, I raised the ticket for that and discussed with my team that the problem is occurred at that same time.
 [00:06:33]  So, okay, then I raised a ticket for that discussion we completed.
 [00:06:38]  Then I also discussed with my lead and then I raised a ticket for that.
 [00:06:43]  So I give the high severity and high priority for the ticket.
 [00:06:46]  and then then is a developer is working on that so I assigned for that particular developer for
 [00:06:54]  that and after that developer can research on the same and developer can fix so then the developer
 [00:07:02]  can fix so I also recheck for the same like it's we are really fixed or not and then I see now
 [00:07:10]  when it's fixed so now it's working fine then I can mark as a closed ticket for the same and
 [00:07:17]  that's do it that same time
 [00:07:20]  Okay, so I am not interested in the technical part of how a bug needs to be handled.
 [00:07:28]  So I'm more interested in knowing about what is that you follow as part of your internship.
 [00:07:34]  Once you identify the issue, what is that you did?
 [00:07:38]  What is that your lead did?
 [00:07:39]  How did the bug get resolved?
 [00:07:42]  Yeah, so once I found the work, so I can discuss with my lead the same bug.
 [00:07:47]  Like this is the high severity and high priority bug.
 [00:07:50]  Which type of problem like our software we're facing, like the data inconsistency, data is not showing at the correct way.
 [00:08:01]  So, I also saw with all the valid reasons like I saw with the using of my software and I saw them how the inconsistency we appear in that data.
 [00:08:15]  So, need also research for that and then the same way I already explained what I can do.
 [00:08:23]  So then I can go with the discussion with the same with the developer too.
 [00:08:29]  And developer also understand why that things be happening and developer can work on that same.
 [00:08:37]  Okay. And as part of your previous internship, right? How was your daily day activities going on?
 [00:08:46]  So as part of my previous internship, daily this is like I am working on a project.
 [00:08:53]  So I perform all type of testings like checking all the functionality that we build, the functionality we develop.
 [00:09:02]  So in that I am checking all the previously functionality working fine or not.
 [00:09:08]  and from the previous functionality so I am checking with a different scenario
 [00:09:14]  all the functionality that you working is that you working fine and some
 [00:09:20]  some new functionality we add on I also check that functionality we like
 [00:09:27]  working as the expected and the new functionality we not not be
 [00:09:36]  not having any issue with the older functionality like the new functionality is
 [00:09:40]  involved in the project so it's not impacting the previous functionality i'm checking with that so
 [00:09:47]  and what the measure like what the uh what the client main requirement and that functionality
 [00:09:55]  that we provide to the client that working as expected or not
 [00:10:00]  This type of things on a daily basis, I am checking and if some new functionality we also wanted to be built in a project.
 [00:10:09]  So I also discussed with the project with the lead how it's be implemented and what the reason.
 [00:10:18]  But I also have the document, but I also talk to the lead for the same type of things on the daily basis I can do in my previous day and day.
 [00:10:28]  So how was your day distributed in terms of manual testing and automation testing?
 [00:10:34]  So, yeah, firstly, as a project in our initial levels, on a daily basis, we daily, we implementing the new thing.
 [00:10:44]  So on that basis, I am starting on performing the manual testing.
 [00:10:48]  After that, I know that functionality is stable now.
 [00:10:52]  We not be more changes, we are minor changes if it is required.
 [00:10:56]  so after that I can go with the automation so basically starting from the
 [00:11:01]  that functionality people so I go for the manual testing then it's be working
 [00:11:06]  and then it's be working fine as expected and after that it's been is
 [00:11:11]  travel then I can go for the automation part for that
 [00:11:16]  Okay, on a daily basis, how many manual test cases did you execute?
 [00:11:21]  Yeah, on the daily basis, I can execute 30 to 40 manual test cases on that.
 [00:11:33]  And how long will that take?
 [00:11:36]  It takes around 5 to 6 hours.
 [00:11:42]  And do you have a practice of capturing the test cases anywhere? Do you document it?
 [00:11:50]  Yeah, I can document it on my Excel sheet.
 [00:11:57]  that test cases and how about the bugs that you track that yeah i i'm using the software that
 [00:12:05]  i also use the jira and as well as i use the software that is apts so that's uh in that
 [00:12:12]  platform i can track all the works like which be uh fixed or not uh they are all the things
 [00:12:19]  be in a trackable mode so i can check everything there
 [00:12:22]  So you told me like you were involved in terms of UI testing, integration testing, regression
 [00:12:31]  testing and all of that sort, right?
 [00:12:33]  So what is that that interested you the most?
 [00:12:37]  If you feel like you are very confident about.
 [00:12:42]  Yes, sir. All the things like I'm checking, like I am go with the sanity testing.
 [00:12:47]  So in which I'm checking the new functionality that introduced is working fine.
 [00:12:52]  And I go with the smoke testing for that, like checking the major functionality and major functionality working fine.
 [00:13:00]  And the regression testing, which I am checking that some new functionality will.
 [00:13:07]  so it's not be impacting the previous functionality and i go with the functional
 [00:13:12]  testing all the functionality and non-functional is also i can check go with load testing and
 [00:13:21]  so testings like how can the website can handle the load and in which usability testing i also
 [00:13:29]  explore the website we are perfect for the end user or not it's via user friendliness or not in
 [00:13:36]  the website or not and i go with a monkey testing in which i can random checking like i cannot
 [00:13:43]  follow any roadmap to check all the functionality if i am the login page and i go there any admin
 [00:13:49]  section i have to so i can jump for it it's not be any issue with that these type of things
 [00:13:57]  So I am interesting all type of testing.
 [00:14:01]  So what tools did you use for the load testing?
 [00:14:06]  So yeah, I use the JMeter for the load testing.
 [00:14:09]  I can virtually impact virtually for the users and checkings like what the way we are of the my application at that time.
 [00:14:19]  Okay.
 [00:14:21]  So did you also get a chance to do the backend testing of it, be it in terms of monitoring the logs, having a DB access?
 [00:14:31]  Yes, actually, I do the automation like when I'm writing my script.
 [00:14:39]  So sometimes the script fails, so I can use the logger for that.
 [00:14:44]  So I can track what exactly the reason, what the reason behind that and what the log be come in the console.
 [00:14:54]  So I can adapt it like a store in my logger class and that log I can show the developer for that type of things it's impacting.
 [00:15:06]  So from there, the application is not forwarding like this.
 [00:15:12]  So what was the automation framework that you used before?
 [00:15:16]  Yeah, I use the hybrid framework in which I follow the page object model and page object model and test engine.
 [00:15:26]  So in our page object model, I make a separate class for each pages like I can make.
 [00:15:32]  I make three package for that one package for the common common for the common utility classes and one for the page and one for the test.
 [00:15:41]  and main resource in which I can store the credentials that that the login credentials
 [00:15:48]  in a in a common package I make the way set up you know we set up the one-time utility
 [00:15:53]  for application like opening the application that open the application I
 [00:15:58]  stored in a before shoot and closing the quite the application I store in after shoot and I also
 [00:16:05]  add in that I use the extend report so extend report method logger if the test case be failed
 [00:16:12]  so it's be marked as a fail at the pass if the skip if it is give the warning so I give it's
 [00:16:19]  one after method and I make another class for that step action step action like when I write
 [00:16:27]  the test case we write a driver dot find element so for the simplifying I make whole the property
 [00:16:34]  so i make as if i can typing some words so i can use the send key for that but i can make a simpler
 [00:16:41]  so i just simply click on save type i make it the name of for the same save type and i make one class
 [00:16:48]  for the synchronization for maintain the synchronization i use the explicit implicit
 [00:16:53]  and fluent bit and where the where to be required for the aesthetics i also stored in the static bit
 [00:17:00]  in my sync class and when I all I make a constant variable class like when we give the weight so we
 [00:17:08]  give the duration how much weight we wanted to give so in the duration like five seconds for the
 [00:17:14]  normal for 10 seconds for 50 seconds for the long weight so for the simplify just if I working on my
 [00:17:20]  page so I just give the save save type save save explicit weight and this type of weight I want to
 [00:17:29]  to give like normal or whatever so i can make this type of class and in my test package i uh
 [00:17:38]  I write the test in my page package.
 [00:17:42]  I write the method, hold the method,
 [00:17:45]  actually what I wanted to perform from that particular method.
 [00:17:48]  And that method, in my page section, I extend the safe action.
 [00:17:55]  I extend the safe action.
 [00:17:56]  In my test method, test classes, I extend the base setup.
 [00:18:01]  In my page, what method I wanted to write,
 [00:18:05]  So I write the method and that method I call at my page.
 [00:18:09]  So yeah, that's the reusable and no duplicates of the code and easy to maintain same work that I follow in my automation.
 [00:18:20]  Okay. So what is the role of QA in Agile?
 [00:18:26]  In Agile methodology?
 [00:18:30]  Yeah, so Agile is an iterative and incremental process in which on the daily basis...
 [00:18:37]  So what is the role of a QA there?
 [00:18:39]  So QA, so like checking everything, like in Agile, we are correctly, what we are completing in that sprint.
 [00:18:50]  So that sprint, like that functionality, so checking like we are working on a trackable mode or not.
 [00:18:59]  We are following that traceability metrics in that what we are done and what we are pending and what we are doing in upcoming type of things.
 [00:19:11]  So what is STLC?
 [00:19:17]  STLC is a software development lifecycle.
 [00:19:22]  STLC.
 [00:19:24]  Okay.
 [00:19:25]  STLC is software testing lifecycle.
 [00:19:28]  So in which we are testing which method,
 [00:19:32]  like the process we are following,
 [00:19:34]  testing the software,
 [00:19:35]  like there are different type of case in the STLC.
 [00:19:39]  First is the requirement analysis,
 [00:19:40]  in which we are understanding and analyze the requirement for the testability what we wanted
 [00:19:47]  to test and then on the basis of the requirement we analyze and we can make the test planning
 [00:19:53]  like defining the scope defining the scope strategy and what the resources
 [00:20:00]  we are providing at that time and then we go for the test case development and we design and write
 [00:20:06]  the test cases on a test data use the excel or where we can write the test case in and then we
 [00:20:14]  can go for the test environment setup which configure what the hardware and software testing
 [00:20:21]  tool we are required in that and what tool we are use in that and after that we can go with the test
 [00:20:29]  execution in which we are execute the test and the test kit and log the defect in
 [00:20:36]  retesting for that and then we are test closer insert the execute test completed
 [00:20:43]  and reporting the finding and document lesson like what the work that we are
 [00:20:49]  previously found we are that bug we really really fixed or not so everything
 [00:20:56]  if the work is really fixed then we can go for the test closer for that
 [00:21:04]  Okay. So what is the database?
 [00:21:09]  So database in which we are storing data, like we are following like different type of database, like SQL database, MongoDB, in which we are storing the data.
 [00:21:23]  Like if database, like if I create a.
 [00:21:26]  create some new user some new user can register on our website so that data
 [00:21:33]  user can use their email id or password so that data we store in our database so when next time
 [00:21:41]  we and user so if it is from uh it's we like we know that user is already registered so we can
 [00:21:49]  uh store all the data in our database
 [00:21:52]  for that like in we are also using an application in which the user can user can upload their
 [00:22:00]  documents so and whenever he or she wanted so use that so we are store that document in a database
 [00:22:08]  and whenever the user wants user easily can access that documents like this like in sql
 [00:22:15]  and data be stored in a row and column by so
 [00:22:22]  So have you worked on any database before be it MySQL or MongoDB?
 [00:22:27]  Yeah, I worked on SQL database.
 [00:22:31]  So what is the use of that clause in SQL?
 [00:22:38]  Bab, bab, close.
 [00:22:40]  Where?
 [00:22:42]  Okay, where clause?
 [00:22:49]  What is that?
 [00:22:59]  where it was in action.
 [00:23:15]  Actually, I'm not sure I'm going to be able to tell you.
 [00:23:22]  the user like select the where clause from that table.
 [00:23:29]  Okay, let's move forward.
 [00:23:31]  So given you a scenario, okay, a page takes a longer time to load or it loads slowly.
 [00:23:40]  Okay, so is this a bug?
 [00:23:45]  Yeah, as the response time be less of the web application, like web application is not
 [00:23:51]  as expected time.
 [00:23:54]  So I checking on the resource, like which time of which API we hit and as a lot of time,
 [00:24:04]  It's me, we directly not say a bug, but it's dependent, depend on like which language the application we will.
 [00:24:13]  So the reason behind that, but if it is.
 [00:24:17]  Okay, let me put it another way.
 [00:24:19]  So I hit a URL.
 [00:24:21]  It takes me five minutes to load the page.
 [00:24:24]  After five minutes, I'm able to see the exact content of the website.
 [00:24:28]  So is this a bug or it is not a bug?
 [00:24:33]  We can say it's a bug though, but apparently we don't, not we say it's a, like if the website
 [00:24:45]  is taking longer time than I expected, then yeah, it's a bug.
 [00:24:52]  what type of bug if your climate is going to be a bug because after five minutes obviously
 [00:24:57]  the page loads completely.
 [00:25:00]  Yeah, so it's a high severity and medium priority.
 [00:25:09]  Because the main interaction.
 [00:25:11]  So how would you categorize this bug?
 [00:25:16]  If in case you claim that it is a bug, is it an integration bug or is it a regression bug or what type of bug it is?
 [00:25:24]  So this type of bug you describe like this categorize I can is right that one.
 [00:25:36]  Yeah. Which category will you log this bug under?
 [00:25:43]  So if you feel that it is a bug.
 [00:25:47]  So login functionality, so that category for that is a login issue.
 [00:25:58]  Login functionality, let's take a longer time than expected.
 [00:26:03]  It's the load within whatever time, like maybe it's the load at one minute or 30 seconds,
 [00:26:13]  but it's take a longer time than expected.
 [00:26:17]  So it's a login.
 [00:26:24]  Okay. How would you test a target password features?
 [00:26:31]  Yeah, forget forward feature I can use like when I click on forget forward.
 [00:26:37]  So there will be an email field is come or not for the enter the email.
 [00:26:44]  So when I am entering the email, so the confirmation mail is moved on my email address for that or not.
 [00:26:53]  And when that I can open my email address, there will be a link.
 [00:26:58]  so when i am entering a new password create a new password so it's working fine or not i can
 [00:27:05]  like there we are creating a new password there will be a scenario scenario follow like it's be
 [00:27:11]  not expect like it's not uh use a number field in it so i am checking like if i
 [00:27:19]  give the number field in that so and uh create on a create new password so then it's uh created or not
 [00:27:27]  And there we are also limit you can make the password 10, 10 character you can make the password and I can make more than of the 10.
 [00:27:37]  I'm checking and create the new password or not.
 [00:27:42]  And there should be and also scenario will follow like the password field is not started from the special symbol.
 [00:27:50]  So, and I'm checking like when I use the special symbols, I can create the password or not.
 [00:27:59]  And when I also click on the password and give a...
 [00:28:05]  Give an invalid mail address and I am checking like mail be like there will be confirmation message mail can like you can receive a mail in your email ID.
 [00:28:20]  This type of things I can follow.
 [00:28:22]  Okay, what if there is no email field itself as part of the password reset feature?
 [00:28:29]  Password reset feature.
 [00:28:30]  So if it is a known not an email field, so like when I, so what the scenario like when
 [00:28:39]  I click on a forgot password, so there will be a new field will appear for the entering
 [00:28:44]  the new password.
 [00:28:46]  Would you explain the scenario?
 [00:28:49]  I am not logged into the application.
 [00:28:53]  Okay.
 [00:28:54]  Okay, I forgot my password.
 [00:28:57]  Now I want to reset my password.
 [00:28:59]  So I'm clicking on forget password.
 [00:29:01]  So what are the possibilities that you can think of
 [00:29:04]  that you can get input from the user
 [00:29:06]  and trigger the forget password workflow?
 [00:29:10]  So like when the user can click on the forget password, so there will be no email field
 [00:29:16]  to be present.
 [00:29:17]  Like user can enter the email and that link becomes on the email.
 [00:29:21]  So he can easily or he or she can easily.
 [00:29:23]  The application is not based on email address.
 [00:29:27]  Okay, so just simply clicks then we can click on the forgot password.
 [00:29:33]  So something page be open for that thing without it be a data bleaches.
 [00:29:39]  Like if the new user, like if the user, there should be no confirmation for that.
 [00:29:45]  So how can user can create a new password from the user and if the user can forgot the password?
 [00:29:52]  because if the random user can log in and he or she can easily change then
 [00:30:00]  then password if there is no any page interaction from the confirmation from the it's here real user
 [00:30:07]  or not towards he or she can change the password then if it is possible so there will be a field
 [00:30:13]  if the user is already logged in then he or she can only then he or she can change the password so
 [00:30:21]  there will be a field you can add the new password and then there should be a second column for the
 [00:30:27]  confirmation password that the password you can create so you you can enter the new password and
 [00:30:33]  the same way you can enter the confirmation password for them
 [00:30:40]  Okay.
 [00:30:43]  Okay, so I'm done with the interview.
 [00:30:46]  Okay.
 [00:30:47]  I will contact you later.
 [00:30:50]  Sir, can I ask a question?
 [00:30:53]  Yeah, sure. Go ahead.
 [00:30:55]  I wanted to ask what are the most valued QA skills that value in your organization?
 [00:31:04]  So it is basically like this. So we are a startup with say 20 member team out of which 10 are from the tech team.
 [00:31:13]  Okay. So of this, this is a mix of a developer as well as QA team.
 [00:31:17]  So QA currently we are like four people. So we are also automation engineers.
 [00:31:24]  But we follow, yeah, so we follow Agile methodology here.
 [00:31:29]  So we have very frequent release frequency.
 [00:31:35]  Okay, so due to that, most of our effort will be towards
 [00:31:41]  back-end testing. So the one that I was asking, right, how well are you, I mean, how did you
 [00:31:47]  have any hands on in terms of reading through the logs, because that is where you'll get
 [00:31:51]  maximum exposure in terms of identifying the issues, rather than sitting and testing the
 [00:31:56]  front end. As was the database part.
 [00:32:01]  And one more thing, sir, like, you know, automation testing, which framework organization working in automation part?
 [00:32:09]  So we make use of TestNG.
 [00:32:12]  So our automation part is more towards the report generation thing and monitoring scripts.
 [00:32:21]  It is not a normal UA automation which the other companies does.
 [00:32:27]  Okay, it is not just the regression flow that is getting automated with clear out.
 [00:32:34]  So it will be more of automation towards monitoring the system, towards fetching.
 [00:32:39]  So let's say there has been some report required by marketing team or sales team on a daily
 [00:32:45]  basis.
 [00:32:46]  So rather than sitting and executing that manually, we quickly automate it.
 [00:32:51]  Yes, sir.
 [00:32:52]  Yeah.
 [00:32:53]  That's something.
 [00:32:54]  Thank you, sir.
 [00:32:55]  Yeah.
 [00:32:56]  Thanks for attending.
 [00:33:07]  Hello, yeah, Pritham.
 [00:33:10]  Can we discuss at the end of the interview or like should be like you just asked about 2025, right?
 [00:33:16]  Is it fine with these profiles?
 [00:33:20]  So, okay, so like,
 [00:33:27]  Are these guys only into automation or how is it?
 [00:33:30]  No, no, no.
 [00:33:30]  Actually, I have scheduled one candidate from 2025 and three from 2024.
 [00:33:36]  So, I just want to schedule like, I just schedule based on at least like if they have done manual testing projects.
 [00:33:42]  Yeah, so that would be better because at least with whatever I spoke with him so far, right?
 [00:33:47]  Yeah.
 [00:33:47]  But 2025 can't be...
 [00:33:50]  Yeah, so let's say, so how I see is someone passed out in 2025, right?
 [00:33:57]  So obviously they will not be having much of an industry experience or an internship experience.
 [00:34:03]  But they should be very strong in terms of the technical keywords for manual testing.
 [00:34:09]  Yeah, I got it.
 [00:34:10]  So this guy, he's able to explain things, but not making use of the keywords.
 [00:34:17]  Okay.
 [00:34:18]  It is like, yeah, giving a detailed explanation for a two more question, something like that.
 [00:34:25]  Let's just go through with these profiles.
 [00:34:27]  If you are not satisfied with these profiles, then I will just check about the 2025 based
 [00:34:32]  on whatever the expectations.
 [00:34:34]  Yeah, I'm just delivering the other candidate.
 [00:34:38]  Yeah.
 [00:35:44]  Hello.
 [00:35:45]  Hello.
 [00:35:47]  Yeah, you're so hard.
 [00:35:50]  Yeah.
 [00:35:52]  You are Bhavani, right?
 [00:35:54]  Yes, Bhavani.
 [00:35:56]  Can you just give me a brief introduction?
 [00:35:58]  Yeah, sure.
 [00:36:00]  Thank you for giving this opportunity to introduce myself.
 [00:36:03]  So first of all, my name is Gangabahani.
 [00:36:05]  I'm from Hyderabad.
 [00:36:06]  I completed post-graduation in MCA year of passing 2021
 [00:36:10]  from the SD of IT college and from Tanaku.
 [00:36:16]  After that, recently I joined in Quality Thought Institute.
 [00:36:19]  I learned full stack testing.
 [00:36:23]  Presently, I'm running also that course.
 [00:36:26]  So I completed automation and manual course.
 [00:36:30]  After that completion of manual and automation,
 [00:36:33]  I was joined in.
 [00:36:36]  Ramana soft internship and there I'm working project or projects in manual testing.
 [00:36:42]  The projects are done in manual testing.
 [00:36:44]  After 10 days, I will come.
 [00:36:46]  I will just start the work on automation project.
 [00:36:50]  This is all about me.
 [00:36:51]  So.
 [00:36:53]  So what is that you tested as part of your manual testing internship?
 [00:36:59]  So for what are the areas you have covered?
 [00:37:01]  Sorry?
 [00:37:02]  What is?
 [00:37:03]  No, what is that you actually tested?
 [00:37:05]  So did they have an application or?
 [00:37:08]  Yeah, application, sir.
 [00:37:09]  First application is Academy Bugs.
 [00:37:13]  Our second one is property insurance.
 [00:37:15]  Okay.
 [00:37:15]  and third one is speed test.
 [00:37:17]  What was your role in that?
 [00:37:19]  Quality assurance or test insurance.
 [00:37:25]  So, were you the only guy taking care of the complete testing team?
 [00:37:31]  I was part of a team.
 [00:37:33]  Yes, I am a part of the team.
 [00:37:35]  Okay. So, like how many test cases do you automate? I mean, how many test cases do you check on a daily basis?
 [00:37:42]  Yeah, approximately 20. So, I can write the rest of the cases.
 [00:37:46]  and modules.
 [00:37:49]  And executions?
 [00:37:50]  Yes, sir. I can execute also.
 [00:37:55]  Okay. Okay. So can you tell me the difference between verification and validation?
 [00:38:02]  Yes. In verification, we verify the project related documents. Verification is also called as static testing.
 [00:38:10]  We can review on the documents code on review code in the form of review inspection and walkthrough.
 [00:38:19]  And dynamic testing or validation testing, dynamic testing we can call as a valid testing.
 [00:38:25]  In valid testing, we testing actual software.
 [00:38:29]  And in the form of levels of testing, unit testing, integration testing, system testing and UAT testing.
 [00:38:36]  This is the difference between static testing and dynamic testing.
 [00:38:43]  Okay. So what is severity versus priority?
 [00:38:48]  Severity means how the defect will impact into the application and priority main is how immediately fix the bug.
 [00:38:59]  Can you give me an example for both?
 [00:39:02]  Yes, login functionality.
 [00:39:05]  If the login functionality is not working, so it is priority is high and severity also high.
 [00:39:13]  So if the login functionality is not working or we can't go to an application, then we don't do anything else.
 [00:39:22]  So priority and severity is high.
 [00:39:27]  Okay.
 [00:39:28]  Yeah.
 [00:39:29]  So what if login works without validation?
 [00:39:35]  What?
 [00:39:36]  The login flow works.
 [00:39:38]  Let's say that you're given a username and password.
 [00:39:40]  It allows you to insert the application.
 [00:39:43]  But the validation of that username and password
 [00:39:46]  doesn't happen.
 [00:39:49]  Is this a bug or is it a positive test case of your login module?
 [00:39:55]  First of all, we need to validate the test cases or enter the one.
 [00:40:00]  user password and under the username and under the password valid data we have to enter and then
 [00:40:07]  login click on the login functionality if the login functionality is not clickable then it
 [00:40:12]  will consider as a bug if it is clickable and if you are allowed into the application
 [00:40:18]  if the login functionality is clickable we need to user should be navigated to the home page
 [00:40:23]  or logout page then it will consider then it will working properly if the page is not navigated to
 [00:40:30]  the correct page or proper page so it will consider as a bug
 [00:40:36]  What if the user does not exist at all?
 [00:40:39]  Sorry, what is the use of?
 [00:40:42]  What if the user does not exist as part of your application, but still he's able to log in successfully?
 [00:40:51]  I can't understand that your question.
 [00:40:55]  No, so you have a login page.
 [00:40:57]  So Bhavani is the username and you have a password set.
 [00:41:00]  Okay.
 [00:41:01]  So you are a user, valid user for that application.
 [00:41:04]  Okay, sir.
 [00:41:05]  Okay, so you key in your username password, you are allowed inside the application.
 [00:41:10]  You say that it is a positive test case.
 [00:41:12]  and there is no issue in that yes yes so i do not have a account with your application
 [00:41:19]  till your application allows me to log in okay my username and password yes yes okay so is that a
 [00:41:25]  bug or is it not a bug is that a positive test case for the login flow
 [00:41:30]  How do you see that?
 [00:41:31]  It is a bug, sir.
 [00:41:34]  When you are giving in my application, you will log in with your details.
 [00:41:39]  So it will consider as a bug.
 [00:41:41]  And it is a negative testing also.
 [00:41:45]  So what type of bug is this?
 [00:41:48]  So functional bugs.
 [00:41:52]  In functionality, it has actually allowed me inside, right?
 [00:41:56]  So login functionality is working fine.
 [00:41:58]  Yeah.
 [00:41:59]  How come it can be a functional bug?
 [00:42:04]  Oh, maybe.
 [00:42:09]  user sorry sir
 [00:42:14]  That's fine. Okay.
 [00:42:15]  Navigation problem.
 [00:42:17]  Yeah.
 [00:42:18]  Let me ask you a generic question.
 [00:42:22]  So you have seen this manhole on the road, right?
 [00:42:26]  The one that they use to close the gutter.
 [00:42:30]  Okay.
 [00:42:30]  Can you think of a reason why the lid is always in circular shape?
 [00:42:38]  Always in?
 [00:42:40]  Circular shape.
 [00:42:42]  The shape of the lip will always be circular, if you would have noticed it.
 [00:42:47]  Can you think of a reason for that?
 [00:42:54]  I don't know, sir.
 [00:42:58]  Mm-hmm.
 [00:43:02]  Okay, so let's say that you are in a room with three switches and three bulbs.
 [00:43:11]  Okay, so the room where you are in has three switches.
 [00:43:16]  The adjacent room has three bulbs.
 [00:43:19]  You do not have access to see that room until you enter it.
 [00:43:26]  You will be allowed only once to enter the room 2 where the bulbs are there.
 [00:43:31]  Once when you enter that, you will have to identify which switch is connected to which bulb.
 [00:43:39]  You'll have to identify all the three.
 [00:43:44]  Okay, first of all, we need to put the bulb in the and on the switch if it is working or it is also to pull further.
 [00:43:56]  It is not working.
 [00:43:57]  We will go for another option.
 [00:44:01]  Yeah, so you cannot just like that on and enter that room.
 [00:44:04]  You'll be allowed to enter room to only once.
 [00:44:08]  Okay. Only one time we need to do and the option is only one we have.
 [00:44:16]  You can turn on and off as many times as you want.
 [00:44:19]  But once when you enter room two, you should be able to identify which bulb is connected to which switch.
 [00:44:25]  Okay.
 [00:44:29]  First of all, we need to test right, sir.
 [00:44:31]  We don't know what switch is suitable for which bulb.
 [00:44:35]  So we need to test that.
 [00:44:36]  The bulb is suitable.
 [00:44:38]  This switch are not.
 [00:44:39]  We need to test right, sir.
 [00:44:42]  So, compulsory we need to switch on and also if it is work, it is fine.
 [00:44:51]  If it is not working, we go for another switch.
 [00:44:55]  I mean, go for another option.
 [00:44:56]  But if there is no any option.
 [00:45:00]  Okay, so all the three switches are in a working condition.
 [00:45:04]  All the three bulbs are also in a working condition.
 [00:45:07]  Your test case is to identify which switch is connected to which bulb.
 [00:45:13]  Okay.
 [00:45:17]  So all three switches are suitable for all three bulbs, right?
 [00:45:20]  Right, sir.
 [00:45:24]  So every switch is connected to only one bulb.
 [00:45:29]  So let's say that you label the switches as 1, 2, 3 and you label the bulbs as A, B, C.
 [00:45:35]  I want to know if one is connected to A or B or C, similar with 2 and 3 also.
 [00:45:41]  So how will you identify that?
 [00:45:45]  So we need to test one switch with three bulbs.
 [00:45:50]  So verify the switch with three bulbs.
 [00:45:53]  So bulb A, bulb C and bulb B.
 [00:45:57]  Then we can identify which bulb is suitable for switch A.
 [00:46:03]  Yeah, so A bulb is suitable for switch A, it will working on, it is suitable for A and the second one is B.
 [00:46:14]  And third one is automatically left of the switch, it will be suitable for bulb C.
 [00:46:21]  So we need to test two bulbs there.
 [00:46:28]  Left one is suitable for third one.
 [00:46:31]  You need to test third one.
 [00:46:32]  We don't need to test this third one.
 [00:46:36]  Mm-hmm.
 [00:46:37]  Yes, sir.
 [00:46:39]  Okay. So can you tell me what are the test cases you will execute to verify if a pencil is working fine or not?
 [00:46:52]  Okay. So verify the pencil length and verify the pencil width and verify the test case pencil
 [00:47:07]  black pencil it is a right or not writable or not and the way for the pencil with the
 [00:47:19]  with the length, with the height and
 [00:47:24]  writing or not so if pencil is so we have to test these three test cases
 [00:47:34]  Only three?
 [00:47:36]  You can write more than that.
 [00:47:38]  Depends on requirements.
 [00:47:42]  No, let's say that you are the one who is going to take a call whether this can be released in the market or not.
 [00:47:47]  So what are the maximum things that you will be testing once when you get the pencil?
 [00:47:54]  So, and dark, first we need to test, first we testing a pencil length and width and pencil is right or not and pencil width of lines, how it will write the dark or lightly.
 [00:48:14]  if it is uh we can test uh also it is a dark or lightly written and
 [00:48:23]  pencil has the eraser or top of the uh pencil if it is uh has the eraser or not
 [00:48:30]  top of the pencil and the pencil has the cap or not uh in that uh and also
 [00:48:38]  Um...
 [00:48:42]  Yeah, and it is a reasonable price or not about the pencil.
 [00:48:49]  Uh-huh.
 [00:48:54]  Yes, sir. These are all I have.
 [00:48:56]  As you told about the price, right?
 [00:48:59]  So what kind of a test case is that?
 [00:49:06]  write the verify the pencil with the price so is it a functional test case or is it a
 [00:49:17]  price how do you group that yeah
 [00:49:25]  It is not functional, it is not performance and
 [00:49:37]  I don't let me know.
 [00:49:43]  Okay, let's say that you use the pencil and write something on a paper.
 [00:49:49]  Now you try erasing that with the eraser.
 [00:49:51]  Yes, sir.
 [00:49:52]  Is that going to be a test case for the eraser or for the pencil?
 [00:49:58]  Pencil, sir. When we are...
 [00:50:00]  write the on page with pencil if you want to remove that it will it will be removed it should
 [00:50:05]  be removed so it is test case for pencil sir and also it is also a riser also when we are using
 [00:50:13]  riser it it should be remove the uh what we are right with pencil so this test case is suitable
 [00:50:20]  for pencil and riser sir
 [00:50:25]  And is this going to be the same type of test case for pencil and eraser?
 [00:50:30]  How do you categorize them?
 [00:50:33]  Performance.
 [00:50:36]  performance of what?
 [00:50:40]  performance of pencil performance of eraser sir and functionality of pencil it is working right sir
 [00:50:49]  uh so functional
 [00:50:51]  So in general, what is performance testing?
 [00:50:56]  Yeah, performance means the speed, sir.
 [00:50:59]  Speed of the testing application.
 [00:51:02]  Speed of the...
 [00:51:03]  In performance testing, we test the speed of the application.
 [00:51:06]  In performance testing, we have three types of testing.
 [00:51:10]  One is load testing and stress testing and volume testing.
 [00:51:15]  Can you relate this with the previous example?
 [00:51:18]  Yes, load testing means...
 [00:51:21]  Performance test case.
 [00:51:24]  So performance means when we are using the pencil, we can write speedily or not.
 [00:51:28]  So write with that pencil, we can move speedily or not in writing.
 [00:51:35]  This is performance testing.
 [00:51:38]  So does that depend upon the pencil or does it depend upon the user who is using the pencil?
 [00:51:43]  So whose performance are you measuring?
 [00:51:46]  So it is also depends on pencil and also user.
 [00:51:51]  So like pencil and of the pencil is it will be with these low high and we can write speedily.
 [00:52:01]  So.
 [00:52:02]  So if it is a with is a small, then we can write easily.
 [00:52:07]  It is also depends on pencil.
 [00:52:10]  I mean,
 [00:52:11]  I mean,
 [00:52:14]  manufacturer and we can it is depends on also user writing speed so yes okay so do you have
 [00:52:25]  hands-on on db and db testing yeah database testing so yeah so can you tell me what is the primary key
 [00:52:38]  foreign key
 [00:52:41]  primary key actually i didn't recall it sir uh yesterday night i know uh tomorrow we can
 [00:52:49]  schedule the interview so there is no enough time to recalling all of these things
 [00:52:56]  okay uh previously i used my sequel right yes sir my sequel can you tell me a simple my sequel query
 [00:53:06]  Yes, select a column name from the table, like select ID from the table name and where ID is equal to three or four semicolon.
 [00:53:20]  So this command, it will give the information about ID three.
 [00:53:26]  So what if I want to display only the top five results from employee table?
 [00:53:37]  How do you do that?
 [00:53:37]  Yes.
 [00:53:38]  So we can use limit to serve in that select.
 [00:53:42]  select a star from in column name if we want to mention the column when then we
 [00:53:47]  can mention instead of the star select column name from the table and as an
 [00:53:54]  order by the order by sending and limit to five sir
 [00:54:01]  So is there any other DB that you've worked on?
 [00:54:06]  Is it only SQL?
 [00:54:09]  I'm working in Veracl and also MySQL, sir.
 [00:54:15]  Okay. So are you aware of what a slow query is?
 [00:54:21]  Yeah, we have so we can write where clause and having clause and group by clause.
 [00:54:29]  No, no. What is a slow query?
 [00:54:31]  What is?
 [00:54:33]  A slow query.
 [00:54:35]  Slow query.
 [00:54:39]  So query means it will perform slowly now, sir.
 [00:54:46]  So what does performing slow means?
 [00:54:51]  I didn't listen this voice as low query.
 [00:54:55]  Okay.
 [00:54:59]  Bye.
 [00:55:02]  So can you tell me like what is regression testing?
 [00:55:06]  Yes. So whenever developer try to make any kind of changes in the application,
 [00:55:14]  so maybe it is like bug fixing or code modification and adding the features and deleting the features.
 [00:55:22]  In that situation, the tester should do the regression testing because of that kind of changes are not impacted to unchanged part of the application.
 [00:55:29]  It is called regression testing.
 [00:55:34]  Okay.
 [00:55:37]  Yeah, Bhavani, so I'm done with the interview. Do you have any questions for me?
 [00:55:41]  Can you give me the rating, sir?
 [00:55:46]  So how do you want the rating to be?
 [00:55:50]  I see it in two ways. One is technical and logical.
 [00:55:56]  Both so.
 [00:55:58]  Okay, I would tell you like you are kind of strong in terms of technical terminologies.
 [00:56:06]  Okay, but you will have to improve a lot in terms of logical thinking.
 [00:56:11]  Okay, sir.
 [00:56:12]  Because in case of this manual question, right, you didn't even attempt to answer it.
 [00:56:18]  So that typically shows like how wide or how long do you stretch yourself in terms of thinking.
 [00:56:25]  And being a QA, obviously, you should think across in writing test cases, right?
 [00:56:30]  So you'll have to improve on that.
 [00:56:32]  Okay, sir. Thank you.
 [00:56:34]  Yeah. Anything else?
 [00:56:35]  Thank you, sir.
 [00:56:37]  No, nothing, sir.
 [00:56:38]  Yeah. Thanks for your time.
 [00:56:40]  Thank you. Thank you.
 [00:56:42]  Bye.
 [00:56:43]  Bye.
 [00:57:39]  Rajkumar, could you turn on your camera?
 [00:57:41]  Yeah.
 [00:57:43]  Okay.
 [00:57:48]  Is it visible?
 [00:57:52]  Yeah.
 [00:57:52]  Yeah.
 [00:57:54]  Yeah, sorry for my manners.
 [00:57:57]  Because I think I...
 [00:57:59]  Sorry for the t-shirt.
 [00:58:01]  Because I thought there's no interview for me today.
 [00:58:04]  And I test like this.
 [00:58:08]  Yes, no problems. So I am Prashant from Clearout. So can you just give me a brief about yourself?
 [00:58:17]  Yeah. Hi, Prashant. I am Raj Kumar Chilaka from Gondur district. I completed my post graduation in 2024.
 [00:58:24]  Currently, I'm staying in Hyderabad and learning the learning manual and automation testing.
 [00:58:30]  And I have a one year experience in Cognizant as a tester.
 [00:58:36]  So I wanted to become a tester. I am a good team player and I am an expressive person and an adaptive person.
 [00:58:45]  And my hobbies are reading books, watching web series, listening music and travelling. I come from a nuclear family.
 [00:58:54]  That's all about me.
 [00:58:56]  Okay. So what was your role at Cognition?
 [00:59:01]  I'm a manual tester as I work with both development team and stakeholders.
 [00:59:10]  I have to check every cycle. My project is a Humana Healthcare.
 [00:59:16]  Now what role did you play? Like how distributed is your day?
 [00:59:21]  I'm a tester. As a tester, I have to check every cycles and for every 15 minutes, I need to give the updates to the developers if any cycle is not working.
 [00:59:32]  So I have to get it and work done immediately within 5 to 10 seconds.
 [00:59:38]  So, continuously I need to check every cycle and
 [00:59:47]  and every cycle will be manually triggered and automatically some triggered and it shows the error every time.
 [00:59:54]  So I need to check everything there.
 [00:59:58]  So how many test cases do you?
 [01:00:00]  test on a daily basis yeah I'm a compatible tester there not writing and
 [01:00:06]  executing the test cases I'm a compatible tester and how compatible it's
 [01:00:11]  in the server and those cycles are running as for that one
 [01:00:19]  So what are the devices you run this compatibility with?
 [01:00:21]  Yeah, in the mainframe network, in mainframe server.
 [01:00:27]  So only server-based compatibility you have done?
 [01:00:29]  Yeah, so what I'm trying to say here,
 [01:00:32]  I have an experience in testing,
 [01:00:34]  but I wanted to learn more about the testing.
 [01:00:36]  So I learned manually and manual testing
 [01:00:39]  and automation testing here.
 [01:00:40]  So that's why I bring up my past experience.
 [01:00:43]  So how confident are you in claiming that you have learned manual and automations?
 [01:00:48]  So what are the things that you'll be able to perform?
 [01:00:50]  Can you tell me that again? I didn't get you.
 [01:00:53]  No. So you're telling that you are spending time and learning manual and automation testing by your own, right?
 [01:01:05]  I'm not getting your voice correctly.
 [01:01:10]  I'll use my microphone.
 [01:01:17]  Yeah. Can you ask that again, Krishan?
 [01:01:22]  So you were telling you are currently spending time and learning manual and automation testing on your own, right?
 [01:01:26]  Yes.
 [01:01:27]  So what is your confidence level on that?
 [01:01:29]  My confidence level is currently I have done coaching in quality thoughts in Amirpet.
 [01:01:35]  So they teach me how to what is manual and what is automation.
 [01:01:39]  And currently I'm performing manual executions and automation executions also.
 [01:01:47]  So what is that you have executed in automation?
 [01:01:50]  Yeah, they have given me a dummy project like academy books and property insurance and some
 [01:01:57]  other marriage projects.
 [01:01:59]  So I checked the every detail.
 [01:02:01]  First I perform the exploratory testing and then I write my own test cases and execute
 [01:02:07]  them.
 [01:02:08]  And then after the manually completed, I run with Selenium.
 [01:02:14]  For the framework, I use this test engine and cucumber only a little bit, but I use the cucumber also.
 [01:02:25]  Mm-hmm.
 [01:02:26]  Yeah.
 [01:02:28]  Okay, let's say that you wanted to test and ensure that on closing the door of the refrigerator, right?
 [01:02:37]  Yeah.
 [01:02:37]  The light inside it turns off.
 [01:02:42]  So how do you test it?
 [01:02:44]  First, I need to check whether it's a first, I need to check whether it's a power is supplying
 [01:02:50]  out to the is a refrigerator or not.
 [01:02:53]  That is a precondition I'll give then and then check whether the door is opening or
 [01:02:59]  not.
 [01:03:00]  That's a step.
 [01:03:01]  And then I need to check the light, the bulb is working properly as not correctly.
 [01:03:08]  Then I write the.
 [01:03:10]  I check if I'm closing with minimum space if it's going off or not.
 [01:03:17]  First I need to check the priority is working or not.
 [01:03:22]  I mean priority is high I'm giving and the bulb is working also working is not as a precondition here and also power is also a precondition.
 [01:03:34]  These things I will check and execute it.
 [01:03:39]  But how does this confirm whether the bulb is turning off when the door is closed?
 [01:03:44]  Yeah, there's a thing here.
 [01:03:47]  If we close a little bit of space here, the bulb will be closed.
 [01:03:52]  The bulb will go off.
 [01:03:54]  So I'll check it.
 [01:03:57]  Any other way you can think of?
 [01:03:59]  Any other way?
 [01:04:01]  What if when the bulb is, I mean when the door is about to be closed, the bulb turns off.
 [01:04:07]  But closing it completely, it turns on again.
 [01:04:11]  How will you confirm it doesn't happen that way?
 [01:04:15]  yeah for that particular reason for condition i'll put a camera there if it's not working i mean if
 [01:04:21]  it's not off when i close the door it would be a error i need to call the developer here the
 [01:04:28]  developer is a mechanical something yeah technician correctly technician one and i check the bulb or
 [01:04:39]  conditions here.
 [01:04:41]  First I need to prove them right because this is a error I am facing here and just like
 [01:04:48]  a proof or attachments.
 [01:04:56]  and then get it completed, done immediately.
 [01:05:00]  Okay. So let's say that a bug appears only sometimes.
 [01:05:07]  Only sometimes.
 [01:05:08]  So what would you do in that case?
 [01:05:10]  First, we need to check whether the platform and environment.
 [01:05:15]  Yeah, what you are trying to say is my system is working correctly and I don't get any error.
 [01:05:21]  But for you, it's not working right.
 [01:05:23]  So this is what you are asking.
 [01:05:25]  Now on your machine itself, it randomly appears.
 [01:05:29]  Yeah, we'll have to root cause it first, which is known as multiple times.
 [01:05:37]  If just like a stress and these things will be appear, right?
 [01:05:42]  So in high stress, what is behaving and what is not occurring there, we need to check.
 [01:05:49]  And then low and then here.
 [01:05:51]  First, low.
 [01:05:53]  If we give some criteria, I mean, some level of the here, if it's appearing, we need to take the proof in this environment.
 [01:06:02]  And then, I mean, in this version or environment, any other things in this version and then checking if it's not occurring, then also we have to take the screenshot here or a proof.
 [01:06:16]  Mainly in testing the proofs are must.
 [01:06:22]  Mm-hmm.
 [01:06:27]  I'll assign it to this defect, it appearing in these versions and in these stresses and in these loads.
 [01:06:35]  And then from here, it will be like this.
 [01:06:38]  We need to clear this, sort this out immediately.
 [01:06:43]  I'll assign it to the developer and get it done.
 [01:06:48]  Okay.
 [01:06:51]  So let's say that your automation test case fails, but when you check it manually, it passes.
 [01:06:57]  So what all could be the possible reasons for this?
 [01:07:01]  For that, if the manual is working fine, but the...
 [01:07:08]  Excuse me.
 [01:07:09]  If the test cases in automation is failing means whether it's a problem with our dependencies or the path we are giving, it might be wrong.
 [01:07:20]  We can check that it's dynamically changes sometimes.
 [01:07:25]  So we have to give the correct XPath and the correct ID.
 [01:07:28]  ID and text will be never changed so dynamically.
 [01:07:31]  So we have to check it.
 [01:07:32]  If the...
 [01:07:34]  automation is failing and manual is working, we need to check where it's going wrong and then again perform the test task.
 [01:07:46]  Okay, so what is smoke testing?
 [01:07:51]  Smoke, I'll tell you mainly.
 [01:07:55]  Smoke is checking whether the application is or the build is working as the build is
 [01:08:04]  eligible to do the further testing.
 [01:08:08]  So what is sanity?
 [01:08:11]  Sanity is a detailed testing and particular module only.
 [01:08:14]  But smoke is like checking high level testing.
 [01:08:18]  We need to perform the login and login details and buttons and then add to cart and these
 [01:08:24]  things will be checking.
 [01:08:26]  But in sanity, we only check individual module only and then we check for the
 [01:08:35]  particular module like every test cases here and everything here.
 [01:08:42]  That is the difference between sanity and smoke here.
 [01:08:48]  Okay.
 [01:08:50]  So can you think of a reason why most of the website logo is placed on the top left corner?
 [01:08:58]  Because whenever the user want to enter, if anything highlighting here, I will be catching up to the left because we are Indians, right to left.
 [01:09:10]  So in America, left to right, they follow.
 [01:09:13]  as of I know in India they check left corner and the top
 [01:09:19]  because it's a and also the application is enter in the laptop or mobile
 [01:09:24]  mobile they check for the top one
 [01:09:30]  Yeah, I only know...
 [01:09:34]  If that's going to be the reason, right?
 [01:09:37]  So why is there a difference in the placement of close button between Windows and Mac?
 [01:09:44]  So on Windows, it sits at right top, whereas in Mac, it sits at left top.
 [01:09:49]  I never use a Mac, so I don't know anything about Mac.
 [01:09:52]  But for Windows, if the page is open, it should be closed at right side.
 [01:10:00]  So if we want to check anything from our end, we'll check for the left side.
 [01:10:06]  And then if we are okay, fine and everything, we'll be closing in right side.
 [01:10:11]  Because in our brain, right will be checked for the right conditions.
 [01:10:16]  Left is a, what we say, imaginary part or interesting things will be working in left side.
 [01:10:25]  as a final.
 [01:10:26]  Yeah.
 [01:10:29]  Okay. So let's say that you are writing test case for a particular feature or a module.
 [01:10:36]  Okay. But the requirement changes mid-sprint. So what do you do in that case?
 [01:10:42]  Yeah. In Agile methodology, last minute changes also available, right? So we need to
 [01:10:49]  prioritize the task and divide it and maintain, complete the task immediately. If the requirement
 [01:10:56]  changes in the last time, last of the closing time or ending time, we need to prioritize
 [01:11:05]  the task and then complete the tasks.
 [01:11:10]  Mm-hmm.
 [01:11:15]  Okay, so do you have any hands-on on DB testing?
 [01:11:19]  Database testing.
 [01:11:20]  Well, I didn't concentrate much on DB and APA.
 [01:11:25]  My own, I mean, first I need to complete the...
 [01:11:31]  As of my thinking, first I need to complete manual and automation and then these frameworks and then I wanted to perform database testing and I'm not telling you like that. I don't know anything about that. I learned SQL, but I didn't have any hands on right now.
 [01:11:50]  Okay, can you give me a...
 [01:11:52]  any basic SQL query?
 [01:11:55]  Yeah, if you want to select,
 [01:11:58]  as a tester, we only select command mostly.
 [01:12:02]  If you want to fetch the files
 [01:12:04]  and if you want to get the files,
 [01:12:06]  select star from employee
 [01:12:08]  and select update employee set ID
 [01:12:12]  equal to some 07 and 08.
 [01:12:15]  If you want to update it,
 [01:12:17]  we'll use update key and set.
 [01:12:19]  And if you want to delete it,
 [01:12:20]  delete star from the table,
 [01:12:21]  delete ID from the table and we just have to mention the column name from the table and where it's located.
 [01:12:31]  and then we can alter it and then we can create the database, insert, update the database,
 [01:12:36]  drop the database, truncate. Truncate means removing the data inside but structure will
 [01:12:42]  be remaining. If I have a 10 or 11 fields available in there, if I truncate it, the
 [01:12:48]  data will be gone but the structure will be remaining. If I drop means the complete table
 [01:12:54]  will be gone.
 [01:12:55]  gone, deleted. Deleted means particularly deleting a column or row, these things.
 [01:13:04]  Okay.
 [01:13:07]  So let's say that you are testing a mobile phone's auto brightness in office lighting.
 [01:13:13]  Okay.
 [01:13:14]  Okay.
 [01:13:14]  How do you simulate sunlight?
 [01:13:19]  Well, in sunlight would be a bright, so it should be increased when I'm outside.
 [01:13:25]  Or it must be increased when I'm outside because the sunlight would be strong and we have a very high temperature.
 [01:13:34]  Whether it doesn't matter the temperature or anything, if the light is heavy,
 [01:13:39]  we are using phone in that light, it should be increased or it must be increased, not should be.
 [01:13:48]  Because if he cannot see anything in that light, it should not be working properly.
 [01:13:56]  In office, the light will be a minimum, so it will automatically decrease because we are using automatic adjust, right?
 [01:14:07]  Now, how do you simulate sunlight equivalent testing for the auto brightness feature inside the office environment?
 [01:14:18]  inside of well we need to check first manually and then we have we have to check both in
 [01:14:27]  sunlight and before before the sunlight or office light or anything user is watching
 [01:14:34]  no your test condition is you will have to stay only inside your office
 [01:14:38]  you cannot make use of the natural sunlight so how will you simulate that
 [01:14:43]  yeah for that i need to increase my light in the office because i need to test right
 [01:14:51]  so how do you increase the light in your office do you think you'll have control on that
 [01:14:56]  yeah but
 [01:14:58]  For testing purpose, we can get everything because the testing is the most important thing in the software development lifecycle.
 [01:15:05]  So I'll ask the management to increase the life for only a bit moment of time to check my condition is working or not.
 [01:15:13]  Because if it's not working, it's a defect and I need to complete or close the defect immediately.
 [01:15:19]  Because customer or the product owner is not waiting for me or any other person to check it and wait for it.
 [01:15:27]  So I need to convince my manager and the team to maintain or else I ask him to give me a little bit of a small room with bright lights on it.
 [01:15:39]  So I can test there and I can perform my actions there also.
 [01:15:44]  So this would probably be one of the test cases for testing a mobile phone feature, right?
 [01:15:51]  Yeah.
 [01:15:51]  How can they accommodate individual rooms for features?
 [01:15:55]  Yeah.
 [01:15:56]  I asked particularly if it's possible for me to give the, I need to run this test case.
 [01:16:03]  So please give me an individual room for me to run these particular test cases and everything.
 [01:16:10]  And I'll show the...
 [01:16:11]  What about the rejected?
 [01:16:13]  Yeah, they rejected means I need to convince my manager because this test case is a very high RIT and severity also very high and critical.
 [01:16:29]  So I have to convince my manager.
 [01:16:33]  What if your manager is also not convinced?
 [01:16:35]  If he is not convincing then I need to adjust my any other desktop or any other co-worker phone or anything.
 [01:16:46]  I need to take there and place it when the sensor.
 [01:16:50]  It's the only option I have right now.
 [01:16:54]  If the management is not allowing me to work on that, sorry.
 [01:17:00]  If the management is not allowing me to execute my work.
 [01:17:04]  Why do you not approach making use of your friend's mobile first rather than asking the
 [01:17:10]  management to give you a dedicated room?
 [01:17:14]  Yeah, first I need to confirm with the manager because everything is fine here for the using mobile, but it's not working for the bigger light.
 [01:17:27]  It should be a problem, right?
 [01:17:29]  So first I need to confirm with the bigger light and then if they are not allowing me or they are not checking me properly, not giving me the...
 [01:17:40]  pass to do this, I'll have to use my colleagues.
 [01:17:47]  So first we need to aim for the bigger one.
 [01:17:50]  So what do you think that is practically possible and people would immediately approve or acknowledge to it?
 [01:17:59]  people would I didn't get what it said.
 [01:18:02]  Now what do you think that would be practically possible?
 [01:18:07]  Yeah, it's 70 to 80% possible because if the test case is test, I am given the priority and severity high because these must be done within the time period or end of the day.
 [01:18:24]  I need to show them and I need to...
 [01:18:28]  give the result if the management is not giving me a proof to process this and I need to ask him
 [01:18:35]  or if he is not working I need to buy myself a light because he if he is not giving me a
 [01:18:41]  his mobile or any other equipment of his
 [01:18:47]  Yeah, I prioritize my tasks than waiting for the approval.
 [01:18:59]  Okay.
 [01:19:01]  Yeah.
 [01:19:01]  So before we close, I have one last question for you.
 [01:19:04]  Yeah.
 [01:19:04]  So let's say that you are in a room with three switches.
 [01:19:09]  Three?
 [01:19:10]  Switch.
 [01:19:12]  Switches.
 [01:19:12]  Okay.
 [01:19:13]  Switches.
 [01:19:13]  Okay.
 [01:19:13]  There is another adjacent room which is closed that has three bulbs.
 [01:19:19]  Okay.
 [01:19:20]  So you will be allowed to enter room 2 only once.
 [01:19:25]  Okay.
 [01:19:27]  You will have to find which switch is connected to which bulb.
 [01:19:32]  for all the reasons.
 [01:19:33]  Yeah.
 [01:19:34]  First, I need to ask their permission and then I have to enter the before entering the
 [01:19:42]  room, I need to check is anyone in the room or not first thing.
 [01:19:46]  And then if they are in there, I just ask their permission if I want to find the switch
 [01:19:51]  and which is I want to work and then take their permission and then.
 [01:19:56]  immediately check the condition and then
 [01:20:00]  done my task and you guys can have your work at that time.
 [01:20:11]  So you will be allowed to enter room 2 only once?
 [01:20:15]  Once.
 [01:20:16]  Okay.
 [01:20:17]  Yeah.
 [01:20:18]  So how will you identify the switch to which bulb is connected?
 [01:20:26]  If the co-workers or colleagues are there, I'll ask them first which switch is connected
 [01:20:32]  to the bulb and which switch is not.
 [01:20:35]  after entering the room then if it's if they said to me like this one or this one or this one or
 [01:20:42]  they they did not tell me because they are work the workload is heavy for them and they are
 [01:20:47]  prioritizing their task so i need to ask their permission to check the light this is my condition
 [01:20:54]  so i need to complete the task
 [01:20:57]  here within this room so if I'm going to go outside from the room I cannot test it so could
 [01:21:03]  you please give me a permission to switch on the light and check for the light which switch is
 [01:21:07]  connected to it and then check it and then off it and then I'll exclude myself from the room
 [01:21:18]  Okay.
 [01:21:19]  Yeah, so I'm done with me.
 [01:21:21]  Do you have any questions for me?
 [01:21:23]  Yeah.
 [01:21:24]  I know I missed some of them.
 [01:21:29]  Can you point out something?
 [01:21:31]  I believe there is a room for me to grow every time.
 [01:21:34]  Can you give me some feedback and everything?
 [01:21:41]  Okay, so we haven't much spoke technical, right?
 [01:21:45]  It was more of a logical screening.
 [01:21:48]  Yeah.
 [01:21:48]  So I would rate you somewhere around 5 to 6 on 10 for your logical thinking.
 [01:21:55]  But in case you want to like get associated as a QA or you want to have your...
 [01:22:00]  career path towards QA, obviously you should be increasing, I mean you should be improving on that.
 [01:22:05]  Okay, I need to improve my logical skills, okay.
 [01:22:09]  Yeah, and obviously like you beat a manual testing or automation testing, you should always find time and try to learn the backend stuff sooner.
 [01:22:21]  be it in terms of DB and the server logs.
 [01:22:26]  Now that you have your mainframe experience, right?
 [01:22:30]  So be it if you're going to get into a normal manual testing or automation testing,
 [01:22:34]  it will probably be Ubuntu environment or the Linux environment that you'll be working on.
 [01:22:38]  So you should be and make yourself strong and confident on those areas.
 [01:22:43]  Yeah, as a technical, as a theoretical part, as a technical part, I have learned and executed
 [01:22:50]  many in the Windows and what we say, browsers and everything, but currently I'm lacking
 [01:22:58]  logical thinking.
 [01:23:00]  Okay.
 [01:23:01]  Yeah.
 [01:23:03]  Anything else you have?
 [01:23:05]  Yeah, what?
 [01:23:08]  Do you have any other questions?
 [01:23:10]  Yeah.
 [01:23:12]  What will be the work if I get a sign?
 [01:23:18]  So it will be like as I told you will have access to the servers directly be non-trod
 [01:23:23]  in roundments.
 [01:23:24]  Okay.
 [01:23:25]  So from that you will be able to I mean you will be given a functionality approach.
 [01:23:32]  Okay, so we would expect you to handle the complete end-to-end testing of it.
 [01:23:39]  Be it from the requirement gathering from the development team, taking your test builds,
 [01:23:44]  deploying it on the environment, testing that and automation part, it will be more towards
 [01:23:52]  monitoring logs and writing DB queries that needs to be automated for marketing and sales support.
 [01:23:58]  It's not the basic UA automation which usually is something for the automation team.
 [01:24:05]  Okay.
 [01:24:06]  Yeah.
 [01:24:09]  Yeah, thank you for your feedback and thank you for explaining the project details and I mean the work detail.
 [01:24:15]  Yes, thanks for your time.
 [01:24:18]  Yeah, thank you for your time.
 [01:24:20]  Yeah.
 [01:24:39]  I think Prashant, have you remembered Bhaskar?
 [01:24:45]  Yeah, so he just joined the...
 [01:24:47]  I mean, he entered the call.
 [01:24:49]  That's where he moved in.
 [01:24:50]  I will just ask him to join again.
 [01:24:53]  Yeah, I guess he's only joined.
 [01:24:54]  You need to admit him.
 [01:24:56]  Yeah, yeah.
 [01:25:11]  Good afternoon, sir.
 [01:25:15]  Hey, Bhaskar. Good afternoon.
 [01:25:17]  Good afternoon.
 [01:25:18]  How are you?
 [01:25:20]  Well, sir, I'm doing well.
 [01:25:23]  Can you just give me a brief about yourself?
 [01:25:28]  Yeah.
 [01:25:29]  Good afternoon, sir.
 [01:25:31]  I'm Bhaskar Reddy.
 [01:25:33]  I have done my graduation recently with BBI Institute of Technology.
 [01:25:39]  And with aggregate CGP of 7.9 and done my schooling in Hyderabad.
 [01:25:46]  Along with my academics, I have also learned many technical skills and other skills like Java and Python and testing related concepts like automation and manual testing.
 [01:26:06]  I have done some projects which is based on Python and my core interests are in learning new things and watching cricket.
 [01:26:19]  Can you explain more about your project that you have worked on?
 [01:26:25]  Yeah, I have done a project called IoT parser, which is basically a NoSQL database.
 [01:26:36]  The values have been extracted from NoSQL database to SQL by using Python with libraries called as .re.
 [01:26:48]  CSV and Base64 are the libraries which has been used as well as Matplotlib which helps me to extract the NoSQL data to real world data in tabular form along with graphs and all.
 [01:27:09]  Okay.
 [01:27:13]  So how do you see your career?
 [01:27:15]  So do you want to continue as an automation tester or a manual tester or get into development?
 [01:27:21]  What is that you see?
 [01:27:23]  I wanted to pursue my career in future both development as well as testing.
 [01:27:32]  More in testing because I have attended 1, 2, 2, 2 to 3 interviews related to testing.
 [01:27:39]  I am so much into testing now.
 [01:27:43]  So how did those interviews go?
 [01:27:45]  I have cleared two technical interviews in G-SPAN technologies and they also done HR.
 [01:27:55]  But after that they rejected me because they have to pursue with referral candidates.
 [01:28:03]  So I have lived that and yeah.
 [01:28:10]  Okay. Okay, let me give a brief about like what kind of profile we are looking for. And you can let me know if that suits you. Okay. So ask this kind of so we have two products, one is clear out and clear out phone.
 [01:28:24]  Yeah.
 [01:28:25]  One is based on email, the other is based on phone numbers. So we do the verification part of it.
 [01:28:31]  So this includes introducing more new features in a shorter period of time.
 [01:28:37]  Okay.
 [01:28:38]  Okay, so this, even though there is a scope for automation, for now we are not concentrating on that.
 [01:28:45]  It will be more of a manual testing that will be done on a regular basis.
 [01:28:50]  And in terms of automation, it will just be the background scripts or backend queries that will be automated.
 [01:28:57]  Yeah, okay.
 [01:28:58]  Using custom scripts.
 [01:29:00]  So do you feel like this would be a right path for you to opt for?
 [01:29:05]  Because this is not going to be the normal UI testing or UI automation testing what you would be expecting for.
 [01:29:11]  Yeah, yes.
 [01:29:14]  I'm very much into that you said, mostly related on manual testing.
 [01:29:19]  Yeah, I'm very interested in that.
 [01:29:22]  So it will be convenient with that?
 [01:29:24]  Yes.
 [01:29:27]  Okay, fine.
 [01:29:29]  So can you tell me like what defect lifecycle is?
 [01:29:35]  Defect lifecycle is between happening between the tester and the developer.
 [01:29:41]  When there are some steps like new, open, undo, open,
 [01:29:50]  and then you can do it.
 [01:29:50]  test, fixed, retest and validation which has been done with
 [01:30:00]  tester will allocate a bug to the developer and he opened the bug and fixed that bug and
 [01:30:08]  and send it back to the tester and told him to recheck the bug which has been cleared or not
 [01:30:17]  after that he validated the results and he closed the bug
 [01:30:24]  Mm-hmm.
 [01:30:27]  Okay.
 [01:30:29]  So what is boundary value analysis?
 [01:30:32]  Sorry.
 [01:30:35]  What is boundary value analysis?
 [01:30:38]  Boundary value analysis which means black box testing.
 [01:30:46]  Black box testing means when the tester is testing any test case, it don't know the functionality
 [01:30:54]  of the test case.
 [01:30:57]  based on the input it takes the test output but it doesn't know what will be
 [01:31:02]  the functionality and another so that's the case
 [01:31:09]  Mm-hmm.
 [01:31:15]  Okay, what is a join in SQL?
 [01:31:19]  Join in SQL.
 [01:31:22]  Joins are nothing but joining, suppose, yeah, join, when two tables are there, we want to join the same data, which is ID.
 [01:31:35]  Suppose some data consists of employment, another table consists of names and all, ID, name, ages.
 [01:31:42]  So we want to using joins with help of joins we aggregate two tables joined together into one particular table.
 [01:31:56]  Yes.
 [01:31:59]  So what will be the syntax for querying to get employees with salary more than 10,000?
 [01:32:07]  Yeah.
 [01:32:08]  In SQL.
 [01:32:10]  Firstly, we select names, select names, comma, salary.
 [01:32:16]  Okay.
 [01:32:17]  So salary from employees and so in this we have to use where salary would be greater than 10,000.
 [01:32:27]  So yeah, 10,000 is a code.
 [01:32:30]  When we run the query, it will show the people who are above 10,000, they are being listed out.
 [01:32:38]  where and above greater than symbol will be main in this query.
 [01:32:46]  where is no nothing but the filter which will filters a group of data which which are above
 [01:32:54]  10,000 salary.
 [01:32:58]  Okay.
 [01:33:00]  So what is negative testing?
 [01:33:03]  Sorry?
 [01:33:04]  Negative testing.
 [01:33:05]  What?
 [01:33:06]  Yeah.
 [01:33:08]  Negative testing means...
 [01:33:16]  I'm going to do testing.
 [01:33:19]  Sorry, sir.
 [01:33:27]  Yeah, negative testing means invalid or unexpected, right?
 [01:33:36]  Negative testing means when we are doing something testing,
 [01:33:42]  we check the wrong inputs and other wrong inputs,
 [01:33:46]  handles correctly or not,
 [01:33:48]  which is also called as verification and validation.
 [01:33:54]  Validate the results to the expected results.
 [01:33:57]  Yeah, so with nothing but testing the invalid or wrong results means wrong errors which
 [01:34:09]  has been raised.
 [01:34:11]  So that has been cleared or not.
 [01:34:13]  That is known as negative testing.
 [01:34:18]  Mm-hmm.
 [01:34:22]  Okay, so let's say that a certain feature works on Chrome, but not on Firefox.
 [01:34:29]  What are you supposed to do next?
 [01:34:32]  uh
 [01:34:37]  I will reassign the web driver.
 [01:34:41]  Suppose I will correct the,
 [01:34:45]  I suppose we firstly were able to deliver,
 [01:34:49]  we attach a web driver in that,
 [01:34:52]  like a Chrome web driver or Firefox web driver.
 [01:34:55]  When it is not running,
 [01:34:56]  we check the latest version is there or not,
 [01:34:59]  or any errors has been there, I will,
 [01:35:04]  rerun the code and recheck the code and it will take the path and other selectors things
 [01:35:13]  correctly or not.
 [01:35:14]  So that's the case.
 [01:35:17]  Selectors and locators are attached to the web drivers, web driver like Chrome or Firefox
 [01:35:27]  properly or not.
 [01:35:28]  So based on that, we able to move forward.
 [01:35:34]  Okay.
 [01:35:38]  So can you think of a reason why the butters in the elevator, right?
 [01:35:43]  They are arranged vertically.
 [01:35:47]  buttons in the elevator yeah you have this lift right yeah the buttons arranged vertically yeah
 [01:35:58]  because of accessibility accessibility and space according to the space they
 [01:36:10]  have they have been kept like that like
 [01:36:18]  When we enter into a lift, we see downwards as a human.
 [01:36:25]  We are checking whether it's a normal human thing that when we enter anything, we will
 [01:36:35]  take from downwards to upwards.
 [01:36:37]  So when we see downwards, vertically, it will be kept there to access the keys properly.
 [01:36:46]  So that's the reason accessibility and space like that.
 [01:36:53]  Natural eye movement goes into that particular region.
 [01:36:59]  When we enter anything, like when we open a door, door is on the same place.
 [01:37:05]  So same position where the lift keys are present.
 [01:37:09]  So that's the reason when we enter into the lift, it's like a door box.
 [01:37:14]  So we automatically, our eyes will be there on that position.
 [01:37:21]  Mm-hmm.
 [01:37:25]  Okay, so what is the primary key in MySQL?
 [01:37:29]  Primary key is a unique key, which is on a suppose.
 [01:37:36]  So it is a unique.
 [01:37:38]  Suppose we anything we have to enter IDs of some certain employees.
 [01:37:44]  We have to use primary key, which cannot be primary key means one, two, three.
 [01:37:49]  It cannot be repeat like one, one, one comma one.
 [01:37:52]  so it cannot repeat to one number again after some time so that's we use primary key and also
 [01:38:00]  it cannot be kept null so it automatically used to follow from place one to etc how many
 [01:38:10]  employees are there from that ids has been mentioned with the primary key
 [01:38:14]  Mainly in IDs, we mainly enter primary key.
 [01:38:20]  So how do you see using a foreign key and a primary key between two tables or can they
 [01:38:30]  have its own primary key?
 [01:38:34]  primary primary key yes because every table has its own primary key I should
 [01:38:49]  uniquely identifies
 [01:38:52]  In a specific case, some relationship tables or anything, foreign key is nothing but the same key which can be used in different tables.
 [01:39:02]  But when it comes to primary key, which has been kept in a particular table to mention the specific IDs and all.
 [01:39:12]  When it comes to foreign key, it not work like that.
 [01:39:16]  It can be used in various tables and so yeah, primary key is different.
 [01:39:25]  Every table it should have a primary key.
 [01:39:30]  Mm-hmm.
 [01:39:33]  So what would be the query to find the max salary in the employee table?
 [01:39:39]  Nothing much.
 [01:39:41]  It's select names, comma, max salary from employees.
 [01:39:47]  Simple.
 [01:39:48]  Max is a keyword in that.
 [01:39:51]  What is the difference between distinct and group by?
 [01:39:57]  Distinct and group by, right?
 [01:40:00]  Group by will be done after the
 [01:40:13]  of by yeah group by means um when two or more filters has been done they have been grouped in
 [01:40:23]  in in particular way to kept all the all all the parameters in the um equal manner when it comes to
 [01:40:33]  distinct to distinct will remove duplicates from the sql records uh when it comes to uh which is
 [01:40:41]  called a group by which will include all duplicate case and all distinct will remove the duplicates
 [01:40:51]  Uh-huh.
 [01:40:57]  So do you have any hands on on MongoDB?
 [01:41:00]  MongoDB, yeah, yes.
 [01:41:03]  Because my project is based on like that.
 [01:41:07]  MongoDB, no SQL.
 [01:41:10]  MongoDB is a no SQL database.
 [01:41:13]  But data will be not in tabular form, which is a mixture
 [01:41:18]  of data will be there.
 [01:41:20]  So.
 [01:41:21]  In my project, I have extracted MongoDB data to SQL data by using Python.
 [01:41:30]  I'll use some libraries with the help of libraries.
 [01:41:35]  I've extracted the database results from non-SQL to SQL database.
 [01:41:46]  Okay. So what is the index in MongoDB?
 [01:41:50]  Sorry, index in MongoDB, right?
 [01:41:52]  Index is nothing but when we include db dot, suppose db dot enter anything, db dot create table,
 [01:42:05]  db dot create table, bracket open and include some datas like name, ID, mention and all.
 [01:42:14]  according to that we declared our values it can be in a uneven manner when it comes to a scale
 [01:42:21]  which is different we particularly mention name id and that id value in the next day we use values
 [01:42:33]  as a keyword in that we mention the values like id number name and like that when it comes to in
 [01:42:39]  in a noise kill db dot some db dot file name and create table will be used to in that bracket open
 [01:42:48]  id name mention anything will be there
 [01:42:51]  It can be implemented like that.
 [01:42:55]  So what is the primary use of having an index?
 [01:43:06]  in which
 [01:43:09]  for a MongoDB collection.
 [01:43:10]  Yeah.
 [01:43:12]  Primary is the select queries.
 [01:43:18]  uh sorry sir index is uh helps to speed up the data to get a faster data performance
 [01:43:27]  uh when it comes to the other one um index will helps to get the data access free uh
 [01:43:35]  where suppose when we access some data uh we need uh we need all all data we don't know particular
 [01:43:43]  right it means we cannot get data as soon as possible when you have indexing and all we can
 [01:43:49]  access the data within seconds so that's the main in mongo db
 [01:43:56]  speed will be more
 [01:44:00]  Okay.
 [01:44:05]  Okay, so one final question.
 [01:44:07]  Yeah.
 [01:44:07]  So let's say that you are in a room with three switches.
 [01:44:11]  Three switches.
 [01:44:12]  Yeah.
 [01:44:13]  Yeah.
 [01:44:14]  And there are three bulbs in another room.
 [01:44:19]  You can enter the bulb room only once.
 [01:44:22]  Okay.
 [01:44:24]  How do you identify which switch controls which bulb?
 [01:44:29]  or how is it connected?
 [01:44:32]  I have to think that
 [01:44:33]  um
 [01:44:34]  hmm
 [01:44:46]  suppose switch on the light light or anything light one two three let get ready for five to
 [01:45:00]  ten minutes 15 minutes right now the heat will be processed
 [01:45:06]  with the when the energy will be captured for more than 5 to 10 to 15 minutes the energy will be
 [01:45:12]  come from the bulb so it can be hot when it comes to the two bulbs suppose there are one two three
 [01:45:19]  bulbs suppose two will be two switch which i have one another switch one bulb will one
 [01:45:27]  It can be captured for 5 to 10 minutes and switch off that and let me come to the room and check the weather in 3 bulbs which bulb is hot. That is the bulb which I have selected in the switch room, switch board.
 [01:45:47]  Mm-hmm.
 [01:45:51]  So what if the bulb doesn't get heated up?
 [01:45:55]  heat enough I will I will do the like it will grow some amount of change will be there when
 [01:46:06]  it comes to the other one or if not 15 minutes will be the time limit if there is no time
 [01:46:12]  limit it will be possible if there is time limit there would be another way of doing
 [01:46:20]  So what if let's say the time taken from for you to reach from room one to room two takes like 20 minutes?
 [01:46:27]  Yeah.
 [01:46:30]  In that case, how will you identify?
 [01:46:44]  same sir
 [01:46:47]  same as I will kept the light on for 30 minutes I guess 30 minutes 25 to 30 minutes and turn
 [01:46:56]  off like that when it comes to 30 minutes the amount of heat to
 [01:47:03]  heat duration will be more when it come when i kept the time limit with more uh the heat duration
 [01:47:10]  will be more so when it come when i come back from room one to room to 20 minutes it will be
 [01:47:17]  the same heat will be there when it comes it will it will become much colder
 [01:47:21]  uh the other two bulbs one will get a normal or it get to
 [01:47:26]  or one one will get to some some zero to two to three degrees celsius
 [01:47:34]  What if all the three bulbs are in the same temperature group?
 [01:47:39]  all the three bulbs are in same temperature.
 [01:47:44]  When three bulbs are in same temperature,
 [01:47:51]  uh
 [01:47:57]  No, sir. I have no idea how to solve that.
 [01:48:01]  Because if there is only way is that I have already asked this question once.
 [01:48:08]  So they have not gone through deeper.
 [01:48:14]  Mm-hmm.
 [01:48:17]  Okay.
 [01:48:20]  Can you tell me...
 [01:48:24]  given a pencil right yeah so what are the test cases that you will be testing that
 [01:48:30]  in case you wanted to launch that as a new product in the market yeah i understood uh
 [01:48:38]  It includes like a check pencil will be right on paper or not.
 [01:48:46]  Suppose this is a pen.
 [01:48:48]  It's run on a paper or not.
 [01:48:53]  Verify pencil has been sharpened or not to write in that.
 [01:48:57]  Because where no sharper is there, it cannot write right.
 [01:49:03]  So it can write on the paper.
 [01:49:06]  and
 [01:49:08]  suppose the
 [01:49:13]  take the eraser and check whether the written word has been erased properly or not and it
 [01:49:24]  can consistently work from time period like from
 [01:49:30]  specific time frame like a one hour two hours it can be run properly like that so it can be checked
 [01:49:36]  and when you sharpen it will hold the shape correctly or not because the when you sharpen
 [01:49:43]  the pencil some amount of the top will be removed so it will be checked like that it will write the
 [01:49:52]  properly on paper when it comes to first this case would be properly right on paper and checking the
 [01:49:59]  sharpness like
 [01:50:00]  thickness and sharpness when it comes to erase how the amount of volume has been
 [01:50:08]  erased like density how much density the pencil has been progressed to write on a
 [01:50:14]  paper and when it comes to another test case would be sharpening how the
 [01:50:20]  sharpening will be takes place
 [01:50:21]  yeah these are the and in that one more thing graphite is the lead which has been used in
 [01:50:31]  pencils which has been working properly or not right which has been correctly kept or not
 [01:50:40]  is graphite is a proper amount of graphite is used or not
 [01:50:44]  Based on that we will decide.
 [01:50:49]  These are now four to five.
 [01:50:50]  This is more towards the functionality of the pencil, right?
 [01:50:53]  Yeah, yeah, yeah.
 [01:50:54]  Writing whether it's able to erase all of that.
 [01:50:56]  Right, right.
 [01:50:56]  So what will be the UI-specific test cases that you can think of?
 [01:51:02]  UI-specific?
 [01:51:04]  Yeah.
 [01:51:06]  UI-specific.
 [01:51:19]  like how to design
 [01:51:22]  um la us specific would be about design how the uh uh in a toolbar right painting painting is the
 [01:51:33]  main example how the painting would be done properly like uh when you move the cursor on in ui
 [01:51:42]  um like when you use um
 [01:51:45]  suppose in a laptop and anything the mouse has been correctly working when
 [01:51:51]  the cursor is moving like that the pencil icon is visible or moving from
 [01:51:57]  one place to another place has been checked and aligned with the correct
 [01:52:02]  properly or not and
 [01:52:05]  suppose it can overlapping with any other elements has been kept has been
 [01:52:09]  checked and along with that we check the eraser in that also how the eraser will
 [01:52:18]  working the pencil after the pins after drawing a line with pencil the erase has
 [01:52:25]  been done one done properly or not and
 [01:52:29]  yeah check the cursor is attached to that it will work properly or not open
 [01:52:37]  the open that and
 [01:52:43]  write a proper proper word or not it can be tested yeah it can be tested the cursor is
 [01:52:52]  correctly attached and correctly synchronized with the pencil or pencil line which has been
 [01:52:59]  in the ui like a laptops and taps so we check like that and it works properly or not
 [01:53:06]  while erasing or anything or working with cursor
 [01:53:10]  So it works properly or not, they'll check like that.
 [01:53:15]  It can be same test case scenarios, but two to three test cases will be different when it comes to the practical and UI based.
 [01:53:30]  Okay. Yes, I am done with my interview. So do you have any questions for me?
 [01:53:40]  How I'm asking, how would be the career if I choose a manual testing in this company?
 [01:53:52]  So here it is not just limited to the basic whatever manual testing that they teach you as part of a course or you learn it somewhere, right?
 [01:54:01]  So you will be having access to the production servers and even non-production servers.
 [01:54:07]  So it will be more of an end-to-end testing that you will be expected to perform.
 [01:54:13]  So we will have a close team wherein you will get a chance to interact directly with the developers.
 [01:54:19]  We'll be like closely connected and you will be handed over features.
 [01:54:24]  Wherein in other companies will just be you will be allocated few test cases.
 [01:54:28]  You will not get any exposure more than that.
 [01:54:31]  Yeah.
 [01:54:32]  Yes, thank you. Thank you for your feedback.
 [01:54:37]  Yes. Thank you, sir.
 [01:54:38]  Have a nice day.
 [01:54:39]  Yeah. See you.
 [01:54:40]  Bye.
 [01:54:41]  Bye, sir.
 [01:55:53]  Okay, Karthik.
 [01:55:57]  Yeah, can you please turn on your camera?
 [01:56:02]  Okay, sir.
 [01:56:12]  Okay, shall we start?
 [01:56:14]  Yes, sir.
 [01:56:17]  Okay, can you just give me a brief overview of yourself?
 [01:56:20]  Good.
 [01:56:23]  Thanks for this opportunity.
 [01:56:28]  Myself, Karthik Bani.
 [01:56:31]  I am from Bhopal Paly district.
 [01:56:34]  I have completed my B.Tech in Computer Science in Bhagav Engineering College at Varangal,
 [01:56:42]  Goli Kundra.
 [01:56:43]  I came from a nuclear family which consists of my father, mother and sister including
 [01:56:48]  me.
 [01:56:49]  And my hobbies were playing cricket and reading books.
 [01:56:57]  My short term goal is to get a job in a reputed company.
 [01:57:04]  That's it, sir.
 [01:57:07]  So do you have any previous internship experience?
 [01:57:11]  No, no, no, no, sir.
 [01:57:14]  Okay. So why software testing?
 [01:57:19]  myself I'm interested in to test I mean I'm interested to check from my
 [01:57:30]  childhood how it is working like if
 [01:57:37]  If something is working, why it is working, how it is working from childhood I am interested in.
 [01:57:46]  That's why I came from small interest.
 [01:57:52]  So do you like do any testing courses or how is it what is your like technical background?
 [01:58:00]  Yes sir, I am preparing and learning manual testing and automation testing from 3 months
 [01:58:14]  in with my from my own no no not from any institute or in there I didn't do any
 [01:58:24]  certifications how do you validate yourself like how confident are you in
 [01:58:30]  over the past three months
 [01:58:34]  I didn't have practical hands-on experience, but I have everything for conference.
 [01:58:43]  Okay, so tell me what is test coverage?
 [01:58:49]  What is test coverage?
 [01:58:52]  Test coverage means what are the functionalities we are going to cover which are specified
 [01:59:05]  in user requirement.
 [01:59:08]  document that means software customer requirements specification that means
 [01:59:16]  whether our whether our test cases are covering all criteria that means user
 [01:59:23]  user specifications or not how
 [01:59:28]  How many test cases were passed?
 [01:59:30]  That means we created 20 test cases.
 [01:59:36]  How many test cases were passed?
 [01:59:38]  How many test cases were failed?
 [01:59:40]  How many was assigned as fixed or closed?
 [01:59:45]  That's it, sir.
 [01:59:48]  So what is the test scenario?
 [01:59:56]  That means for what functionality we are going to cover.
 [02:00:00]  going to test us for example we are going to test for a in banking application we are going to
 [02:00:10]  transfer amount from one account to another account sir in that we are going to test the
 [02:00:18]  field field cases that means text will user go user user going to fill you his
 [02:00:29]  are his account number and receivers account number then he will press the
 [02:00:35]  transfer button so then I'm on should be transferred in this case we have to test
 [02:00:40]  with the
 [02:00:46]  That means we need to test with alpha numeric values for account numbers, numeric values with amount fields.
 [02:00:58]  This is a scenario, sir.
 [02:01:01]  From scenario.
 [02:01:02]  So then what is the difference between a test case and a test scenario?
 [02:01:08]  For this scenario, we should write in efficient test cases.
 [02:01:13]  That means we should check exactly from positive test cases.
 [02:01:19]  That means we should test with alpha numeric values for account number.
 [02:01:27]  For user account number, we need to test with alpha numeric values.
 [02:01:30]  If it takes, that means if it takes, it will be...
 [02:01:37]  Okay, sir. Test case will be passed. Otherwise, test case will be failed, sir. This is test case, sir. We should test for each and every criteria for this scenario, sir.
 [02:01:50]  Mm-hmm.
 [02:01:55]  So what is severity and priority in defect management?
 [02:02:01]  Severity and priority, sir.
 [02:02:03]  So severity means if I tell one scenario, sir, better understand.
 [02:02:15]  Can I?
 [02:02:15]  I think I'm not able to hear you.
 [02:02:18]  Sir, can I go through a simple example, sir?
 [02:02:21]  Still no.
 [02:02:23]  Sir, if a tester found a defect, that means obstacle, during testing, sir,
 [02:02:33]  How much effect is there with that obstacle?
 [02:02:43]  Is it not audible?
 [02:02:47]  Hello?
 [02:02:48]  Hello.
 [02:02:52]  I'm audible?
 [02:02:53]  I'm audible?
 [02:02:54]  You are audible, Karthik.
 [02:02:55]  Ah.
 [02:02:56]  Severe, severe, just a minute, just a minute, Karthik.
 [02:02:59]  I think Shant is not audible.
 [02:03:06]  I think sir is in, he's going, he's not able to hear me.
 [02:03:12]  Yeah, exactly.
 [02:03:14]  Just a minute.
 [02:03:21]  He's joining again.
 [02:03:23]  Prashant, is it audible now?
 [02:03:26]  Yeah.
 [02:03:27]  Can I continue?
 [02:03:30]  Yeah, please.
 [02:03:31]  CBRT means how...
 [02:03:35]  how the damage is that defect is going to do.
 [02:03:39]  That means how much loss is done to the customer.
 [02:03:43]  That means how much losses, I mean, if,
 [02:03:47]  if example scenario, if a login page is failed,
 [02:03:53]  if we have defect in that section,
 [02:03:57]  If we don't, user would don't log into that application, should not, isn't able to log into that application and he cannot use that application.
 [02:04:07]  That means we stuck in beginning, sir.
 [02:04:10]  It is a severe loss, sir.
 [02:04:15]  He cannot use, user cannot use it.
 [02:04:17]  It is a severity.
 [02:04:19]  Priority means how...
 [02:04:23]  That means how fast we should fix that test case.
 [02:04:30]  That means if in the same scenario, we should fix that login functionality issue,
 [02:04:37]  then only user should use that application.
 [02:04:39]  That means it has higher priority.
 [02:04:42]  That means without fixing that issue,
 [02:04:45]  user cannot use that application sir that is priority sir that means we should solve it that bug immediately sir
 [02:04:56]  Mm-hmm.
 [02:05:00]  Okay, what are the different levels of testing?
 [02:05:04]  different levels of testing.
 [02:05:19]  Sir.
 [02:05:25]  functionality testing.
 [02:05:29]  Hello.
 [02:05:30]  Yeah.
 [02:05:31]  Functionality system.
 [02:05:33]  In the integration testing.
 [02:05:36]  system testing, acceptable testing.
 [02:05:42]  So what is the defect like cycle?
 [02:05:48]  defect life cycle involves how the bug is that means how bug is born and dead
 [02:05:56]  that means defective defective arise arise it will be stated as it will be
 [02:06:06]  stated as new
 [02:06:08]  status then after tester is assigned to developer sir then status will be that means stay bug state
 [02:06:18]  will be a change to assign then after developer will look into it look into that bug sir then
 [02:06:27]  after it is that means state will be changed to
 [02:06:36]  state will change it sir then after developer will fix it fix it sir that means he
 [02:06:45]  state changes to fix it sir in progress before that in progress sir where when
 [02:06:52]  when developer looking in looking to that bug he before he fixing
 [02:06:57]  status will be changed to in progress after that fixed that means fixed sir or else he whenever
 [02:07:07]  the tester will find again issue in that bug he will change that status to reassign
 [02:07:19]  Okay, so when do you stop testing?
 [02:07:22]  Sir?
 [02:07:24]  When do you stop testing?
 [02:07:26]  Stop testing.
 [02:07:28]  That means if in acceptable testing, that means whenever the software meets that user requirements, that means...
 [02:07:41]  In acceptable testing, testers will do like users or end users.
 [02:07:48]  If there is no obstacles during using that application, we cannot proceed with further
 [02:07:56]  testing.
 [02:07:57]  It is the last testing.
 [02:08:00]  So who takes this call?
 [02:08:05]  Sir?
 [02:08:05]  Like, let's stop testing here.
 [02:08:08]  Who takes that call?
 [02:08:11]  team testing team leads
 [02:08:15]  testing team lead.
 [02:08:17]  Yeah.
 [02:08:19]  Okay.
 [02:08:20]  So can you test an application without any requirement or documentation?
 [02:08:28]  Yeah, requirement and documentation, sir.
 [02:08:32]  Yeah, without any documentation.
 [02:08:35]  From beginning or in middle, sir?
 [02:08:38]  From beginning.
 [02:08:39]  From beginning.
 [02:08:44]  without documentation and requirements.
 [02:08:48]  Yeah.
 [02:08:49]  So yes, we can test with exploratory testing.
 [02:08:53]  Sir.
 [02:08:54]  Mm hmm.
 [02:08:56]  So what is exploratory testing?
 [02:08:58]  Without user requirements, that means customer requirements, we can do testing.
 [02:09:07]  When we have customer requirements, that means we can focus to design test cases for those customer requirements.
 [02:09:20]  whenever customer using that end product that means end application he will
 [02:09:28]  sometimes he will use a random that means which which are some some
 [02:09:36]  activities which are doesn't cover in
 [02:09:39]  and user user specification that means customers customer requirements that will be covered in
 [02:09:50]  exploratory exploratory testing it means we have testers will do
 [02:09:57]  testing in more flexible
 [02:10:00]  with the without user requirements he will he will do testers will do testing with a wide range of
 [02:10:12]  scenarios when you specify the application with scenario just one scenario he will do he will go
 [02:10:20]  through that application sir so what to what the application will need across how will will work
 [02:10:28]  he will go through it sir for that he will need some basic domain knowledge for that application
 [02:10:35]  what he is going to build what he is going to test
 [02:10:39]  He will test beyond test cases, beyond requirements.
 [02:10:44]  He doesn't need to, tester will doesn't need requirements.
 [02:10:50]  He needs, but without also we can build test cases and test the application.
 [02:11:00]  Uh-huh.
 [02:11:04]  So how do you test a text box that accepts a password?
 [02:11:09]  I can tell with selenium.
 [02:11:15]  Hmm. Okay.
 [02:11:17]  Selenium or manual?
 [02:11:19]  Either ways.
 [02:11:21]  Sir?
 [02:11:22]  Either ways, whichever you are convenient with.
 [02:11:25]  Okay, sir.
 [02:11:25]  I can tell with selenium, sir.
 [02:11:31]  Can you repeat the question once again?
 [02:11:35]  No, so you are given a text box that accepts a pass note.
 [02:11:37]  So how do you test both?
 [02:11:40]  I can tell for both manual and automation.
 [02:11:44]  For manual, in a text field,
 [02:11:51]  for password sir in password they will mention one criteria sir it should accept
 [02:11:59]  your capital letter one capital letter special character number small letter
 [02:12:06]  etc we should select with all the character first alphabet sir
 [02:12:12]  manually, it should fail sir. This is one test case. And then after we should test with
 [02:12:20]  all numbers, then after we should test with all special characters, then after one mix
 [02:12:24]  sir, then after each in each cases miss one one characters, that means number you should
 [02:12:31]  miss and special character you should miss, capital letter you should miss and small letters
 [02:12:37]  you should miss all this all this criteria should be tested manually
 [02:12:43]  one only only one criteria should be passed so that means one test case should be first whenever
 [02:12:50]  you specify that specified criteria that should you should enter the password with
 [02:12:58]  special character small small that means small alphabets and big alphabets
 [02:13:07]  numbers whenever you should enter that mixed kind of characters it should pass that test case sir
 [02:13:15]  it is it is from manual sir by using selenium we can selenium web driver sir
 [02:13:25]  by using a JavaScript executor, we can fill that text field, sir.
 [02:13:38]  Or else, by using...
 [02:13:43]  Selenium WebDriver methods.
 [02:13:47]  Okay.
 [02:13:50]  So let's say that you have reported a bug, but the developer says it's not a bug.
 [02:13:55]  Okay.
 [02:13:56]  So what would you do in this case?
 [02:13:58]  Sir, once I thoroughly go through whether I should properly test it or not, sir.
 [02:14:08]  Then after I should recheck, that means retest it, sir.
 [02:14:13]  Go through the requirements, that's what...
 [02:14:19]  what I test previously from root cause sir where this bug for what in what scenario that
 [02:14:29]  this bug this defect is arise previously and then after I will check in different browser and
 [02:14:41]  different operating systems whether I have appeared that defect in some other OS that
 [02:14:53]  means I am using Windows developer will using Linux something.
 [02:15:02]  In that it doesn't work means it should my we will fix that issue sir.
 [02:15:14]  Compatibility testing that means.
 [02:15:19]  If the defect found in any OS or any browser, I would take the screenshots, proof of the defect, attach it to the defect below and provide it to developer for proof.
 [02:15:43]  Uh-huh.
 [02:15:47]  Okay, how do you test the application that has no UI?
 [02:15:51]  No UI.
 [02:16:01]  No, you're in the...
 [02:16:06]  Simply form checking, sir.
 [02:16:11]  I can't understand the question.
 [02:16:13]  So form itself is a UI, right?
 [02:16:15]  Yes, sir.
 [02:16:16]  Let's say it's a server-side application or a Linux-based application.
 [02:16:21]  Link-based application.
 [02:16:23]  Linux, Linux operating system-based.
 [02:16:26]  Okay.
 [02:16:28]  So the application is going to run on the server only,
 [02:16:31]  which will not have a login page or a form or anything of that sort.
 [02:16:40]  by using API testing, sir.
 [02:16:44]  What is API testing?
 [02:16:48]  How is API testing going to help that?
 [02:16:55]  then go
 [02:16:56]  sorry
 [02:17:00]  Sorry?
 [02:17:01]  I didn't go.
 [02:17:02]  I didn't know, sir.
 [02:17:04]  Okay, what if application crashes only on a particular environment?
 [02:17:14]  What is that you'll be checking there?
 [02:17:18]  Sir?
 [02:17:21]  Only on a particular environment, let's say application crashes.
 [02:17:24]  Yes, sir.
 [02:17:25]  So what is that you'll be looking further into it?
 [02:17:28]  How will you approach, like what will be your approach of reproducing the issue?
 [02:17:34]  Once checked, whether he should work with this environment and must go through requirements first.
 [02:17:49]  Then after,
 [02:17:53]  communicate with the user customer or user to whether he is going to do whether he whether
 [02:18:03]  he want this environment or not first we have a clarifier then after I should rectify
 [02:18:13]  that we where in all aspects of testing where the obstacle is occurring that means whether i should
 [02:18:25]  change environment that means how
 [02:18:31]  the test environment gonna major issue how can we
 [02:18:45]  how can we cover it sir that means we can use better we can if this test application
 [02:18:51]  crashes in windows 10 we can use it in some other os so if the application works at some
 [02:19:01]  other environment that means in windows 11 or linux
 [02:19:07]  first customer specify that customer it will be only cast in in specified environment so
 [02:19:16]  we should mention to the customer sir but customer would don't don't he doesn't use
 [02:19:23]  his environment that means he doesn't use a specified environment that means he doesn't
 [02:19:30]  he use windows 10 windows 11 any any environment any environment sir we should fix that environment
 [02:19:35]  we should take scenarios which
 [02:19:40]  which you would make better
 [02:19:46]  That means we should fix that application to run in all OSR by that means selenium
 [02:20:00]  sir we can use it by using selenium grid we can test it sir if it doesn't work we should
 [02:20:09]  we should specify that your application mode doesn't work in this windows or browser for this
 [02:20:16]  browser yes that's it
 [02:20:22]  Okay. So how would you test the toggle button?
 [02:20:27]  Sir?
 [02:20:29]  How will you test a toggle button?
 [02:20:32]  toggle button
 [02:20:37]  So,
 [02:20:59]  Don't know.
 [02:21:02]  Okay.
 [02:21:05]  Yeah, so I'm done with the interview.
 [02:21:06]  Do you have any questions for me?
 [02:21:10]  Is it relevant to know?
 [02:21:15]  Sir, can you tell me?
 [02:21:21]  How I answered to the questions?
 [02:21:26]  Okay, so as you told like you have started learning it on your own.
 [02:21:31]  I didn't take much of a technical questions.
 [02:21:34]  So these are kind of mostly logical and basics of testing.
 [02:21:39]  Yes.
 [02:21:40]  I would say you should furthermore improve on the basics of testing in terms of getting the right keywords.
 [02:21:50]  Okay.
 [02:21:51]  Okay.
 [02:21:53]  Yeah.
 [02:21:54]  Anything else?
 [02:21:56]  Thanks.
 [02:21:57]  Thanks.
 [02:22:05]  Karthik, you can leave.
 [02:22:09]  Prashant actually it's done. I have scheduled for the five people on it.
 [02:22:15]  Sure.
 [02:22:16]  Any feedback or like will you inform in the group?
 [02:22:21]  I think it's fine. Maybe I have captured it in multiple sheets.
 [02:22:24]  Maybe I can put it on the group.
 [02:22:26]  So one thing what I see is like the Karthik and the previous guy, right?
 [02:22:32]  Not the cognizant.
 [02:22:38]  Baskar.
 [02:22:39]  Yeah, Baskar 2025.
 [02:22:41]  So, yeah, so these both looks like they're making use of other tools, at least with their eye movement and stuff, right?
 [02:22:49]  But across more towards...
 [02:22:54]  Yeah, please go ahead.
 [02:22:55]  Same thing for Karthik.
 [02:22:57]  I also felt it for Baskar.
 [02:22:59]  Yeah.
 [02:23:00]  So Baskar initially, he started with less confidence.
 [02:23:04]  But over a point in time when certain things were discussed,
 [02:23:08]  it sounded more like he's reading from the screen.
 [02:23:12]  Got it.
 [02:23:12]  I will just take care of what it means.
 [02:23:14]  Yeah. So, yeah, maybe I will consult it and share it on the group, no?
 [02:23:21]  Yeah, sure. If you want the scheduling means, let me know. So based on that 2025 or like based on whatever the expectations, I will just move forward.
 [02:23:30]  Yeah. So let me check that again.
 [02:23:35]  Yeah, you can check and let me know.
 [02:23:38]  Yeah.
 [02:23:38]  Yeah. Thank you.
 [02:23:40]  Thanks.
No results found