The Life-Long Journey of Learning!

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 STICK for Testers: For Testing Image Upload Functionality. Sunday, July 07, 2013 Usability Testing or Functional Testing ? Tuesday, July 09, 2013 Why do you need to choose Test Automation? Wednesday, July 10, 2013 Want to Capture Screens on Windows? Friday, July 12, 2013 How do i test Email Address Validation... ? Monday, July 15, 2013 Is there Testing called Exploratory Testing? Tuesday, July 16, 2013 Testing Book of the Month : July Wednesday, July 17, 2013 Tests without Specifications : Part -1 Thursday, July 18, 2013 My Journey towards "Miagi-Do School of Testing" Tuesday, July 23, 2013 Tests using (Design and Functional) Specifications (Part-2) Thursday, July 25, 2013 Software Testing Good Practices Tuesday, July 30, 2013 Its your Life.... Le...

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 f rom 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 p...

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...

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 desig...

Here is one more Milestone - 50 th Blogpost and Today’s Date is 18 th 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...

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.       ...

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.

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 Tes...

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). Refer:  http://www.ietf.org/rfc.html All the Email messages which are sent from Email Addresses should conform that they accept standards specified by IETF (Internet Society...

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 perf...

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 Funct...

Here is a STICK for Testers. STICK means " Software Testing Checklist ". Check for uploaded image path. Check if there is a upload and Cancel Buttons are there and working properly. Check the image upload functionality with image files of different extensions (JPEG, PNG, BMP etc.). Check image upload functionality with image filename having space or any other allowed special character. Check image upload with image size greater than the max allowed size. Proper error message should be displayed. Try to upload the image file with Zero Bytes. Proper error message should be displayed. Try to upload the image file with image size less than the max allowed size. Proper error message should be displayed. Try to upload the image file with exact size that was specified. Check image upload functionality with file types other than images (e.g. txt, doc, pdf, exe etc.). Proper error message should be displayed. Check if images of specified height and width (if de...