Showing posts with label software testing. Show all posts
Showing posts with label software testing. Show all posts

Monday, May 30, 2022

The fundamentals have gone for a toss

 25 Fundamental Mantras for Good Testing

  1. Why are you testing - Know it
  2. Ask it if you don't know it
  3. Confirm it if you are not sure about it
  4. Test it out before believing anything
  5. Listen to everyone but you take the final decision
  6. Save as soon as you see it
  7. Try for Autosave wherever possible
  8. Take backups
  9. Pay attention to the Context
  10. Pincode can have letters, names can have special characters. Study the domain well
  11. Document well, read documentation well
  12. Write clearly, Think deeply, Read widely
  13. Use tools wherever it helps
  14. Know limitation of tools
  15. Have a large network of friends and fieldstones
  16. Learn to connect the dots across fields
  17. If you can model well, you can test well
  18. Know mnemonics and heuristics
  19. Pay attention to keywords - always, never, must, should, obvious
  20. Learn Safety Language
  21. Keep collecting fieldstones
  22. Start recording and then testing. Never waste time unless it is part of a test
  23. There is no one good way of testing. 
  24. Testers can get bored easily if you keep doing mundane stuff. Add variety to your questions, ideas, routines.
  25. There is already a lot of work done by the community. Learn to search well.
  26. Organize well.

Leia Mais…

Saturday, March 15, 2014

Testing Strategy and Test Planning - My mindmap

I do not subscribe to any testing related blog feeds. Instead, I pay close attention to Joris Meets' twitter feed and check Ministry of Testing feed. Both of them do a great job of consolidating important testing related blogs/articles. While browsing through James post on Test Jumper, I liked what he wrote. It matched with my preferred style of working - help people identify traps, test with them and create an environment conducive to learning and improving testing skills.

There have been instances in my previous and the current organization where I am called upon to help a project which is going nowhere. Most of the times, they face one of the situations:

  • Important bugs being identified late
  • Testers on unplanned leave
  • Unstable product or need for better coverage
  • Inexperienced project team
  • Important project
I like such challenges. They seem to get the best out of me. I visualize this video and feel good at the additional responsibility given to me.

I started thinking of what gives me the confidence of taking up the role of a Test Jumper. Can I pass any checklist for someone to use and build on it? I launched XMind and here is the output. 
My Project Preparation
This is again a heuristic and not a final plan. It depends on the project, answers to the different questions and other factors like project, team, stakeholders, risks and deadline :) 

Leia Mais…

Monday, January 28, 2013

Software Testing Training - Skype

Skype Training from Jan 31st



Leia Mais…

Wednesday, December 26, 2012

Release of my 4th book on software testing

I have released a book each on my mother's birthday followed by my sister's birthday and my birthday. Obviously, my father was feeling left out and I am releasing a book on his birthday. This is my fourth book on software testing.

Book 1: What If... A question every software tester must ask.


When I logged my first bug, I thought – ‘What if’ this bug was found after release? Years passed, many products were released, and I gained a lot of varied experiences.  I made a few embarrassing mistakes too. There were few instances where I wished that someone had warned me beforehand. So, I started preparing a book of tips targeted at software testers. Special care has been taken to keep each of the 22 chapters short and to the point. Emphasis is on ready-to-use tips which would give you instant results.

Book 2: What If... 50+ tips to win testing contests. 


This book is a collection of tips which might help any tester competing in a testing contest. Testers are under tremendous time pressure and the competition is tough. Skilled testers have a better chance of winning the contests. After participating in a number of testing contests, I realized that it is easy to win any contest if you dedicate some time and demonstrate the right skills. In this book, I have tried to highlight few points which will improve your chances of winning the testing contest.

Book 3: What If... 50+ tips to boost your productivity.


This book is a small collection of tips, tricks and list of tools to help boost your productivity. This is entirely based on my experiences in software testing as well as using computer. Internet is so powerful. A simple Google search will yield you so many search results. Google for “Screen Capture Tools” and you will find a minimum of ten tools in the first page itself. Which one do you choose? Do you have the time to try each one of them? What about Windows command prompts? There seems to be more than fifty commands. Which one is useful for us, especially for a software tester?

Book 4: What If... 50+ tips to improve tester-programmer relationship



