A freshers approach on search of jobs

Few years/ month back I was in search of job. After completion of my graduation, I normally used to apply for many companies for many roles. I haven’t known which sort of jobs will suit me (my interest). Lots of struggle to get into IT concern. Later on I realized my faults, known my interest and worked on that. I settled in a job (my favorite).  And today I am in one concern working as a Software Tester and some other roles too.  In case of job search same situation is happening even now among the fresher’s. The problem what I have faced is almost same when I see some people who apply for the job in my concern. I have interviewed two kinds of candidates, people applying for testing job and who have no idea about choosing the job.

Most of the fresher who complete their graduation will gain the knowledge in some X technologies but haven’t developed their skills. I believe skills are what the industry expert from the candidate than having just knowledge alone. So, I suggest a fresher’s (College passed out) to develop their skills along with the knowledge.  

I see some people coming for an interview with no idea about the position they have applied for. I am the person who believes more on the interest than the knowledge they have. So, before checking their knowledge, I just look into their interest. On questioning about their interest, few says that yes I have an interest.But when I asked about the measurement they have taken for that, they say sorry I didn't do anything. Few say I got this interest last month before that my interest was different. So, for those people I just stop going further and give them time to know/ think about their interest and if they are clear with that I would ask them to apply again.

 When I have interviewed few people they just come with the blank idea saying that they want to work in a software job. But don’t know what they are really looking in the software job. Few thinks that software job is all about coding and testing .They don’t consider even web designing as a part of it. It is not the responsibility of an interview to educate about the varieties of jobs in the software company. It is the responsibility of the candidate. Sometimes it is the responsibility of her/his staff in college.  Teacher must be much dedicated and should help his/her student in choosing the career when they are helpless. Sometimes I feel it is the responsibility of the teacher to create awareness about the happenings in the IT industry.

Here is another case I was speaking with one person who appeared for an interview after completion of interview process .I made a formal chat with that person. He is interested in web designing but want to get into programming because his dad wants him to get into programming. But he is not interested in that. To those people he/she should convince his/her parents and let them know their child’s interest. Some parents/student believes that programming is the top level in the IT job and one could have a fastest growth and best salary if they are into programming.

Some people learn their engineering subject in just sake of clearing the semester exams and some will have good knowledge on particular subject’s .But as far as the industry concerns it is not enough.  I don’t blame all the students’ way of learning their subjects. Some will develop skills along with the knowledge. Kudos to those people.

Because of demand on job search few do some certification believing that it would help us in getting a job. There are some institutes who provide a service just for their business sake and there are some companies who don’t even consider the course certificate. So be aware of that. Course certification is like an eye/brain wash it will not always help you in fetching the job .Unless you realize your interest and develop your skills it is tough for you to get into the job.

Nowadays the degree certification has become a gate pass for applying for the job. With the help of such certificate alone without skills there is no use in having such degree certificate. No matter what the value that degree certificate holds or the grades you got.

So, learn engineering in such a way that you could develop the skills along with the knowledge.  Know/Develop your interest work on that. Reach your dream. Make it true and enjoy your life.

All the Best!!!

If I am wrong in my approach/ opinion, Please send me your feedback.  Feedback sometimes acts as a sign for “Caring”
                                                                              - Pradeep Lingan

Caring is a kind of quality a testers must have in his/her work

I normally used to test when I use some product. Sometimes I see BUGs that are dancing in front of my eyes. What should I do when I see such bugs in those products?. I am not working on such product company. Should I leave that? No.  Being a tester I will not leave that. I used to make a bug report and send it to the concerned person.  Because it’s not just to say that I care for the product (any). But I love my job. I personally feel caring is a kind of quality a testers must have in his/her work. This could also be a way of representing that I care for the quality of the product and the job I do. Some of the BUGS/Suggestions that I seen in some apps are listed below. I used to report it to those concerned person and then I used to update it in the social media.


