Jan 23, 2010
Do definitions of Testing or testing skills, which one bring out more bugs?
Frndz, one of my hilarious conversations with an interviewer.
Interviewer: What is Regression Testing?
Me: I have got a bug in one screen and reported to the developer. After fixing it, he asks over me to test it just the once again whether that bug is fixed or not.
If I test the application where I got the bug is Re- Testing.
If I test all the applications to check whether the changed code affected anywhere is Regression Testing.
Interviewer: No, am not getting you exactly.
Me: haaaaaaaaaaaaa???????????????? :-)
Interviewer: Can you give the exact definitions of Regression and Re-Testing with some real time scenarios?
Me: That is what I have done.
Okay I will explain you one scenario.I was testing a login screen. In the login screen, I do have “Forgot Password” option. And I also have “Change Password” option in the settings screen. For both the options, it should send a mail to email id which we configure in the admin settings.
While I was testing “Forgot Password” it was not sending the mail. Whereas it was fine with “Change Password”. I reported this bug to developer. After fixing this bug he asked to test it.
If I test only for “Forgot Password”, where I got the bug is RE-TESTING.
If I test it for both “Forgot Password” and “Change Password” to check whether both the options sending the mail to same email id is REGRESSION TESTING.
Interviewer: Common man, I was asking you to say the exact definitions and you were saying the examples. Why you are wasting my valuable time, I need to take more interviews……….
Sudhamshu lost his patience, no way my fnrdz. How these guys are eligible to take the interviews.
It went on like this with a lot of stupid questions and stupid explanations. I was puzzled, what he wants exactly from me. Does he wants’ me to test or wants’ me to go and join a Software Institute to learn the exact definition for all the Testing terminologies.
Hammaya :-( , at last he asked one brilliant question, “Do you want anything to ask me?”
Then I asked him, “Do definitions of Testing or Testing Skills, which one bring out more bugs?”
Interviewer: What a funny question, obv Testing Skills.
Me: My dear friend Learn and practice them, they makes you to write your own definitions of the skills you know.
Really Frndz some of my interviewers will depend on Google and the classes they went out to learn testing. If we answer wrongly from what they learnt, no way you are not selected.
Frndz, if you come across such type of Interviewers please educate them. They are our beloved TESTERS and they belong to our own community.
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
Jan 20, 2010
Why security, usability and performance testing has to be done?
Hi Frndz,
Lemme share my ideas of about Security, Performance and Usability.
Security testing
Is a process to determine that an information system protects data and maintains functionality as intended.
The six basic security concepts that need to be covered by security testing are: confidentiality, integrity, authentication, authorization, availability and non-repudiation.
Performance Testing
In the computer industry, software performance testing is used to determine the speed or effectiveness of a computer, network, software program or device. This process can involve quantitative tests done in a lab, such as measuring the response time or the number of MIPS (millions of instructions per second) at which a system functions. Qualitative attributes such as reliability, scalability and interoperability may also be evaluated. Performance testing is often done in conjunction with stress testing.
Usability testing
Is a technique used to evaluate a product by testing it on users. This can be seen as an irreplaceable usability practice, since it gives direct input on how real users use the system.This is in contrast with usability inspection methods where experts use different methods to evaluate a user interface without involving users.
I was into testing a web product, which deals with the sales as like ebay and amazon.
As per our FRS (Functional Requirement Specifications) and BRS (Business Requirement Specifications), satisfied with the quality of the product from client side and released into the market.
Then the actual bugs came up.
Some points of the FRS:
1. When a user logs in and selects the categories to buy, let us think he wants to buy teddy bears, he has to select that category.
2. Will get different types of the selected category, in the second page.
3. After selecting a teddy bear if he wants to buy it, he has to click on Buy button.
4. This navigates to the third page.
5. Will get a list of options like DD, Credit Card and Debit Card.
6. After selecting, it has to show the available banks in the list.
7. Enter bank id and password to buy the product.
8. Have to get a confirmation mail from the web.
Some, only some steps to check. If these points are not bringing up in FRS or BRS, request client to act in response for these issues.
1. How much time it is taking to navigate from one page to another page in the process to buy a product?
2. If it is taking 10 seconds to navigate from one page to another page, it is okay. But if it takes more than 30 seconds, does it encourage user to visit this page again.
3. How much it is secured to give the bank account details?
Frndz I will deliver some more info regarding the same concepts. Lemme work more on this product and rear to you ASAP.
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
Lemme share my ideas of about Security, Performance and Usability.
Security testing
Is a process to determine that an information system protects data and maintains functionality as intended.
The six basic security concepts that need to be covered by security testing are: confidentiality, integrity, authentication, authorization, availability and non-repudiation.
Performance Testing
In the computer industry, software performance testing is used to determine the speed or effectiveness of a computer, network, software program or device. This process can involve quantitative tests done in a lab, such as measuring the response time or the number of MIPS (millions of instructions per second) at which a system functions. Qualitative attributes such as reliability, scalability and interoperability may also be evaluated. Performance testing is often done in conjunction with stress testing.
Usability testing
Is a technique used to evaluate a product by testing it on users. This can be seen as an irreplaceable usability practice, since it gives direct input on how real users use the system.This is in contrast with usability inspection methods where experts use different methods to evaluate a user interface without involving users.
I was into testing a web product, which deals with the sales as like ebay and amazon.
As per our FRS (Functional Requirement Specifications) and BRS (Business Requirement Specifications), satisfied with the quality of the product from client side and released into the market.
Then the actual bugs came up.
Some points of the FRS:
1. When a user logs in and selects the categories to buy, let us think he wants to buy teddy bears, he has to select that category.
2. Will get different types of the selected category, in the second page.
3. After selecting a teddy bear if he wants to buy it, he has to click on Buy button.
4. This navigates to the third page.
5. Will get a list of options like DD, Credit Card and Debit Card.
6. After selecting, it has to show the available banks in the list.
7. Enter bank id and password to buy the product.
8. Have to get a confirmation mail from the web.
Some, only some steps to check. If these points are not bringing up in FRS or BRS, request client to act in response for these issues.
1. How much time it is taking to navigate from one page to another page in the process to buy a product?
2. If it is taking 10 seconds to navigate from one page to another page, it is okay. But if it takes more than 30 seconds, does it encourage user to visit this page again.
3. How much it is secured to give the bank account details?
Frndz I will deliver some more info regarding the same concepts. Lemme work more on this product and rear to you ASAP.
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
Jan 14, 2010
Ask for the brinjals in the bars.........(How important is the domain knowledge and technical knowledge)
Hi Guys,
Hope you are doing great and wonderful testing these days.
Ask for the brinjals in the bars......
Will you ask for the stationary in the banks?
- Or-
Will you ask for a America ticket in the city bus?
If you so, then don't scroll down.
Leave it frndz. We are genius by birth :-)
So we don't ask like that. We know that, we get stationary in super market and we should stair a plane to land into America.
Why am mentioning all this futile stuff in this post? Why am wasting your precious time?
Because, I just need to declare that how important is the knowledge we have of about a software/produce, which we are going to test.
Lemme share my familiarity here:
After carrying out my PG, I joined a testing institute. After finishing classes there, I attend the interviews and joined a company.
When I was asked to write the test cases for the CRS, I wrote them.
Sorry, I forgot to say of what the domain I was working on. It is an ERP product which was developed for Staffing and Recruiting. When I was theoretical to write the TCs, I even don't know of about the words "Staffing" and "Recruiting". But I wrote and not bad, I got some major bugs too.
When I left that company, when the product is went out for the first release, I was master in the terms of Sales & Recruiting.
My intention is not to articulate that we should be the masters in all the domains and all the technologies. But shouldn't we have a basic knowledge?
If we don't know what we are doing then how we can say that we have done?
To do the best, we should be good @ what we are doing.
Please frndz let us have the basic knowledge of what the domain and what the environment we are working on. When you attend an interview or when you apply for a job, collect the information and prepare accordingly.
I will furnish the info of about how to get the basic knowledge before testing sumtng in my further posts.
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
Hope you are doing great and wonderful testing these days.
Ask for the brinjals in the bars......
Will you ask for the stationary in the banks?
- Or-
Will you ask for a America ticket in the city bus?
If you so, then don't scroll down.
Leave it frndz. We are genius by birth :-)
So we don't ask like that. We know that, we get stationary in super market and we should stair a plane to land into America.
Why am mentioning all this futile stuff in this post? Why am wasting your precious time?
Because, I just need to declare that how important is the knowledge we have of about a software/produce, which we are going to test.
Lemme share my familiarity here:
After carrying out my PG, I joined a testing institute. After finishing classes there, I attend the interviews and joined a company.
When I was asked to write the test cases for the CRS, I wrote them.
Sorry, I forgot to say of what the domain I was working on. It is an ERP product which was developed for Staffing and Recruiting. When I was theoretical to write the TCs, I even don't know of about the words "Staffing" and "Recruiting". But I wrote and not bad, I got some major bugs too.
When I left that company, when the product is went out for the first release, I was master in the terms of Sales & Recruiting.
My intention is not to articulate that we should be the masters in all the domains and all the technologies. But shouldn't we have a basic knowledge?
If we don't know what we are doing then how we can say that we have done?
To do the best, we should be good @ what we are doing.
Please frndz let us have the basic knowledge of what the domain and what the environment we are working on. When you attend an interview or when you apply for a job, collect the information and prepare accordingly.
I will furnish the info of about how to get the basic knowledge before testing sumtng in my further posts.
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
Jan 12, 2010
Start acting, don't bother about Outcome.
While I was goggling for some notes on testing, I came over this article. Which made me to read again and again.
Am pasting it here for you to read once.
This is a story about a famous research scientist who had made several very important medical breakthroughs. He was being interviewed by a newspaper reporter who asked him why he thought he was able to be so much more creative than the average person. What set him so far apart from others?
He responded that, in his opinion, it all came from an experience with his mother that occurred when he was about two years old. He had been trying to remove a bottle of milk from the refrigerator when he lost his grip on the slippery bottle and it fell, spilling its contents all over the kitchen floor—a veritable sea of milk!
When his mother came into the kitchen, instead of yelling at him, giving him a lecture, or punishing him, she said, "Robert, what a great and wonderful mess you have made! I have rarely seen such a huge puddle of milk. Well, the damage has already been done. Would you like to get down and play in the milk for a few minutes before we clean it up?"
Indeed, he did. After a few minutes, his mother said, "You know, Robert, whenever you make a mess like this, eventually you have to clean it up and restore everything to its proper order. So, how would you like to do that? We could use a sponge, a towel, or a mop. Which do you prefer?" He chose the sponge and together they cleaned up the spilled milk.
His mother then said, "You know, what we have here is a failed experiment in how to effectively carry a big milk bottle with two tiny hands. Let's go out in the back yard and fill the bottle with water and see if you can discover a way to carry it without dropping it." The little boy learned that if he grasped the bottle at the top near the lip with both hands, he could carry it without dropping it. What a wonderful lesson!
This renowned scientist then remarked that it was at that moment that he knew he didn't need to be afraid to make mistakes. Instead, he learned that mistakes were just opportunities for learning something new, which is, after all, what scientific experiments are all about. Even if the experiment "doesn't work," we usually learn something valuable from it.
Picked it from: http://www.itpepper.com/default.aspx
Wow frndz, really it is a great experience right? Let us thank the guy who has brought it to us.
Can't we think out of the region while testing a software, if we do so can't we get more results(bugs)?
As I had read that "Lateral Thinking" will surely make us to think in a better and wide range. Let us read some books or do some puzzles on Lateral Thinking.
Start Testing, don't bother about Outcome. Even if it is a worst trial, you can learn from it. Experiment will only make us to do more experiments. Leave of about Positives and Negatives.
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
Jan 11, 2010
Apple's for sale
Apple's for sale - Wrong
Apples for sale - Correct.
A small punctuation can make a lot of difference (Really).
I have spent most of the day putting in a comma and the rest of the day taking it out.
- Oscar Wilde
Why am posting of about Punctuation, how it is related to testing a software.
Cool guys’ lemme give you the brief ideas of some terminologies in testing.
What is Regression Testing and Retesting?
Let us think that we do have some problem with date in one application. For example, if we enter the date as 12/01/09(DD/MM/YY), but the application is treating it is MM/DD/YY, then
what about 25/12/09?
How the system responds?
Testing the application once after a developer fix the issue in the application where we have raised the bug is Re Testing.
Testing all the applications Parallely to check whether the fixed bug, have created new errors or unexpected behaviour is Regression Testing.
Correct me if am wrong. :-)
Back to punctuation.
An unintentional slip of a key that replaces a full stop with a comma might not be detected for weeks but could have serious effects.
Why Regression tools are used to automate software? Let us discuss it in the further posts.
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
Apples for sale - Correct.
A small punctuation can make a lot of difference (Really).
I have spent most of the day putting in a comma and the rest of the day taking it out.
- Oscar Wilde
Why am posting of about Punctuation, how it is related to testing a software.
Cool guys’ lemme give you the brief ideas of some terminologies in testing.
What is Regression Testing and Retesting?
Let us think that we do have some problem with date in one application. For example, if we enter the date as 12/01/09(DD/MM/YY), but the application is treating it is MM/DD/YY, then
what about 25/12/09?
How the system responds?
Testing the application once after a developer fix the issue in the application where we have raised the bug is Re Testing.
Testing all the applications Parallely to check whether the fixed bug, have created new errors or unexpected behaviour is Regression Testing.
Correct me if am wrong. :-)
Back to punctuation.
An unintentional slip of a key that replaces a full stop with a comma might not be detected for weeks but could have serious effects.
Why Regression tools are used to automate software? Let us discuss it in the further posts.
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
Jan 8, 2010
Conversation learnt me "What is Testing exactly".
Hi Frndz,Recently I had a intresting and important conversation with Pradeep, which helped me and educated me.
For your need am posting over here.
Me: I just came to know that for some of my clients the system get hang, I was trying to execute the same case but am unable to do it, Pradeep,Even I tried with diff OS,Versions of IE
the same configuration as like my client
Pradeep: hold on
Pradeep: Read this
http://www.satisfice.com/blog/archives/34, read it slow and experiment with the ideas in it.
Me: fine pradeep I will read it and I will surely try to find the bug
Pradeep: Have you heard about testability and supportability?
Me: no
Pradeep: Have you read a testing book? Not the ISTQB or CSTE stuff
Me: yeah, am following ur blog and some other blogs
Pradeep: blog is different from book, have you read a testing book completely?
Me: no I haven't read
Pradeep: Let me ask you this question: Do you think the programmer with whom you work has never read a book on programming?
Me: they have learnt
Pradeep: Well then if you were to suffer in future, please dont blame it on software testing but yourself. However, the good news for you is.
Your problem is solvable. Go read
Testing Computer Software, 2nd Edition
and
Lessons Learned in Software Testing
then read blogs
Me: yeah Pradeep, I will buy and read the book
Pradeep: thanks,If you do that you will be doing the biggest thing to yourself as a tester.
Me: I should thank u Pradeep
Pradeep: dont thank me, I havent done any help to you yet
Me: fine
Really I were in to testing field from 2 years but I haven't read a single book on this.
Shame on u Sudhamshu.....
I started to read a book now, mostly am going to complete it.
www.nickjenkins.net/prose/testingPrimer.pdf (Worth reading it)
So frndz, start reading the books, if you haven't yet.
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com/
Jan 6, 2010
A small Ant(Versatile Tester)
Frndz, first lemme wish u a very Happy and Prosperous New Year. I wish you lots of luck and bright future this year.
A small Ant (Versatile Tester)
Recently, I come across a situation, which made up my mind to think in different scenarios to prevail over a situation.
One fine day, I saw an ant. This is frustrating to escape from water (heavy pour) under a tap. I thought of serving it. I have taken a leaf and helped her to come out of water. But again it went to a place where a small drop of water was bounded. This time, I was not supposed to help her. Sat there and seen the ant, how it come out of it.
Really, I was never seen such a situation with lot of persistence. It was moving only to a side again and again (more than hundreds of times). After a lot of time, it was moving to all the other three sides. Common Frndz, I again thought to help it with the leaf. But I observed it again and again with much more patience.
After moving here and there, it waited in the middle for a while. Then I puzzled of what it was doing about. Then the puzzle is solved, it came out from that place.
Frndz it waited for water to get evaporated.
Lemme apply it to real life.
As a tester, lot of my teammates and my managers helped me out with leaves to overcome some situations in initial days of my career. But will they be with me every time?
No, so how should I do things soft and beneficially? As according to my knowledge, when you find a new scenario or situation which you haven’t tested yet, think for a while, do some homework and practice with some test scenarios. Even if you are not able to test it (Surely you will get the test cases), then go for the help.
Frndz, try until you can, if a small ant can test in different ways to come out of the water, why can’t we?
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
A small Ant (Versatile Tester)
Recently, I come across a situation, which made up my mind to think in different scenarios to prevail over a situation.
One fine day, I saw an ant. This is frustrating to escape from water (heavy pour) under a tap. I thought of serving it. I have taken a leaf and helped her to come out of water. But again it went to a place where a small drop of water was bounded. This time, I was not supposed to help her. Sat there and seen the ant, how it come out of it.
Really, I was never seen such a situation with lot of persistence. It was moving only to a side again and again (more than hundreds of times). After a lot of time, it was moving to all the other three sides. Common Frndz, I again thought to help it with the leaf. But I observed it again and again with much more patience.
After moving here and there, it waited in the middle for a while. Then I puzzled of what it was doing about. Then the puzzle is solved, it came out from that place.
Frndz it waited for water to get evaporated.
Lemme apply it to real life.
As a tester, lot of my teammates and my managers helped me out with leaves to overcome some situations in initial days of my career. But will they be with me every time?
No, so how should I do things soft and beneficially? As according to my knowledge, when you find a new scenario or situation which you haven’t tested yet, think for a while, do some homework and practice with some test scenarios. Even if you are not able to test it (Surely you will get the test cases), then go for the help.
Frndz, try until you can, if a small ant can test in different ways to come out of the water, why can’t we?
Happy Testing
Sudhamshu Ailineni.
sudhamshu.rao@gmail.com
http://sudhamshu-softwaretestingnotes.blogspot.com
Subscribe to:
Posts (Atom)