This book brings into picture a very important person - the programmer & the programming team. Each one of us might have the experience of working with at least one tough programmer. Some programmers are very friendly and help us with finding bugs. Some of them are very strict with their deliverables and do not respond to any queries outside office hours. Some hardly talk to you unless you ask them a question. There are different types of programmers and bring in variety to our testing challenges. As I write this book, I have completed over six years of software testing and interacting with multiple programmers across different projects within and outside the company. With a rich experience of working with tough programmers, I write this book to help you.

My special thanks to my family members (for having a gap between the birthdays), my friends for accepting me as I am, my friends on twitter, facebook who keep encouraging my work, the programmers who keep challenging me, those who bought my first three books, those who provided me feedback and those who continue to believe in me :)
And of course, my love and thanks to my father who continues to encourage me in everything I do.

How to buy the books:
Download from bit.ly/booksaj

Leia Mais…

Wednesday, December 5, 2012

test-ed.in conference

Dec 05th 2012
Thanks to the organizers and the team behind this event.

Leia Mais…

Sunday, October 28, 2012

Flipkart Testing @ Hyderabad - Session Results

At the end of Session 1 & Session 2, we preapred two mindmaps about the product & the testing plan.
The corkboard image is also put up below.
Thanks to Anurag & Raghavendra.


Consider this for testing
What to test

Testing Notes

Leia Mais…

Flipkart Testing @Hyderabad - Session 1

One of the reasons I travel at my own cost to present workshops at other cities is that I get a chance to meet  other software testers. I arrived at Hyderabad on 27th October early morning around 5.30 am IST. The first tester I met in Hyderabad was Raghavendra who received me at the railway station. From there, we went to his room, got ready and left for the venue for the workshop. The experience at the workshop is for a different post. I missed my train and had to stay one more day at Hyderabad. Raghavendra was generous enough to accommodate me in his room for an additional day. His hospitality is definitely commendable - right from food, entertainment facilities, the unlimited energy when asking questions on software testing and so on. Thanks Raghavendra.

Raghavendra wanted me to explain my testing approach from scratch. He wanted to know how I test, what tools I use, what bugs I find and so on. Though we were tired after the workshop, we were awake till 11 pm IST discussing about software testing. The TV was on mute and we don't know when we dozed off. The notebooks were filled with lots of notes.

Plan for Sunday
Next day, as planned we got up early and I invited Anurag - a budding software tester whom I met online in my Skype training class and also at the workshop on Saturday. We planned to test a product for close to four or five hours and present a test report.

We started at 12.06 pm IST and decided to use corkboard.me to share notes.
The application to be tested was 'Flipkart'. We spent the next 45 minutes testing and noting the issues, tests, tips, notes.
Attached are the corkboard images before and after the 45 minute session.
When we started
After Testing Session 1


Leia Mais…

Saturday, October 6, 2012

Oct Batch - Online Hands on Testing Training

The first batch started in the month of April. It was well-received and you can find the comments here.
Encouraged by the participants, I conducted the second & third batches too. I have learnt a lot from the three batches, the participants, the drop-outs, the assignments, the emails and the feedback. Few of them attended all three :) Thanks. While I conducted three batches, I also attended the online 'Power Searching With Google' course.

To complement the online course, I have started conducting onsite courses on Software Testing with Exploratory Testing as the main theme. The Chennai workshop was a first time experience of conducting a full day workshop. So, I am back after a month's break. Some of you were asking me about the fourth batch and here is your chance.

Course Contents:

  • Mind maps - Introduction, Creation, Different types, Tools, Tips, Collaborative mind map.
  • Testing Session - Bugs and Oracles, Mnemonics, Heuristics, Tips, Intermittent bugs.
  • Tools - Screen Capture, Screen Recording, Note-taking, Shortcuts, tips to improve productivity.

What is different in fourth batch course content?
I have slightly modified the content and will be covering few topics in detail. This course will be slow and detail-oriented. I want to answer more questions in this course compared to the previous three batches.

How do I join?
Ping me on Skype [ajay184f is my Skype ID] and let me know that you are interested to attend the fourth batch of my hands on training on software testing.

Date & Time?
Every Monday, Wednesday & Friday starting October 10th till Nov 2nd.
Time: 10 pm IST to 11.15 pm IST
Cost: Its Free. I need your active participation, nothing more.

Any questions?
If you want me to conduct an onsite training in your city, email me [ ajay184f@gmail.com ]