How some one could update something into my profile. How will I ( any user) feel it as a secured

The message that wish me saying that I finished this section successfully though I got an error in the output.

This I made it purposely. I just changed the line of the code to see how it respond for that change. 

 I was asked to enter a password after successful completion of log-in to my account

 I didn't send any request or made some changes in it. But, I don't why it is asking me to log out and sign in. 

Bug reporting is one of the important skill a tester should have. But here it is shown as a duplicate skill.

Wrong content is entered 

Having a forgot password option in user profile setting page makes no sense.

Google in Tamil : Looking for Tamil words but I see both English and Tamil

My new style of designing the test case

I just want to make (follow) some new style of working in testing. I just started and trying to do a research in creating (test case design) and following the testing style.

I have gone through few test case document creations. But I am entirely against to it. Because my testing approach (Exploratory-learn and test) is quite against to following test cases for testing. I have done some work to have a new style of designing the test document that contains two or three columns if it is documented in excel. The columns are “Questions/Check”  “Results got”  “Comments/Notes”. I don’t prefer to have a lengthy column sections for the test case design like “Test strategies Test scenarios, , Test Steps, Expected Results, Actual Results, Status. I haven’t followed any test case document. But, I just want to know how well it works with my new approach.

I have learned and believe that testing is about questioning the product. So, we test by questioning to ourselves over the product. I believe “Product quality goes blind and deaf is the tester doesn't knows how to see and speak with the product”.

So, as a tester we need to know how to communicate with the product. How well you communicate with the product and that much the quality that product will have. 

My new design has few features

Module name will help us to know which module/Unit we are working with .This will help us to know about the trace-ability matrix. Followed by test designer name and people who executed the test cases and along with that time required to execute the test.

I see this will be the simple way to have a test case document preparation.

This could be created in other kind of document like Mind mapping. Mind mapping is another way of representing the document in picture form. There could be any (many) style of having a document through mind mapping

If the test case is prepared through other document file like word, excel:  (sample document):

Test case Document Module Name:         Designed By:      Executed By:          Duration:
Sl.No	Questions/Check	Results found	Comment/Notes
1 2. 3.	Does the username field contain rectangle shape? Does the data’s in the password field are encrypted? Does the min/Max length of the password is X, Y?

This is the sample of my work not the result of my research work. All the changes I make in preparing the document will be updated in my blog post.  I will be happy if anyone provides me a feedback for my work and I will be happier if you try to create a new documentation style and test case following approach.

My Contact Information:

Email: ktg.pardeep@gmail.com

Phone: 07639959901

Skype: pradeep.lingan

Need of learning about the product before testing

When I was asked to test a product, I first learn about the product. Unless I understand  about the product, I don't start testing. If I have a short time for test, some how I will  manage my time for learning(quick learning) about the product. There is no use in testing a product by just clicking on few  links or buttons and saying "yeah, it's working fine" or running a passed test-cases again to make it pass.

 How I test a product? 

I am not a great expert in the testing domain. I just have 1+ year of work experience in the relevant field. But I have formed my own style of learning and working .When the product is ready for test I just make sure few things like

1. Learn about the product

2. Know the end users for that product

3. Choose what test to perform either Automation or Hands-on

The above  are the most important to be known to start testing.

When you know about the product you could make a check on product quality based on

1.Functionality

2.Logical and other testing activities

Logical thinking:

When you know about the product flow, only then you could work on logical part. Unless you learn completely about the product you can't provide a better solution for a logical problems. Even you find some logical issue, you can't confirm its a problem. Because you are not sure about the entire product concept. I have experienced such problem. When I tested for one product, I was confused whether to report this or not. Few things I made it in assumption(assuming that it is correct) which is not a good practice. I realized by fault then I promised my self for not repeating the same.

