Archive for July 2013

Post of the Month : July 2013

Phew ... ! What a month on writing testing posts.

In this post, i will share you the posts of the month of July.


"Do good things for good reasons"

Friday, July 05, 2013

Sunday, July 07, 2013

Tuesday, July 09, 2013

Wednesday, July 10, 2013

Friday, July 12, 2013

Monday, July 15, 2013

Tuesday, July 16, 2013

Thursday, July 25, 2013
Software Testing Good Practices

(Image by: Russell Davies)




Posted in | Leave a comment Location: Mysore, Karnataka, India

Its your Life.... Let go forward in Life…

Life is full of challenges, interesting twists, love, passion, emotions, egos, adventures, comfort etc.

"7" is my memorable number in my life. Here are 7 things, that i have learnt from the past life.



PAST FAILURES
Everyone goes through tough times – Success and Failures comes in life. Never think that you are alone in your life and remember there is always something that we are behind to achieve in life.  Stop thinking about the past and start thinking on what you are doing right now and move forward. 

“Nobody can go back and start a new beginning, but anyone can start       today and        make a new ending” – Maria Robinson

STOP PROCRASTINATING
If you want to achieve what you want in your life, stop procrastinating and take control to change the situation with responsibility to move forward.

“Act as though, It is Impossible to fail” - Dorothea Brande

Be a Leader
Stop playing blame game on others. Stand up and take the leadership in doing in front of your colleagues to solve the problem. Don’t try to impress anyone by putting down someone else in front of all.

“The Purpose of Life is a Life of Purpose” - Robert Byrne



Be Systematic and Organized
We are passionate to learn and do the things to achieve in life, we need to be systematic and organized in keeping your learning’s and research notes as they are our hard work we spent our valuable time.

“Once you eliminate your number one problem, number two gets a promotion.” - Gerald M. Weinberg

Make a Plan
Learning is never ending. We need to plan our learning and manage with time to bring our dreams reality.

“If you know where you are going, then you don’t need a map in finding the route” - Lewis Carroll

Self-Managed Learning
Nothing changes if you’re comfortable with the present. Try to change your day activities, do the stuff and compare yourself every week, to what you were like earlier and see the difference.

“Your career is your own responsibility. Your employer is not your mother.” -Jurgen Appelo

Reflection
My mentors say, we need to express our thinking by talking to people, take time to read a lot, take notes on thoughts and share with others. Appreciations would come your way and people will respect you and will ask for your help.

"Happiness is only real when shared." - Christoper McCandless



I would continue to Blog more often to make me more motivated and learn from the mistakes.

"It’s not what you achieve, it’s what you overcome. That defines your career.” - Carlton Fisk 

Posted in | Leave a comment Location: Mysore, Karnataka, India

Software Testing Good Practices

The following are some good practices, I have learnt for doing testing.

Before you start the testing the product, Understand the product Architecture.
Understanding the architecture and working of the product, can help you see more error prone areas and can cover large amount of errors in less time.

The Error prone areas may mostly occurs on the interfaces between the different modules, as different programmers work on different modules in a product development.

See the potential misuses and verify how the software works with those issues.
If application is working perfectly as per it is intended, then don’t stop the testing.
Just like a detective solves a murder mystery and the testers has to find out the any ways of potential misuses and how the software works unexpectedly with those issues. 


Sherlock Holmes is Top Fiction Detective

Think like an End User, who has no idea of how to use the product, explore it (or) Think like a Hacker try to find out methods how can a hacker exploit the scenarios by manipulating the program. 
For all these case the response from the product should be intelligent than providing critical information.

Record every step clearly and in detail
While doing the testing, record each step clearly and in detail with environment (operating system, browser etc.). If any error you have found, take a screenshot of it to show as a proof.
This can help the programmers in reproducing the error again and fix it without wasting a lot of time.
This can also help the testers while doing retesting, after the fixing done by the programmers.

Tip to Testers:  Learn to write notes, which can help you improve your communication and testing skills.

Help the team from preventing recurring errors
While retesting, testers should make sure that no new problems are introduced. Help the team in providing correct scenarios where the error may prone to occur again. This can help programmers from further error prevention in future process of product.
Explaining about the occurrence of defect to the architects, programmers and managers may reduce the cost and time of testing the product.

If you think, this post helps...Please let me know any Feed backs or comments.

Cheers, Happy Testing … J

Date Timeline: 25th July, 2013

Posted in | Leave a comment Location: Mysore, Karnataka, India

Tests using (Design and Functional) Specifications (Part-2)

In the previous post: We have learnt about "Tests without Specifications (Part -1)".

If you have missed it: Click here.