Lets meet, test and share what we know :)



Leia Mais…

Wednesday, August 1, 2012

August batch of online course on "Software Testing Skills"

Its time for the third batch to start. Third batch of my course - "Software Testing Skills".


What this course is about:
The rough outline would be

1. Building a Feature Map
3. Information gathering through Application 
Tours
4. Effective bug hunting, investigation and reporting
5. Preparing a Test Report

I am open to changes based on the testers' skills and experience.

Is there any mailing list where I can see artifacts by students of previous classes?

Schedule:
Every monday, wednesday and friday starting from August 06th till August 31st

Time: 
10 pm IST to 11.15 pm IST (4.30 pm GMT to  5.45 pm GMT)

Cost:
It costs only your time. There is NO FEES.

The sessions are over Skype chat only. No calls.

Interested?
Email me (ajay184f@gmail.com) with the subject: "AjAug2012" and provide your Skype ID in the body of the email. I would appreciate if you would add me on Skype too.

What will I learn? Can you tell me more about how will the experience be?
I will let the students who attended comment on this post.

Leia Mais…

Sunday, April 1, 2012

The Tools/Commands/Tips I use - Part 1


Thanks to Jon Bach for the inspiration behind this blog post.
This blog post is an attempt to tell you the different tools I use and how I learnt different tips & tricks useful for testing. Feel free to comment with your choice of tools/tips/tricks.

The first time I switched on a computer was the time I joined a computer course. The class was about DOS and MS-Office. That day I got to know what Ctrl + Alt + Delete did. It was like a magic combination. I did not know anything about what an operating system did. All I knew was that, you needed to press Ctrl + Alt + Delete to unlock the computer. Then I happily played Dave for the next one hour.

After few months, I understood the joke about a software engineer shouting "F1" when in danger. Well, he needed "Help" and the most common key associated with Help was F1. As I typed my college assignment in MS-Word, I found it difficult to edit long sentences. I pressed the left/right arrow keys till the cursor was at the right word and then I edited the word. My friend then showed me the power of Home and End keys.

During college days, me and my friends used to watch movies on friend's computer. Windows Media Player or VLC were the most commonly used tools. I was surprised when Alt + Enter changed the mode to Full Screen. Then I got to know what PrntScr did. I was always hesitant to use those keys - specially the F1 - F12 and the Insert, Pg Up, Pg Dn, Home, End. I did not want something bad to happen as most of the savings went into buying a computer.

Then I joined as a software tester in a company. The first day in training, the application was not responding. It was happening only on my machine. The programmer was called for by my trainer. He came and pressed some keys and Windows Task Manager popped up. I asked him the combination. It was Ctrl + Shift + Esc. That key combination was the first combination I learnt as an employee. Then, he right clicked on the Application name, Go to Process and clicked 'End Process'. This was how he force closed the application.

I spent more time observing the programmers. I did not know how to check the version of any application other than using the About/Help menu. The programmer taught me to check using the Add/Remove Programs window to note any application version. When I made a note of the flow to get to Add/Remove Programs from Start > Control Panel, he immediately showed me an easier way. He asked me to try 'Run > appwiz.cpl'. When my eyes asked the question "What?", he told me that appwiz = Application Wizard and cpl = Control Panel. I smiled and thanked him. My other friend taught me what Run > temp and Run > %temp% did.

Then I started using more tools. I used CCleaner. I was surprised by how much space it cleared for me by deleting the temp files and fixing some registry related files. The amount of free space increased. This tool was specially useful to me who never cleaned the temporary files. It cleans up your computer in minutes. As a tester, I have to take many screenshots. My friend suggested Greenshot and it was quite good. I used it for some time before I found Jing. I think it was Elena Houser who introduced me to Jing at CAST 2011. Yes, it was Elena. We used it for the testing competition. I continue to use it.

As I tested more and more applications, I found many application crashes. Then my programmer friend taught me how to use DrWatson. He was happy that I attached the logs and I was happy that I learnt something new. In one of the applications I tested, I found that the logo appeared to be a bit different from the one on the company website. When I showed that to the programmer, he attributed that to my machine display settings. I was not convinced. I searched for a tool which will let you know the RGB values of the color and also the hex code. I used ColorCop and proved to the programmer that there was indeed a difference.