Raising a question is good but not good always. When I started my testing journey( during my training),  I was asked to test one e-commerce sites. Its a UK based product. Once I got that product I just started clicking on few links to check whether the links are working fine and made some other test also. I ordered one product entered an address for shipping, I entered Indian address,  but I got an error message. It never allowed me to order a product for such location. Because there was a zip-code it is a mandatory field and only a  valid zip-code are accepted .So when I entered a zip-code like "656788" I got an error message . I raised a  question like how the people in India could get this product. The person( lead) just laughed and asked me to go through(learn) about the product before you test, After going through I just came to know that the shipping is for that specific country only not for  other countries. If I have learned about the product before I started I haven't asked such unwanted questions. Questioning is good. It is a basic need a tester should have. But not always.The question should be raised when it is suppose to be raised. If I keep questioning without knowing anything  it will irritate other people.

How far BPO experience will help in testing work:

I was fired from my first company and I was looking for the next job. Searched for the job  but couldn't able to find. So, I  decided to find my job in BPO sector just for time being. So, I consulted my teacher(my guru) regarding joining in BPO. He encouraged my to join in BPO and asked my to work for the product support. He said this will help in your testing career. I was wondering how this experience will add a value to the testing work. He said you will come to know about customers issue on such product .This will help you to know what customer is actually looking for. So when you work as a tester this will help you a lot. But I didn't join in any BPO I got a job in one concern for a testing role.

I am working in a product based company. When I was testing a product in my current company I realized what my teacher told about the value of  BPO experience( in handling customers). I felt little difficult to analyse the customers expectation over this product.

Unless you learn about the product scope, you can't do a better testing. Compare the product with your competitors product and see what makes your product different from your competitors product. This will help you to give a better suggestion. Learn about the end users for that product. If it is a job portal and dedicated only for the engineering students and the professionals then you need not worry much about certain things like, if there is an option like settings it is shown up with symbol but no names. Here the user could understand easily what that symbol is meant for.Because most of the end users for this product will have good enough knowledge in using websites and some symbols.So there is no harm for them in playing with these products. So, they could easily understand few things and there is no need to educate much about the product features.

Suppose if the product contains different kind of users like shopkeeper, etc.. and some users will use the computer very rarely may not have much knowledge about web. So, in such case it is necessary to provide a name along with the symbol for setting options. Otherwise it is tough for few users to understand about the product features. We need to educate them in a better way. The products should be made based on the end users.

If the product contains small font size and light color. So in such case we need to consider few things like the user with low vision, good vision. A good vision user could some how manage to learn the content but in the case of low vision user it is quite hard. it will lead to an  accessibility issue

Message: The content either in error message or in any option if it is in high level English it is of no use. No more it  will add a value to the product just by providing the high level contents. So, the content that are shown could be understandable with normal English word and without spelling mistake. The sentence should not contain any grammar mistake.

Choosing which test to perform:

The most important one is what testing to perform either Hands-on or Automation. If it is an automation need to plan according to time constraints, other resources. If it is a  hands-on then how to test (with test case or without test cases). 

My Interview Experience and the Lessons I Learned from it

I have never attended any kind of interviews during my college days. The reason was due to rare opportunities, eligibility and scaredness. I was too scared to attend the interview. But I know without interview no one is going to provide me a job. I was looking for the job without interview or  with less competition. I hate interviews. After completion of my graduation, no way I have to go for the job. To do so I need to attend a interview. The journey started. I had a very good experience in attending interviews after the college days. In my first interview I was asked to speak for few minutes about myself,  but I couldn't able to express the thing that sparked in my mind. I was frustrated. I know my mistakes. But I had no idea of changing myself. It continued. I failed many times. Slowly attending interview had became as a day today activity to me. I haven't realized that. But, one day when I attended an interview in one BPO,  I was asked to speak for the topic they given to me. No scared, no struggle, whatever comes to my mind, I expressed through word of mouth. I felt I was so bold than others. I realized the changes. I go for an interview purposely to make myself ready to face the people without any scared, shyness, hesitation.