Now, we will do in contrast "Tests using (Design and Functional) Specifications (Part-2)"



Read the Project Documentations:
There are different kinds of documents may be available: 
               Design Specifications
               Requirement Specifications
               Functional Specifications
               User Guides / Manuals

These documents are very important and can help to build the product and test it.

Seek Guidance … Ask others:
To understand “what to be tested”, you must learn to ask others about the product and seek guidance who has relevant knowledge about the product workflow.

Use Test Case Design Techniques:
The test case designs can be developed using these three important techniques:
  User based Scenarios
  Boundary value Analysis (BVA)
  Equivalence Partitioning (EP)

Question others:
If you still want to understand about the system and learn to develop more test cases.

Learn to Question others. It can be to “Users”, “Project Managers”, “Programmers” and even “Testers”. Remember; think you don’t know anything and ask them to tell about the product, but don’t forget to interrupt to explain more in detail.

This can help you to generate more test ideas of what to test.

Conclusion:
Test generation is a skill, it should be learnt and understand to create good test cases and helps to provide exactly or more than the customer needs.

Tip to Management: Create a friendly environment between the teams to interact frequently; this can help the product successful.

If you think, this post helps...Please let me know any Feed backs or comments.

Cheers, Happy Testing …  J



Posted in | Leave a comment Location: Mysore, Karnataka, India

My Journey towards "Miagi-Do School of Testing"

Here is one more Milestone - 50th Blogpost and Today’s Date is 18th which is divine and Wonderful Number.

Testing is my passion, I do it from my heart. I try to find happiness in fulfilling my job as a Software Tester.

I have lost myself, certainly when I lost many opportunities during the past days. I have taken a break from my life and took time what are negatives and positives in my life.

I got heard so many things, “He is not having testing certificates or skills to show up his work, so he is unable to get a project.”

I am very thankful to "Sharad Rathi" (Linkedin) “Michael Bolton”, “Ajay Balamurugadas”, “Sudhamshu Rao”, “Parimala Hariprasad”, “Anshul Jain” and many others… for giving suggestions during my initial days of my career.

After getting inspired from them, I have started Blogging on Testing and participating in different testing contests and reading many testing articles to learn more and keep my goal.
One day, I have seen a post on a “There is an Initial challenge to become a part of Miagi-Do School of Testing”. The challenge was quite interesting, It was on “LightSabre”, instructed by “Michael Larsen”.

It was pretty exciting while having this challenge, and having a good time with Michael Larsen, even though we had time differences (PST vs IST). He is very cool mentor. He pointed me quite interesting questions during the challenge to how I should look at the things. I am very much thankful for him and inspired me with Questions he raised after the challenge.

“Many of the great achievements of the world were accomplished by tired and discouraged men who kept on working for their passion.”

Now, I am “Student of Miagi-Do School of Testing”. Now it’s time to interact, learn and contribute with amazing team.

Also, I got learn my mistakes, few appreciations and awards during this journey from my friends, seniors and mentors.



Conclusion
“God Almighty: My Rock star, my inspiration and my guide.  If God is not in your life, you've either got to be really lucky or really passionate to move towards success”

I am gratitude and very much thankful to all the people who are part in this journey of my career And also I will continue to learn & share more on testing and try hard to be part of Indian Testing Community.

Posted in | Leave a comment Location: Mysore, Karnataka, India

Tests without Specifications : Part -1

To write a good test cases, a tester needs a good reference, which is requirements (functional or design) specification documents. Using this, we measure the quality of the test done on software, whether it reached the goal of the requirements specified by the client.

The specifications can make tester’s job easier and client also saves time – money, helping in building a good product.

But today, sadly, testing is not considered during the documentation. There might be many reasons, may be specified testing resource is to be allocated; project budget might be released; testing is seen as part from development process etc.

So when requirements are not proper and doesn’t come your way, at that point what you would do and whom you point the issue? What can we do apart from panic?

But you have to start testing somewhere.
Here are some techniques to derive in this kind of situation and can be applied to any kind of software projects.

                Identification of Test Requirements
Test cases can be developed from available information, which describe the product developing at some point of the development process. These are called as test conditions, and can be used in generating a suite of test cases.
                Test requirements can be generated using past experience.
Test cases can be written from past experience on projects, what you have tested, how did you test it, any particular areas where bugs can be found in past projects?


Hint for Testers: Search through the defect logging tool on the previous projects, this may help get you to focus and make a contribution to the project.Coming soon with Part-2....
If you think, this post helps...Please let me know any Feed backs or comments.
Cheers, Happy Testing …  J

Posted in | Leave a comment Location: Mysore, Karnataka, India

Testing Book of the Month : July

