Transcript for:
Mock Interview Review for Candidate Niharika

okay so before uh going to start uh let me  just give you a few instructions and then we   will start okay so this is going to be a walk-in  review and which is also will be recorded and uh   will be uploaded on youtube later and  because others also learn something   from it and the second thing is and don't be  nervous and be confident okay and uh yeah so   let us start with this are you okay with that  yes very fine okay great yeah so uh based on   your profile i have just considered your profile  as a fresher okay and uh and also you mentioned   skills like manual testing and then manual  testing java and sql right these are the basic   three different skill sets you mentioned in  your resume so let me ask some basic questions   because i consider your profile as a fresher so  let me just go with some basic questions right   okay so okay uh shall we start now yes sir  okay great so can you just introduce yourself   what is your experience and uh yeah your  qualification what is your skill set yeah myself niharika i'm basically  born and brought up in bangalore   um i have completed my b  tech in computer science uh   in uh uh vijay vital institute of  technology with aggregate of 60 65 and coming to my skill set i know um manual testing manual testing um  then basics of java and sql okay   okay great so uh what do you know about  sdlc software development lifecycle uh sdlc uh uh this is the uh uh step by step  procedure uh which we follow for uh developing a   uh new software okay and what are the  different phases or including sdlc the this is involved requirement gathering requirement gathering analysis design   coding testing installation and uh maintenance and  support okay and this yeah yeah tell me proceed yeah in the requirement gathering uh the ba  will go to the customer place and collect the   uh requirements from the customers and uh he  will collect it in the business language and   he will convert that into the software language  and explain it to the team uh and once after the   requirements are collected then analysis phase  comes uh in this phase um a team um will be   there with the business analyst along with the  design architects along with the architects   hr and finance team where they  will do the feasibility study   of the technical feasibility study uh  resource feasibility study as well as the uh   finance feasibility study okay uh after after  they do the uh once the feasibility study is   done here the project manager will decide  whether to take up this uh project or not   based on the requirements and after after uh  taking up the project the next process is the   design phase here the senior architects um and uh  will uh will do the no no just tell me just very   high level action so i don't need any internal  water the task will be done so what exactly   happening the requirement what will happen in the  design and coding testing and the production right   so let's say in the requirement analysis phase  mainly business unit project managers or product   managers these people will be involved and during  the design and development so development people   will involve so they do some kind of design  like high level design low level design   and accordingly they'll write the code during  the coding phase and then testing will come   into picture and after completion of the testing  so then will production will start okay so this   is very high level information about sdlc okay  you don't need to go in detail of sdlc until   until unless i ask the question okay if  anybody asks you explain in detail about   sdlc then you need to explain what each and  every activity will be done in the sdlc okay   fine so what do you know about stlc so do you  know about stlc yes yes tlc yeah yeah what is sdlc   it is a software testing life cycle okay um it  is a process which is followed for the testing   process okay then in the in the stlc there are  like uh there is a system study uh writing the   test plan um writing the test cases okay then  requirement traceability writing the requirement   is ability matrix [Music] okay so that's it so  sdlc basically talking about the software testing   process which is a part of sdlc okay so sdlc is  talking about enter software development process   from the requirement to teal production but stlc  is a part of development process sorry so it's a   part of testing process okay it is talking about  only testing phase like during testing what you   will do we will understand the requirements  right and then we will writing the test case   that's part of designing and then we'll execute  the test cases and then finally we'll exit from   the test and we'll report the defects or bugs  to the developer so these are all activities   involved during stlc process okay there's a part  of enter sdlc okay great so do you know what are   the different models are available or under  sdlc like software development process models   yes yeah what are the different models are  available uh waterfall model okay um v model   spiral model okay prototype model agile  model okay so do you know about v model yes   okay so how the how the development and  testing activities will go on av model   uh they go on in a parallel law okay parallelly  the development and the testing will be happening   from the first phase itself okay so  from the first phase in the sense from the requirement gathering phase  okay okay so from the requirement   and uh uh you are saying like from the  beginning like from requirement design testing   development in each and every  phase testing will be there right   okay fine yes during testing phase as a tester  we will do the functional testing but in initial   levels like in the requirement phase and design  phase how the testing will happen in the model um we will review the   documents so uh static testing is done  okay great so what is status static testing   uh testing any uh software um based on the  documents it's called has they okay so let me just   clarify it so basically uh in v model so we will  have each and every phase of testing right but in   the phase of requirement analysis or designing by  the time we don't have any software only we have   only documentation right so by the time we don't  have any software to be ready until unless the   development is done software is not it ready right  so during requirement design phase so we will   review the document we will test the documentation  like the documentation means what the documents   again talk about the software how it will be  what are the different features should be there   right so we will verify whether the documents  are correctly written or not completed or not   so that is comes under static testing because  we are going to test only documentation part   until unless the software is ready right once the  software is ready once the development is started   then software will be ready then we do dynamic  testing so there we will exactly test the software   okay so that's the basic difference so in the v  model like uh development and testing will happen   parallely like uh while developing the developing  is doing unit testing a unit like development is   happening unit testing will be done so integration  testing and then system testing and uit testing   so these testings will happen depends on the  resp corresponding documents like we have a srs   document like we have a design document then we  have unit test plan then we have integration test   plan right so system test plan so based on those  documents we will parallely perform the testing   in the v model okay so do we know about anything  uh functional testing what is functional testing   uh functional testing is uh testing the  functionality or the behavior of an uh software um   okay so suppose there is an  application so how we will start   uh functional testing how will  perform functional testing suppose there is okay no problem so there is  an application let's say i have given some   application and uh you have to start functional  testing on that application so how we will start   what is your approach how do  you perform functional testing   so where we where you will start and what you  will refer before conducting functional testing   because a straightforward cannot directly start  function testing right if you want to test any   application you have to know something some  input you need to have you need to know something   about application right until unless you  know the application you cannot directly   start testing right so how do you perform  functional testing so how we will start   first the requirement study will be done exactly  after which after we will prepare the test data   for the input okay so will you prepare  test cases first or test data first no [Music]   okay when do you prepare test cases yeah test  cases right when do you prepare test cases um like after the test plan after writing the  test plan uh when uh we will write the uh   yes yes cases yeah so once you understood the  functionality right once you understand the   functionality then you start creating the test  cases and if there is any data is required for   the test cases then you will prepare test  data parallely along with the test cases   okay all right so the next question let's say  suppose uh i have given an application and you   want to test that application but i have not  provided to you any documentation so you don't   have any documentation by hand i would strive for  i have given an application so how to test that   application what kind of testing you will do we  will do the exploratory testing we will explore   the application um by using the application  and we will get to know the functionality   yeah great correct so exploratory testing means  without having any documentation so we'll just   explore the functionality it's basically learning  the application and then we will start testing   okay so what is regression testing uh regression testing uh testing uh   testing the modules um the modified  modules and also if there is any if the if there is any uh changes because  of change because of the change in one model   whether it is affecting the other modules or not  we are testing that in the regression testing   okay great so sometimes the developer made uh some  changes in the build so because of those changes   the existing functionality or some other  functionality we should not be impacted by   the changes right so sometimes developer may add  a new functionality or they will fix existing bugs   right so because of that they do some kind of code  changes and that should not be impacted on other   functionality for that we will test the existing  functionality also along with the new feature and   bug fixes so that comes under regression testing  so perfect okay so how to write a test case so what you will refer while writing the test case so what is the input you need to  know first of all so let's say   uh you have a join a project okay and suppose  your lead is asked to write some test cases   and what is the information you need to have  before writing the test cases what you should know um so you have to know the require requirements   yes you need to know the requirements  and where you will get the requirement   where you will understand the functionality  of your application until unless you know the   functionality you cannot write the test cases  right so where exactly will get the function   where you will know the functionality on what  basis you will understand the functionality using the test scenarios yes test scenario so  again how we will prepare the test scenarios   because test scenarios test cases you have  to write even if you want to write the test   scenarios so you need to know something right  you need to know the function of application so   where you can see the functionality how we  will know the functionality of application in the srs and the design document exactly srs means  a software requirement specification and   functional specification requirement which is  contains a detailed documentation which is in   understandable format more technical format and  testers and developers will able to understand   okay that's called frs functional requirement  specification document based on that   you can understand and fr is also  sometime contains the use cases   right use cases what what is the use case do you  know what is the use case use case is also part   of a requirement by seeing the use case you will  understand what is the input what is an action   what is an outcome so you will review all these  things and depends on that or based on that you   will understand the functionality and then you  will form the test scenarios and then you write   the test cases okay that's the process is there  any difference between test scenario and test case yes sir yeah what is the difference um   scenario is the high level uh documentation um  which we prepare uh looking at the requirement   test cases is the in detailed documentation we  prepare by looking at this in uh test scenarios   okay uh it is the steps to perform for the uh  executing the uh okay so yeah perfect so basically   test scenario is talking about very high level  functionality let's say what to test and test case   talk about how to test like what are the different  steps are involved what is an expected what is an   actual result so these things are included in the  test case so let's step by step action which we   need to perform on the application and then we  will check the expected and actually is exactly   equal or not so those things will be included in  the test scale but test scenarios is very high   level again test scenario we can again divide it  into multiple test cases so one test scenario can   have one or multiple test cases okay okay great  so good answer and let me ask a few more questions what is the difference between priority  and severity [Music] no priority is um   is the urgency of fixing the defector uh  severity is the how much impact it is uh   uh it is on the business okay business of the  customer okay so see where it is basically   talking about the seriousness of the defect how  it will impact the business right and priority   is nothing but how soon we need to fix that issue  it's basically talking about the time okay good   okay so what is the defect life cycle   can you explain yeah uh a defect life  cycle uh once once the test engineer is found out the defect then he  will uh uh he will state it as a   um open he will open the defect and he will  send he will communicate with the development   uh development development team and he will he will uh he will send this defect to the  development team so the development team will um   uh will develop a developer will make the bug has  the assign and once it is assigned um they will uh   develop developer will fix the uh defect and it  will be uh assigned uh like after fixing it will   be uh stated has the fixed and uh they  will send it send back to the test   for testing okay um then test engineer will uh  test this uh defect and if it is uh fixed uh   then he will close the defect and uh if it is uh  knotted fixed then he will sends back it as the   re open okay okay good so do you  know about uh agile agile process um the basics yeah okay sure no problem  so how the agile will different from other   traditional models like when you compare with  v model agile or waterfall models how agile   model will be different what is the main  advantage of agile process original model   is there any advantage when you compare with the v  model or other models would you have any advantage   of agile process or regional model yes sir we have  here the in the agile process the communication   in the team is good the communication will  be good and also uh here there will be a   less documentation okay documentation work  okay okay so based on that uh so because   of that we can provide the uh deliver the uh  software soon and quality will be good okay so   in agile process uh customer no need to wait  till the long time okay so you will get the   very frequent releases let's say there is a huge  functionality let's 100 features are there in   the application so customer no need to wait for  all 100 features to be completed as soon as we   completed some piece of software we will test it  and we will give the demo to the customer and if   he is okay we will release that piece of software  to the customer and apparently he is using it   and on top of that we will add few more features  and again we will start development and testing   process so customer is mainly no need to wait for  long term to complete entire software so we can   uh deliver a piece of software in  intervals okay there's a main advantage of   agile process okay great so let me just give  you a one scenario so you can just tell me uh   how we can test it let's say in internet banking  applications you want to send a money to some   other person so you need to provide enter you need  to enter some amount right so that amount should   be uh limited per day let's say you can send  home between 20 uh minimum 10 000 maximum 50 000   so you cannot send more than 50 000 so  starting like 10 000 minimum amount maximum   amount 50 000 you can send per day okay so  how we can test how we can test that field   uh we can test this by applying the uh testing  techniques okay boundary value analysis   okay okay so how we will test it by  using bba boundary value analysis   yeah we will check with uh we will check  with the minimum um that is the 10 000 and   and 10 000 minus one okay we will check and  ten thousand plus one we will be checking   for these three data's for the minimum and when it  comes to the maximum again we will check with the   maximum that is a fifty thousand and uh we will  check for the fifty thousand minus 1 um and 50   000 plus one okay great so we have to check six  parameters that will cover all the boundaries   okay yeah now let me let me just give one scenario  let's say i have file upload scenario so i need   to upload a file in my application i need to  upload a file and that's basically an image   file okay so that is accepting only dot png file  and the size the maximum size of the file is 1 mb   so i should upload only 1 mb size maximum size  is 1 mb and that should be dot png extension so   it should not allow any other extension or it  should not allow if the size is exceeded 1 mb   so can you just give me one positive test  case and one negative test case for this do you know what is positive test and  negative test case positive testing   negative test case or testing okay so first let  me okay first tell me what is positive testing   uh testing a software by passing the valid input  according to the customer requirement right great   yeah so that is positive and negative is passing  the invalid uh inputs okay which is not according   to the customer requirement great great so now  just tell me one positive test case and negative   test case for file upload so my requirement is the  file share should be maximum one name it should   not exceed one end and always file extension  should be dot png it should not accept any other   extension of the files now tell me one positive  test case and one negative test case for that   uh we verify that uh the image should be should  be in the format of the dot png so that is the   that is the positive okay and negative is uh  we are uh to check to check that um the size   of the image is greater than 1 mb okay so that  is negative testing similarly we can also check   size wise we can size ways and also we can also  check the extension right if you upload file with   less than one number 1 mb size it should be  uploaded successfully if you upload the file   greater than one mb it should not be uploaded  so one is negative one is positive similarly   the extension right if you upload the file  with dot png it should be uploaded without   dot png should not be uploaded so that is one  positive destination one negative test case okay   so that's all about manual testing so can ask  some questions from java i think you also put   skill on java i'll ask some basic questions okay  and uh yeah so you already mentioned your profile   you know some concepts about object  oriented programming concepts so   can you just let me know what are the  oops concepts are supported by java yes sir method over overloading overriding  abstraction polymorphism encapsulation   okay and uh what else what about the class  object yeah class class yeah the basic entity   itself is a class right if you have a class  then rest of the concepts will be there other   than class there is not there nothing is  possible so the first one class object then   polymorphism encapsulation inheritance so these  are data abstractions so these are all different   object oriented programming concepts okay so  can you just tell me the differences between   method overloading and overriding overloading  and overriding uh in the method of overloading um it should have in the method overloading  uh the parameters should be of the um   so just tell me first of all what is  overloading what is method overloading in the method overloading with this uh the method name will be same uh in the and we  are changing the the number of parameters can be   varying great and in this method overriding  we are changing the implementation of the   method itself okay great so let me just clarify  this so basically method overloading means   suppose when you create a class in java so we  can write multiple methods with the same name   right with this if i use same name for multiple  method that's basically called method overload   but here what are the rules we need to  follow while writing the while overloading   the methods the number of parameters should be  different let's say if i create one method with   two parameters the same method with the two  parameters we cannot create again but if you   still created two parameters again we need to  change the data type or order of the parameters   so each and every method should have a different  definition it should not be a unique that's called   method overloading so when you come to overriding  so in method overrating is possible only with   inheritance at least we need to have a two classes  right that means whatever method we created in the   parent class the same method if you recreate again  in the chain class by changing the implementation   which is basically called as overriding right so  overloading is possible with single class also   but overheading is possible only with inheritance  at least we need to have two classes then   overriding is possible but in overloading we will  change the only parameters method name is only we   change the parameters but in overwriting we should  not change the definition the written type name   of the method number of parameter we should not  change we should change only the implementation   okay so these are the basic differences  between overloading and overriding   okay great okay what is the use of a super keyword  [Music] when do you use super keyword in java have you used it okay no problem actually  basically super keyword will be used along   with the inheritance suppose in the  parent class you created one method   and in the chain class you overrided that method  okay now when you create an object of the jail   class when you call that method only change class  method will be called because there's a latest   method you have implemented but still if you  want to invoke the immediate parent class method   yeah right so then we will use a super cube like  we can invoke the immediate parent class variable   immediate parent class method or immediate parent  class constructor we use super keyword okay which   we basically use along with the inheritance  concept okay so what is an abstract method in java what is an abstract method in java the method which doesn't have the uh complaint  complete implementation so that method is called   as abstract right so the method doesn't have  any implementation just only which you have   only definition which is called as abstract method  so where you can create abstract methods in java where you can create normal class can can i can  i create abstract methods in the normal class   no so where we can create  yes interfaces we can attack   we can create abstract class and where  else what else where else we can create abstract class right so we have an  abstract class right before interfacing   in abstract class method contains abstract  methods so even interface also we can create   an abstract methods and those methods we will  implement later by using some other class okay   so in interface implementation is not possible  so we need to create another class and then we   will implement those abstract methods great so  any idea about collections java collections do   you know anything any collections like arraylist  hashmap okay no problem leave it okay so let me   ask a few questions from sql so do you know sql  so how much rating you can give on sql one to ten five okay fine so let me just ask a few queries  because you mentioned like uh you have knowledge   on sub queries and joins and you know some basic  dml ddl commands a simple query i'm going to ask   let's say i have a product table okay if you have  a paper and pen you can just write it down or if   you have a notepad still you can write it down no  problem it's a simple query i'm going to show you   simple a product table which contains only  two columns okay and uh product a name or the   other column is a price product and price only  two columns one column is having product name   and the other column is called product price so  there are different products so some products are   having same price right some products are having  higher price some products having a low price   so i want to display the data from this table  like uh expensive products like whichever the   product is very expensive i want to display  the data of that particular product let's say   you have 10 items in your table each item each  item is having some price let's say one item is   100 rupees other item is 200 rupees or 500  rupees or 1000 now i want to display the   item which is having highest price or which is  very expensive single table only two columns select okay the product price okay from the table name is uh products you can  just consider as products product details   or products table which contains only product  names yeah price yes after display with the name   and uh the price right and just display the name  of the product name along with the price yeah just i want to get most expensive  product or high value product   and the product which is having high price and you  compare with the rest of the products okay then uh   select the product name uh from the products table  okay uh where max or max of the product price max function how to use this max function   can we write uh can you achieve this with single  query or do we need any sub query for that we need we need sub query yeah we need sub query  right so how we can use it so select select select the product right max of the product  price from the products table okay that will   be the subject here that will give you the maximum  price so if i say select max of max or price from   product table that will give you maximum price  but what is my requirement here i want to just   display the details of the product not only max  that will be yes so that we will get the maximum   price and that is the sub query and that's  a sub query will be you put into others uh   the main sub query main query that is the select  your product name from the product this sub query   so the final query will be select star or if you  want to capture all the columns we can simply say   select star from products where price equal to  in the sub query we can simply say select max of   price from the products table so first we need to  know what is the maximum price right what is the   highest price in the table and once you get it  we will use that maximum price and then get the   details of the product and whichever product is  having that price we will get it so select max   price from the product table is a sub query and  the output from that query will be the input of   the outer query so in outer query we will just  specify the select star from products table or   select the product name or price from products  table so we can achieve this by using subquery   right okay so can i ask one more question so it's  simple having customers table like customer id   there's a customer name and uh customers are  belongs to different countries like one customer   is belongs to uk us or any other countries now i  want to face the data from this table like each   country how many customers are there so let's say  i have a table in which there are five different   customers are from u.s country right so now now  i want to find out from u.s how many customers   are there from uk how many customers are there  from germany how many customers that means each   and every like country-wise i want to find out  total number of customers from the customers table   again single table just to have a few columns  like customer id customer name and country or   you can just take customer name  and country only two columns if you want you can just write down  your paper just have customer names   other column is a customer countries countries  yeah so you can have some duplicate country also   us is repeated two three times uk is repeated  two three times now from the u.s country how   many customers are there from uk country how many  customers are there that means each and every   country how many customers are there in the table  i need to find out so how we can write the query uh select this country home account equals [Music] we have to display for all the  countries also yes yes [Music] each country how many customers are how many  customers are there in each and every country i'm not getting the sub query server so you  you don't need to use subquery actually here   so single table so you don't need to use any  subquery still you can get it just can you try so let me also give a clue so here basically we  need to group the result yep so first of all we   need to group it so all the countries right  country wise count we need so country-wise   we need to use group yes yeah we have to use  the count select country count equals to um so country wise results we need to group i'm not getting the property okay no problem so  here uh we have a different countries i said right   each country how many customers are there how many  customers how we will find out by using count star   count star will give how many so each country  how many customers are there each country means   whenever you say each country means group  by will come so group by country we need to   use so the final query will be select count star  comma country from customers group by country so   country wise we grouped and each and every country  how many customers are there count star will give   you the counter okay so here we no need to write  the sub query so we can simply rise group by class   and count star and we can get it okay so that  is a simple query and do you know about joins   one last question so when do you use joins  when there are two different tables okay   multiple tables yes not only two even if you have  one table we can write a self-adjoint right so   we can create an aliases of the table and we can  create so joints will be used if you want to get   the data from one or multiple tables if you want  to join the tables we can go with the choice okay   so that's all from my site so whatever you  know you answered perfectly fine and from   manual testing you answered everything almost java  and sql java you need to prepare well so mostly   i have not asked any practical questions from java  but you need to prepare for practical questions   like program oriented questions and theoretical  questions are fine so you answered well whatever   you know you answered well only thing is  practical questions you need to prepare from sql   uh also you need to prepare uh queries  okay so theoretical questions are fine but   you need to prepare some more queries okay  that's all from my side all right so thanks   for attending the interview so prepare well  and if possible again i'll take one more mock   interview in future okay if you are prepared well  thank you thank you very much thank you thank you