I failed in most(may be 50+) of the interviews. I had no confidence in me. I did some course(java, Testing). But I didn't get through. I got job in one BPO and that was my first job. Bad experience from the lead. I learned how a lead should not be? I know, I am not for that job. I quit that job and started searching for the other. Decided to search for the software job. I was a fresher( A new baby to the IT industry). So, not much idea about IT jobs. I thought only the programming is the top best job in the IT company. So, looking for that. But I don't have much programming skills. Learned without practicing. I couldn't do well(get through) due to lack of confidence in my answer. But some how I got into testing. Felt relaxed because I got a job.So,  no more interviews still I quit the job(searching for the other).

Few days gone, Things went out well. I was bit relaxed and enjoying too. But a sudden change  like a hump in the  long straight road. I was fired. Now, again I need to take my CV and have to walk for the interview. But this time I was not worried about attending the interview. I was worried about the job (role, company, and the lead). I attended some companies not much. I realized how poor some of the hiring people are.  I had a very bad experience with one hiring manager. He called me inside got my CV. Never read what I have written in my CV. He took one pen and started scribbling at  last page of my CV. His questions are
1.Tell about your self as normally every one ask. I replied with smiling face
2.Then asked about my family background. I replied
3.Then what language you know. I said I practiced manual testing. I have not practiced any script. But it is not a great challenge to me. I could learn it when there is a need for that.

 He said, Do you think Manual testing has a scope in the future. How long you could be in manual testing. I don't know you will be a fit for the IT industry. I know some thing in testing.So,  improve yourself else it will be a  tough for you to be in the industry. He suggested me to go through the book written by his boss.
I replied I don't wish to work with the people like you. You have never gone through my CV and how you know about me(about my stuff).I thought you will ask about my project but you didn't do that. I don't want to spoil my career by working with you.  I am ready to take up any challenge.  Said Good Bye. You might think they are looking for automation tester. But the interview was for the manual testing.

Another experience was that I was interviewed by two person. For some question I don't know the answer.So, struggled. but those two people who are near to my age started laughing at me, started kidding by asking the questions. Very bad incident I experienced. But I wish to meet them again.

I see most of the people who interview others feels, that the candidate has less knowledge than him/her. When some question are asked and the answer given to him/her is not relevant, then its a wrong answer for them. I have the habit of giving my own definition for the concept I know. I don't prefer to give the answer written by others( not all). I just go through few peoples explanation on some topics but never try to by-heart those sentences. I answer what I know( from what I worked with). I know that there are "N" number of definition for the question what is testing? But all the answer could not be compromised by all.  I love to question them for the question which I never answered and do homework too.
The difference I see in my interview before and after the job.
Before getting into any job
1. I was scared
2. Trusted interviewers answers
3. Felt he/she knows everything that's why they are interviewing me
4. I felt they are the  great people during the time of interview.
5. Believed on every thing that are published in the blogs, book or in any websites.
After getting into job:
1. No scaredness
2. Know what to ask when needed
3. Know how to answer
4. Learned how to refer a book
5. Seeing them(interviewer) as a normal person ( a staff in that office).

The value of Communication skills for a tester

When we speak about the skills we normally mention the tools that we are exposed to, the language we know and practiced. But most of us don't mention about the speaking and writing as a skill( especially in resume). Most of us mention such thing under the category language we know.

Did a communication matters a lot for being a software tester? 

It depends on the organization( Sorry, people in that organization). But to me, I would say "yes". We may be good in testing the product. But,  if we don't know how to communicate(right way of telling) the problems that are found in that product, then there arise a problem. The stuff of that person (not only the tester anybody in any domain) may not be exposed to others. You may be a king of king in testing(finding the defect) a product, when there is no proper communication between the people or if you don't know how to communicate with the team, you will be cornered. It is like having the Luxurious phone with no charge in the battery. Unless you charge your phone you can't do anything with that phone. So, know the importance of communication and also learn how to communicate with the people. 