This is a new series, I will Blog on "Testing Book of the Month" - Books to Read about Testing or Interest to Testers.

All the posts, are labelled with "Testing Library".

Lee Copeland has over thirty years experience as an information systems professional. He has held a number of technical and managerial positions with commercial and non-profit organizations in the areas of applications development, software testing, and software development process improvement.



He is a well-known and highly regarded speaker at software & testing conferences. Lee is the author of A Practitioners Guide to Software Test Design, a compendium of the most effective methods of test case design.

Posted in | Leave a comment Location: Mysore, Karnataka, India

Is there Testing called Exploratory Testing?

Few months back, when I went for interviews: I was quizzed with a question.

Q: What kind of testing you performed in your previous projects/ company?
A: I went blank because I do learn about the project, explore the standards, try out my ideas whatever comes to my mind and execute them to deliver good quality product to the customer/client.

When I said this, Interviewers dint accept me. I got rejected.

This is a definition which I learned from Cem Kaner:
“Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test”

This is the same I answered in a practical way, what I do.

Every time whenever a new topic I hear, I use my “W3H Technique”.
“What – Why –When – How” –> Asking this questions, I can learn few things to about it.

I am thankful to my first team – Auto ID Team, who has observed my skills and gave me Testing job”    

In simple words, I do Testing in an exploratory way.


In recent days, I heard from one of the tester saying, “He is doing exploratory testing”.
-----

Now the point comes, Is there Exploratory Testing?

Then I immediately referred back to Cem Kaner Definition. Then I re-read individually each word.

I framed it as “Testing is an investigation by observing or experiencing the product, and providing information to stakeholders/ customers about quality of the product or service under test”.

So, There is no “Exploratory testing” or “Any other testing”.  All testing is exploratory way.




Whenever a project is assigned to me, I keep targets – how many defects I can find in a day faster and report them in the defect tracking tool. Good testing requires thoughtful effort and practice.

I then start learning about the technology, the programmers had done coding and designers have done their designing. This increases my knowledge and understands the technical architecture of the project and can report the bugs in technical terms.

If you attend any conferences or meetings on software testing: “No one says, How to test?”

Because, Testing is an investigation of a product, The good quality product comes out – if you do explore much and experience it, to give it to customer with minimal risks.*
*No Product delivered is 100% bug-free, but we testers have to try hard to find the risks hidden and minimize the risks at least 90%.

If you think, this post helps to clear about Exploratory Testing? Please let me know.

Cheers, Happy Testing …  J

Posted in | Leave a comment Location: Mysore, Karnataka, India

How do i test Email Address Validation... ?

Every time I have been on Website Projects, I always had a testing task to validate Email Address text field.



I heard the following from many developers say: Why does User enter wrong email address? And why do we need to validate the Email address.

Many feel why we need to test the email address format, why do the user. But as am passionate testers, I always try to research to find out new things and learn and try out, how it can be useful to make the application stable. 

I always go for hunt to find out valid or invalid email test cases. So, I thought I will write a post as well as it can be useful for future references for me and for the testing community.

The Valid Email Address follows the official standard Regular Expression (regex), defined in RFC (Request for Comments).


All the Email messages which are sent from Email Addresses should conform that they accept standards specified by IETF (Internet Society).

The sad thing is, many don’t read and ignore the RFC Standards proposed, but prepare their own regexp to issue a valid email address.

Question:  What is the maximum length of the email address can be?
Answer: 254 Characters.

The above are the test cases to check if Email Address is Valid or Not.

I am very thankful to “Chan Chaiyochlarb”; a software engineer specialized in Quality. I dedicate this Blog Post to him, in return of favour, for helping me in testing career.

Question: Is there a way to check whether your email address is according to RFC Standards?
Answer:   Yes,"Dominic Sayers" has made a lot of efforts to make a project.

Try out yourself: http://isemail.info/  ( is_email is email validator according to standards or not).

Posted in | Leave a comment Location: Mysore, Karnataka, India

Want to Capture Screens on Windows?

Every time during testing, we find issues and report them in the bug tracking tool. As said in the previous post: “Usability Testing or Functional Testing?”. Taking the screenshot gives advantage to testers. 

If you have missed it, check out here.

After logging the defects in the bug tracking tool, there are many cases where Programmers ask to repeat the same thing you have done, when you have logged it.

So, here in this post – I would like to share the cool tools which are useful for Testers.

Cool Tools for Testers:


 
Most of them would be using the free editions of “ScreenCapture” or “SnagIt” for capturing the Screens.

It’s a delight that windows too have two inbuilt Screen Capturing tools.