After attending Rapid Software Testing (RST) workshop, I started using Perlclip a lot more. It was easy to generate lots and lots of text very quickly. Some of the programmers were impressed and the testers surprised. :) I started attaching video files to my bug reports. WebEx Recorder proved to be a very good tool for this task. The only drawback was that you could play the recording only using WebEx Player as the output file format was .wrf . So, I started using Jing to record the videos too.

I started registering on many social networks. The number of open applications too increased. While I knew that Alt + Tab switched between applications, I faced a lot of difficulty when the number of tabs in my browser increased. A browser is a single application and Alt + Tab did not help. Accidentally, I discovered that Ctrl + Tab switched tabs on a single browser instance. It was all good until Ctrl + x opened the xth tab where x was a number. Example: If you had ten tabs open, Ctrl + 2 opened the second tab. Ctrl + 9 always opened the last open tab.  Well, it doesn't open the respective tab, it just brings the focus onto the tab.

There were instances where I used Ctrl + to zoom in and Ctrl - to zoom out on a browser window. But I did not know how to view the original size through any shortcut. Ctrl + 0 seemed to be the shortcut.
I received a lot of emails with broken hyperlinks and I had to manually copy the entire link text and paste on the browser. Then, my friend showed me that using "" and typing the text between the quotes and pressing enter would turn the entire text into a hyperlink. This helps avoid broken links specially for network paths. Try it on Outlook.

There was an informal group in my company started by me and my friend. We called ourselves the Mission group. There was no hierarchy and we shared useful information about testing via emails. As we shared lot of article links, we used bit.ly a lot to shorten the url. I used to take a printout of the article and write just the 6 characters of the bit.ly link at the top of the page. We used typewith.me a lot to take simultaneous testing notes sitting at different computers.

Sometimes, the visible screen on the browser was not enough to highlight the problem. I used F11 to view full screen and then take screenshot. I have also used the website PDFmyURL to convert the entire page to a pdf file.

And for mind map lovers:
Don't forget to comment with your choice of tools/tips/tricks. Thanks.

To be continued...

Leia Mais…

Thursday, November 5, 2009

Golden Chance to meet Michael Bolton in India!!!

QAI India
Organized by
Edista Testing Institute
Learn, Rapid Software Testing with Michael Bolton Learn, Rapid Software Testing with Michael Bolton Learn, Rapid Software Testing with Michael Bolton
Mumbai: 12 Nov.2009 – 12 Nov.2009 Hyderabad: 16 Nov.2009 – 16 Nov.2009
Chennai: 13 Nov.2009 – 13 Nov.2009 Bangalore: 17 Nov.2009 – 18 Nov.2009


Course Description

Rapid testing is a complete methodology designed for today’s testing, in which we’re dealing with complex products, constant change, and turbulent schedules. It's an approach to testing that begins with developing personal skills and extends to the ultimate mission of software testing: lighting the way of the project by evaluating the product. The approach is consistent with and follow-on to many of the concepts and principles introduced in the book Lessons Learned in Software Testing: a Context-Driven Approach by Kaner, Bach, and Pettichord. In interactive workshop, Michael Bolton, the co-author (with James Bach) of the Rapid Software Testing course introduces testers, managers, developers, and any other interested parties to the philosophy and practice of Rapid Software Testing, through lecture, stories, discussions, and “minds-on” exercises that simulate important aspects of real software testing problems.

Contact Details
Bangalore/Hyderabad: Akshay Raj
(M): +91-9845176034
(P): +91-080-41574806/7/9
akshay.r@edistatesting.com, training@edistatesting.com

Chennai: Harsha Bhat
(M): +91-9845098916
harsha.bhat@edistatesting.com

Delhi: Divya Raturi
(M): +91-9871252501
divya.raturi@qaiglobal.com

Mumbai: Kishor Parab
(M): +91-9821251126
kishor.parab@qaiglobal.com

I have registered. When will you register?

See you at the workshop.

Leia Mais…

Sunday, August 9, 2009

Trio Testing at a distance - Part 1


Testers involved:
Ajay Balamurugadas, Sharath Byregowda and M V Manoj

Website Tested:
www.tinyurl.com

Mission:
To find bugs.

Start Time:
Aug 09 2009, 0022hrs IST

End Time:
Aug 09 2009, 0145hrs IST