Communication doesn't mean just speaking through word of mouth even your writing is a kind of communicating. How far writing skills help the tester to be a good tester. The same as you convey through word of mouth. You may be good in testing, but if your writing is not that good, where one can't understand what you are coming to say about it, the problems arises. It is some what easy to make others understand by communicating  through word of mouth either through phone or by facing directly. But, in case of communicating through your writings it is not that easy. A real stuff is needed for that. Lot of practice( home work) should be done to have a better writing skills. When you are writing to others one could able to understand what  you are about to say and that person who read should not assume by himself.  

A tester is responsible for making(preparing) the bug report. So, if the report that you prepare should be able to explain about the history of the bugs clearly. If the report is not that clear then even the critical bugs could be left out sometimes  and the people who have left such things are not responsible for not considering that bugs. it is you (tester) because of your writing. The story is not that clear.You have not conveyed it clearly. So, they have left it. 

How I witnessed this  as a problem?

I had worked with the people who have a good communication( Speaking and Writing). But, at that time I never realized this as one of the important skills. When I worked at my client office, I was doing the work what they want me to do apart from that. I was learning things quickly( because I am  so passionate about it). But one day I was fired from that office. Surprised, confused, Shocked, really don't know what else to write..Smile..  I was in such situation after hearing this word "Today will be your last working day" .

I did my work and had done better. But how and what went wrong.? I questioned my self. I believe every problem has some solution. Then I realized that I had not communicated properly. I had tested the product and reported the problem through mail.But, I didn't communicated (apart from mail) well. Even in my mail that I have send,  I didn't explained my issues(story clearly). This made a gap between me and my manager. Then I decided I should not repeat the same mistake in the next company. May be with some new mistakes,  But not intentionally. Because I love mistakes as I believe I could learn more from it. Mistake is not a big problem, unless you fail to learn from it by repeating the same . 

This blogging is a kind of home work I do to improve my self and also conducting the meeting with my team often in my office is  to get rid of my  shyness and scaredness while facing the crowd. I believe I will be one of the best writer and speaker in the future.                                                                                   

My Contact Details:

Email: ktg.pardeep@gmail.com

Phone: 07639959901

Skype: pradeep.lingan

When to stop testing

When to stop testing ?

This is somewhat a complicated question but answerable. Every problems has some solution. Before stating to test a product one should be aware of the time given to test. Based on the time one should plan what to test and how to test. Covering the entire module in deeper(reaching every corner) is not an easy task but one could cover the entire module (the necessity features ) by using the testing techniques they prefer.

How to know whether the feature is a necessity or not? 

This could be possible only by knowing(having a good knowledge) about the product. So, having a good knowledge on the product leads to a better quality of the testing.

Testing is a never an  ending activity and  we can never assume or assure that 100 % testing has been done. Learning the product in a very short time, Preparing the test data, or test script, preparing the test report by covering the maximum modules will be a a great stuff of a tester and  it's a challenge too.

The real testing experience(stuff) matters a lot here, not the year of experience. I believe stuff(experience) is the ability of an individual not the experience letter that one holds.

We can minimize the risk of the testing by doing some "X" testing and covering some "N" modules.

Things to be focused before shipping the product to the client

1. Number of modules covered

2. Number of bugs found

3. Time to fix those bugs

4. Meeting the client requirements to some point.

5. Defect rates fall below the specified level.

Things to be focused while shipping the product to the client

1. The critical bugs  are fixed and tested again

2. The risk in the product is under acceptable limit.

Testing is never an ending process We can not test till all the defects are found and removed. It is not possible at all. At some point, we have to stop testing and ship the product to the client. So, one could stop testing after performing the above mentioned task within the available time, budget, etc.

My Contact Information:

E-mail:  ktg.pradeep@gmail.com

Phone: 07639959901

Skype:pradeep.lingan

Twitter: pradeep.lingan1