Firstly, Most of them Know “Snipping tool” – This you can find in Programs, and It allows to screen capture of an area neatly. This is very handy tool to use from Microsoft.

Another tool, which is hidden inside Windows, which can record the steps you perform.

The Tool is available as “PSR.exe” – It is known as “Problem Steps Recorder”. This can help you a lot, as this can record the steps you took while testing the test scenario and at the end, a Problem Steps Recorded summary file is saved in a zip format with pictures and actions performed.

Enjoy Testing :) 

Posted in | Leave a comment Location: Mysore, Karnataka, India

Usability Testing or Functional Testing ?

Whenever an application comes to testers, do you know what Project Managers first say to Test team?

The answer would be, Test the Functionality first and release the build tonight as it’s very important.
Yes, Functionality is very important for an application to work. But there is another important to be tested, before it has to be released, which is side-lined due to time frames.

Functionality testing includes testing all vital and essential features thoroughly to work without any flaws in middle of the application and Application should go in a smooth way in the process of fulfilling the functionality.

The Other Important thing which is mostly taken aside is Usability Testing.
Usability Testing should be start with the Requirement specification and analysis phase then goes to design and then in coding phase. If we perform Usability testing in the same phase, Then Usability testing is just like Verification. This Testing can happen after (or) along with Functional Testing.


Important: If we build a project and then test the ‘Usability Testing’, then we will be setting a stage to cause serious problems.
During the initial stages of the development cycle, Usability Testing comes first and as the project progress – the Functionality testing takes its upper hand.

Whenever a project is developed, it’s shown to Client about the Project Progress and for any improvements or changes to be made in the first phase of the project before it is released to LIVE.

Majorly, many clients are very particular about the look and feel and check deeply every minute point as they gain more customers than their opponents in the first sight of the their project.

We Testers are given us job to make their project go easy without any issues (even though it is small). If anything issues, the client observes and reports to the management: First every one points out their eyes to Testing Team. 
But I don’t understand, they won’t ask the programming team who is handling all the issues coming from testers and why they are not released with the current build.

I knew everyone says, a project can never be 100% bug-free. But if you test-hard enough, a project can be 100% bug-free without any issues.
Many may think which is more important for testers, Testing the functionality or Usability.

Its same like: “Do you love your parents or your loved ones?”
There is no one answer, both are Important for project success and long run without any issues. But at very first sight, every client sees the usability first and then goes to functionality.


To overcome that at that situation, here is above Tip for Testers.

Tip to Testers: Even though, if it is very small spelling mistake or an issue with respect to GUI / Design / Usability, report all your bugs in the defect tracking sheet. Keep all the test execution and bug tracking sheets in handy.
Additionally, whenever you execute a test-case take a screenshot of them, it would be much beneficial also.

Also Above is my Request to Project Management Team.


Kind Request to Project Managers: If anything goes wrong while demo to the client, don’t ever point out a single person for the mistakes. It’s a Team work in project development and everyone is responsible including him.

Leave a comment

STICK for Testers: For Testing Image Upload Functionality.

Here is a STICK for Testers. STICK means "Software Testing Checklist".



  1. Check for uploaded image path.
  2. Check if there is a upload and Cancel Buttons are there and working properly.
  3. Check the image upload functionality with image files of different extensions (JPEG, PNG, BMP etc.).
  4. Check image upload functionality with image filename having space or any other allowed special character.
  5. Check image upload with image size greater than the max allowed size. Proper error message should be displayed.
  6. Try to upload the image file with Zero Bytes. Proper error message should be displayed.
  7. Try to upload the image file with image size less than the max allowed size. Proper error message should be displayed.
  8. Try to upload the image file with exact size that was specified.
  9. Check image upload functionality with file types other than images (e.g. txt, doc, pdf, exe etc.). Proper error message should be displayed.
  10. Check if images of specified height and width (if defined) are accepted otherwise reject the images and should show proper error messages.
  11. Image upload progress bar should appear while uploading for large size images.
  12. Check if cancel button functionality is working in between upload process.
  13. Check multiple images upload functionality.
  14. Check image quality after upload. Image quality size (@AjayBalamuragadas) should not be changed after upload (should not be shrinked / cropped).
  15. Check if user is able to view the uploaded images.
  16. Check if the image is converted from other formats (doc/pdf to jpeg/png) and can be uploaded.
  17. Check if the image file gets uploaded if it has more than one extension (filename.jpg.png).
  18. Check whether the file name of the image in the file uploader gets enabled to edit.
  19. Check if image uploader expands/shrinks when the Image file name is small or large.
  20. Check whether the image uploaded can be Deleted or not.

Posted in | Leave a comment Location: Mysore, Karnataka, India