About the website:
TinyURL is a web service that provides short aliases for redirection of long URLs. Kevin Gilbertson, a web developer, launched the service in January 2002 so that he would be able to link directly to newsgroup postings which frequently had long and cumbersome addresses.

Our Testing Session highlights:
The entire session was conducted over Group Chat on Gmail.
We started our search for a software to test around 1145hrs on Aug 08th 2009.
The search continued for an hour with Eyeos, Barcode4J and Piwik grabbing our attention.

Lack of prerequisites for the above softwares forced us to test TinyURL.

Bugs were communicated to the group as and when they were found.
The tests were based on learning from the tests conducted by the other testers.

Sharath's tests focussed on the security issues. Wish we had a proxy network setup. He'd have loved to test on a proxy network.

Manoj's tests focussed on the usability and Custom Alias feature. He highlighted the disadvantages of using Custom alias feature.

I focussed on the general functionality of the website.

It was fun testing coupled with good learning for me.
Though the testing session lasted for over an hour, the lessons gained would be for a long time. Thanks to Sharath and Manoj for their determination and passion at odd hours of Sunday.

Please find the testing report shared at Scribd.

If you would like to participate in such testing on weekends, drop an email to me at :
weekendtesting@gmail.com

Leia Mais…

Wednesday, April 1, 2009

I support ETI Finishing School... Do you?

Congratulations !!!

The ‘Hands on software testing training’ has brought in a bold change.

Are you brave enough to appreciate these ‘testers’?
Do you still believe that ‘training through slides’ is better than ‘hands on training’?
Then read no further…
The results might shock you.

The Test EXPERIENCE Reports are out and available at http://testertested.qualityfrog.com/erpstt.pdf

How do you feel?

Don’t you think we need to support this unique school of software testing?

How Can I support this initiative?

Send an email to isupport@etifinishingschool.com with
-Your Name
-Your Designation
-Your Organization name
-Your Web Address

Friends, There is never a wrong time to do the right thing!!!

Who knows, few years down the lane, this may be the turning point in the history of software testing.

Be proud to extend your full-fledged support.
Thank you for your valuable time.

Leia Mais…

Wednesday, July 9, 2008

Interesting defect

This is about a defect I found in my application this morning.

The application was not tested for a month due to some requirements change. I was shifted to test some other products and finally I got my application back.
There were supposed to be lot of changes introduced as per client request.

My application has a login window as soon as it is launched.The login window has fields username & password and OK & Cancel buttons.Username: guest, password: guest

So, the first test is as follows:Enter guest in the username field and guadt in the password field.Click OK.Observed Behavior:A window with the message 'Incorrect username/password.' popped up.This window too had a OK button.
I clicked on OK and clicked again on OK button in the Login window.

As stated in www.satisfice.com/rst.pdf slides 108 and 109, I wanted to test 'Error Handling'.I kept on pressing 'Enter' key in the keyboard.

This happened for more than 20 times and I was reminded of M.Bolton's statement in one of the post : 'Do the right thing after you have tried the incorrect thing' (Not the same words)

So, I thought of entering the correct credentials as I had tried enough of incorrect credentials and the application is not allowing me to enter.

I entered 'guest' in both the username and password fields.

Bingo!!!

The same window : 'Incorrect username/password' popped up.

I deleted the password and entered the password 'guest' again carefully and slowly.
Again the same message.I found something interesting here.

I went to the developer and asked whether they had changed the password and they replied 'NO'.

I closed the instance and opened a new instance.Entered 'guest' in both the fields and the application opened without any problem.
So, I realized that entering incorrect credentials and then entering correct credentials might reproduce this defect.

I tried entering incorrect credentials 10 times and the correct credentials at the 11th time. Application worked.
15 times, it worked.
20 times, it did not work, message popped up.
19 times, it worked.
21 times, it did not work, message popped up.

So, finally I logged a defect that 'After 20 incorrect logins, login with correct credentials also fails.'

Test Ideas that helped me find this defect:
Error Handling technique.
M.Bolton's statement.
Ben Simo's 'Failure' mnemonic

Have you ever come across such a defect?
Have you come across defects more interesting and wierd than this?

Please share the test ideas too as it may help others.

Scripted Testers:Would this defect be found by the execution of test case?

Feel free to question, discuss and comment.
Regards,
Ajay
www.enjoytesting.blogspot.com
ajay184f@yahoo.com

Leia Mais…