‘TestAway’ has been a phenomenal addition to my life both personally and professionally. I feel it has the potential of becoming the next big thing in the community space.
And I am saying this without any adornment based on my experience and interaction in the two high-energy events of Goa and Shimla and also as someone who is involved from day 0 to official cessation.
A look at the Goa and Shimla
Goa and Shimla TestAway both had their own flavour and enthusiasm.
I love sunsets over the ocean and Goa is certainly a good place to experience this.
Imagine this topped with a private luxury villa housing swimming pool and a terrific set of Testers from different corners of the country.
TestAway Goa venueSandeep Garg educating us with ‘Critical Thinking’ workshopAt Chapora fort with PD
After Goa, the next TestAway was planned keeping in mind the call of the Testers to have another one soon.
Originally the TestAway was thought to be an annual occurrence but we all know two TestAways has happened in less than 8 months.
After an event in a coastal backdrop, it was not less than obvious to have the next one in the Mountains. Shimla ticked the most number of boxes wrt to accessibility and availability.
And what an event it has been high voltage, high amplitude, high altitude everything high minus the attendees 😀
Preparation and Screening
The joy I was talking about is yet to appear 🙂 If you wondered what goes in making the TestAway event, stay glued, I would be leaking some details 😛
TestAway is based on the residence learning program, the concept is, selected Testers are invited for a 3-day learning and experience program.
Almost all the attendees are strangers and all we do in the 3 days is chat-share-connect-motivate-learn. It really works. Like when was the last time 15 different minds from different specialities and all equally passionate brainstorm, chat testing for 3 days and 3 nights. Imagine the outcomes of such elegant deep discussions you always wished to have with someone like-minded, won’t that be amazing?
Let’s talk a bit about the planning part. The planning always begins with a hunt for a location and then for the venue. Easy said than done. I find this as one of the most draining tasks in the overall planning and execution.
Risks are pretty high in the sense that what if the location or venue doesn’t work out. 20s of calls are made to hotels, resorts, villas, homestays for availability and pricing. Then the shortlisted properties are again evaluated on 50+ parameters.
Finding a balance between the luxury and pricing and negotiating with uninterested hoteliers is what I don’t love much 🙂 But that’s what the 1st step is for kickoff.
Next set of activities involve thinking about workshops, round table topics, games and other schedule-related things. While the TestAway page and related pages like invitation forms, etc are made live, other items like branding items, welcome kits are planned and orders are provided.
Stationery accessories itself has a list of 60+ different items to collate. All these activities too take ample time and energy as affording a 360-degree merchandise partner is out of the question. Moolya Software Testing Pvt. Ltd. do support TestAway while being a co-sponsor for the branding kits.
With less than 45 days left, screening candidates becomes a daily job. Sometimes they are busy, sometimes we, multiple calls are made explaining the concept of the TestAway, general QnA and seeking their expectations from the event.
It’s not always this straightforward and sometimes it turns funny too when candidates ask the places of the city tour that they will be taken.
We get some relief from the preparation once the squad is ready and WhatsApp group is created. Initially, the traction of interaction among the attendees is relaxed but once it picks up that fails to slow down and great relationships starts forging.
That’s the place where 15 Testers camped for 3 days 😀
One of the views from the balcony ?
Thats Ajay educating us in his styleOne of the team brainstorming sessionScene from a bomb defusal game. Friends reacting when you are not able to defuse the bomb 😀Outing to Mall Road, ShimlaFrom the Bonfire sessionMiss those peaceful morning walks up the hill ?
Shimla squad. Can you guess what they are up to 😀
Leaving for the venue
Post Goa, the core team thought of reaching the venue one day in advance as it would give us crucial time to plan out last-minute details. That was the reason we left for Shimla with one extra day in hand.
Mumbai to Delhi was a late evening flight. With 2+ hours in hand, we had assumed we would get the prebooked AC bus from Delhi to Shimla without any serious effort.
Unfortunately, the Ola driver was new to Delhi just like us and we were doing circles of ISBT without knowing ours has already departed. That 15-minute flurry from ISBT to ISBT (don’t ask me details :D) with all the branding items, sippers, T-Shirts, our luggage was crazy.
Drenched in sweat we were running with an inner surety coated with the hope that our bus can be late 😀 It wasn’t, our bus had left the terminal. Luck favoured us with a Himachal State Transport bus for that night, without double thought we boarded the bus.
That night didn’t stop entertaining us. From a young guy, who left open his bladder pressure inside the running bus to an old chacha threatening fellow passengers citing himself as the star of Shimla. Nevertheless, there should be ups and downs otherwise we know what a straight line in ECG means.
On the venue
D-Day is quite special for me as I get to meet most of the attendees for the first time and welcoming them is a good feeling. Post this, the clocks move super fast. Before we realise that we are making amazing conversations and friends we realise oh 3 days have passed and its time to bid bye.
As a volunteer, sometimes we are not able to participate in expert discussions which we wish to. But this never stopped me in putting my points or getting in touch with attendees and talk about something I liked.
One thing we have been lucky in both Goa and Shimla is that we had very generous caretakers. Suresh Ji and Deshraj Ji in White Haven Shimla never said no to any request made for extra aloo paratha or green Himalayan apples or extra cup of Tea. They very smilingly extended their help in whatever way they could be it putting our TestAway flag or making arrangements for cab on runtime. Our Shimla attendees were aware of the effort put by them and reflected their gratitude courteously.
Last pic
Its very heavy on heart to leave the place knowing all these moments are not going to continue or come back. And its heavy on the brain when the tempo traveller from Gozo cabs you booked from Shimla to Delhi eats up your brain for 2 hours in midnight at the Delhi Airport to settle out the unreasonable tolls and taxes.
In the end
I am left with a truth that Testing can be fun. I am left with event memories I do not wish to erase. I am left with friends I would always like to be in touch with. I am left with photos which I would see again and again and which will make me smile. I am left with a dream to repeat.
Disclaimer: This post is my personal memoir and does not represent anything from my employer or The Test Tribe community.
Get in touch with me in case you wish to be a part of or know more about it:
Software development is inherently very dynamic in nature when it comes to changing requirements. This, in turn, makes testing challenging as they have to absorb shocks of changes which may come very late in the development cycle. To collate such testing challenges we turned to our community and received wonderful responses from variedly experienced Testers.
Sharing it here with a view that it will help Testing fraternity as the saying goes ‘Life is too small to learn only from our experience‘
Arokya Samy
In Mobile testing, identifying the OS and mobile devices.
Trying to answer the question from the manager. Why did you miss this bug?
Convincing the developer to accept and have a look at the bug which he was citing as invalid
While working with customers tickets sometimes it is challenging to understand their problems and trying to replicate the same bug in the testing environment
Coverage in the Mobile app Automation Testing
Creating awareness towards the Accessibility Testing
Priti Visaji
Testing under a time constraint that focuses only on task completion and not on test coverage
Geosley Andrades
Automate your project 100% and find all possible bug
Rajan Verma
Complete testing of new features along with its impact on old features within a given time limit
Stephen Kanagaraj
Ever-changing requirements and unclear scope
Kunal Ashar
Proving parallel automation support and maintaining success rate when your application is too dynamic
Mahesh Chikane
I would say something which I have comparatively faced fewer times but was definitely challenging and thought provoking – It was explaining my Testing. Why I test what I test. Why I follow a particular order in Testing. Why certain amount of Testing(X scenarios/ X cases / X hours of exploratory testing) is needed before I conclude my testing for that cycle.
I would suggest to all new testers – Try answering these questions. Probably to yourself first. Try to keep answers practical(Meaning, don’t just say, my gut feeling says three days I need). Backup with some reasons/data.
Trina Acharya
One of the biggest Testing challenges that I have faced and still continue to face is to be able to keep learning new things while doing complete justice to my current tasks.. To have a start and correct direction on it and also to be able to keep working on it so that I don’t lose touch with whatever I learned.
Abhaychandra Chede
Staying Current, A tester has to keep updating oneself with advancing technology. It is very crucial to keep current.
Work Pressure, this might mount around releases as a tester might have to put in extra time
Hamza Bhamla
Have I able to achieve the expected coverage of the feature? At times the creativity of the mind stops at a stage with a thought that this the maximum possible cases. However, there’s always something that is likely to be missed.
Ajay Balamurugadas
Why this small change requires one day of testing
Niraj Yadav
Preparing test data which is expected to as perfect as Production but the client refuses to handle Production data because it is not anonymized and nobody has the bandwidth to do so.
Interpersonal issues of teammates. One of the team members is too casual or lazy resulting in other members to be overloaded and cover up for him until the manager figure out a resolution.
Working under extreme time crunch during the last phase of release as most of the time is eaten up during development.
Working under a manager, management or client who doesn’t understand the importance of Testing rather Quality.
Writing Test cases in absence of proper design document and wireframes. It is much better to write cases parallelly during execution rather than duplicating the effort.
Vadeesh Budramane
Validate the below
Lack of bandwidth as testing was not prioritized during budgeting.
Too much of data to prepare
Test scripts are fragile. I end up updating the same scripts sprint after sprint
I end up spending too much time manually verifying test results out of the automated suite.
Unexpected pop-ups come while executing automated scripts
Steffy Thomas
I think it should be reproducing intermittent issues!! It requires a good investment of time and effort with a tinge of “Thinking outside the Box”.
Arjun
Learning new technologies every day and upgrading yourself.
Anita Gujju
People: Working with/for someone who feels testing is “Validating Requirement”
Process: Creating and the following process over testing
We are sure that you too must have faced one or other Testing challenges which had made you think deeply on the situation. Do write down your similar experience in the comment box below.
When we say Tools and Technologies we often forget techniques. For any Software Tester techniques should be the primary concern as it deals with the approach we apply to test something. ‘Technical Tester’, this word is often used in Software Testing but the meaning is taken as technological tester i.e. one who knows about technologies (Internet, Web servers, Databases, etc). Whereas Technical tester term is more about the skills and crafts required for testing, for example, designing tests, approach to exploratory testing, etc.
When we turned to our community as what do they have to say about bare minimum tools and technologies a QA should posses we received wonderful responses from Testers having varied experiences.
We thought of compiling the comments and sharing it outside the group so that our Testing fraternity is benefitted with content.
The tester has to have at least an elementary programming knowledge with a fundamental understanding of how software is built and run. If you haven’t learned to program, start small and learn continuously.
Below are the things which I think a Technical Tester should be doing(List is what I could think of while I wrote. There can be surely more).
Will you guys mind adding more to this list or suggesting if something should be removed?
Here it is (in no particular order):
Knows Different types of Testing. Knowing those at the core I mean and not just being limited to one tool. Remember, if the use case/understanding is clear, one objective may be achieved using many tools.
Understands the architecture of his/her application
By architecture I mean, what all technologies are used to form the complete application.
What exactly each of those is doing.
In what way they are connected to each other.
How do they communicate?
When a business user initiates a request, how the entire request-response flow works.
Understands the logs, or at least tries to understand. There are several ways like Google the exception or error, past experience, asking a developer and remember, making logical guess while reading and cross-checking with Dev if your understanding was correct.
Questions himself/herself why a particular issue is occurring while using all the logs available(front end, backend, web server logs, DB logs) whenever possible before routing to Dev. Same can be done in parallel if urgency demands.
Requests RCA for the bugs logged. Asks questions till the time it is clear
Explicitly asks for Impact area of the Bug fix/new feature
Requests overview of how particular bug was fixed
Requests overview of how the new feature is getting developed. Helps Dev to further assess the impact area, a better approach, etc.
May not be an expert coder but if situation demands can code. More the better here.
Always thinks of how to automate basic routine stuff. Something as simple as Build deployment or Executing Automation suite.
Thinks of innovative approaches to test and still follows a set process.
Does research about the new technology/jar/upgrade being taken and looks for information on open issues. Also on its compatibility with remaining Tech stack.
Understands the value of automation, and decides what to automate and makes sure it is being automated right.
If not fluent, decent with Database queries and is ready to learn on demand. Remember knowing everything is best but knowing basics/nothing and being ready to research as needed is ‘human’.
Probably repeating, but an understanding of different types of Testing. For example, Security Testing. It’s ok if you cannot hack or find critical Vulnerabilities. But at least test for basic flaws like other customer data in export, URL tampering, open admin pages, easy guess passwords, XSS wherever you can, etc.
Knows how to use browser developer toolbar for different purposes like checking response, request, response time, 404 errors, etc.
Testers should be full stack Tester. This term ‘Full stack QA’ was later beautifully elaborated on another community discussion by Mahesh and Ravisurya, posting their excerpts as it is
A lot more technical, not just a bit. The more, the better, as elaborated below:
Monitoring production logs especially after deployments has benefits of its own. And if the tester does it regularly then there is a lot they can discover through those logs.
If as a tester, you are not yet doing production deployments then I suggest you to start doing it and make sure to check production logs (or logs on other environments for that matter). If for some reason, you do not own deployments then try to spend at least one short session for monitoring your application’s production logs, every day. That’s what I mean by “Monitoring session”.
Monitoring sessions can also help you identify technical bugs, errors or warnings, which might not be directly affecting the end user but still warrant attention and fixing. It’s hard to identify such issues in regular functional testing which usually has a big scope of its own.
As a tester one should gather as much as knowledge possible for whatever one is working upon. There isn’t any minimum technical or programming concept one should learn. Rather it should be let’s learn and explore as much as possible.
Just as technical understanding would help the tester understand the product a little more from a developer perspective, the knowledge of management skills would help them make use of proper time estimation techniques, RTM, criticality matrix and even create it accurately if needed.
There’s a need for every tester to have the holistic approach – TechFuncMan (technical, functional and managerial)
TestAway was a long dreamed event for the Testing Community. It came out in a wonderful fashion and the experience was one of a kind. We asked Geosley Andrades (Associate Engineering Manager at Cornerstone OnDemand) to share his experience of TestAway and he very gladly accepted it. Below are his experiences in his words hope you all will love it.
The Dream
It all started with a casual discussion over the snacks post The Test Tribe meeting. Few tribals including me were discussing how cool it would be to plan an outing for the Test Tribe Members.
The day was not far. I realized “Dreams do become reality” when this one of a kind flagship event of “TestAway” was announced as a part of The Test Tribe one-year celebrations with the community reaching around 1500 members in such a short span. The destination of the TestAway was Goa, I would have never imagined I would go someday in Goa for learning.
The Self-Realization
This was an invite-only program where only selected 15 passionate testers were to be invited post screening of their profile. Filling the application form, I was so excited that this was happening and wished I could be selected to witness and be part of such an exclusive event.
I did have double thoughts when I came to know it was not for free and we had to shell out from our pockets. Seeing the amazing lineup of topics and activities of TestAway helped me erase the concerns of money over the only chance to rediscover myself as a tester.
Finally, the names of the attendees were out. I felt happy to be on the list. I thanked God for this very chance and took an oath to make the most of this opportunity.
TestAway came in a nice way and at the right time to me. The beauty of community, learning and networking with the elite group of testers was what I always wished to have.
Day One – Bring it On
Thursday, 7th March 2019 – The day had finally arrived. Set with all the packing, I caught my flight to Goa – the land of beaches, sun, cool breeze and coconut trees.
Waited for fellow attendees to join me at Dabolim Airport and the fire lit instantly. In no time we were discussing Testing over some quick bites. That’s when I realized I am here for serious learning.
Sandeep Garg the Master of Note making, Rahul Singh the Gamer Boy, Arokya Samy the entrepreneur, Sharath Kumaraswamy the Aerospace Drone Guy, Arjun BM the Micro-Community Builder joined me on the journey to our Test Away destination “Ziva Villa” by Villa De Goa a private luxury villa in the Candolim, North Goa.
The Test Away Flag flew high on top of our villa and I knew our organizer’s Mahesh Chikane, Founder The Test Tribe and Niraj Yadav, Event Manager for TestAway had made sure all arrangements were in place before our arrival.
As soon as rest of the testers reached the venue, introductory conversations erupted. We felt like one family, one team there on a common mission to create an impact in the testing world. Ajay Balamurugadas, Wizard of Testing took center stage in leading the war cry – How is the Josh? So loud was the “Josh” I am sure must have reached 3 villas far away 😛
Collecting our swags, we freshened and headed for lunch. Resetting ourselves we jumped on to our first interesting activity “Gamifying Testing”. It was an interesting game based on the principle of minute observation and test of memory.
Though the rules were pretty simple but it demanded a great deal of team coordination, observation skills and an excellent strategy. Our strategy was basically assigning 4 quadrants of the UI to 4 individuals and one person would focus on the center and link these 4 quadrants. Not sure if this was the best strategy but my team did manage to eventually win this game.
This was followed by another interesting game wherein we had to guess which Product or Company a person might be thinking by asking only five specific questions. This was difficult where none of the teams were able to crack out completely. But we surely enjoyed every bit of it and improved on asking intelligent questions round after round to eventually crack the strategy.
After this amazing fun activity we sat down for a Tester’s Roundtable where we discussed on the “State of Testing – What wrong we have done and how we can Improve”. The roundup was concluded with pain areas identified and solution on how to overcome them.
Roundtable discussions
Now, this didn’t end here. We were introduced to a superb strategy game called the “Mafia” – modeling a conflict between two groups – the mafia and the villager. At the start of the game, each player is secretly assigned a role affiliated with one of these teams. The game has two alternating phases: one, during which the mafia may covertly “murder” a villager, and two, in which surviving players debate the identities of the mafia and vote to eliminate a suspect.
The game continues until all the mafia have been eliminated or until the mafia outnumbers the villagers. So addicted where we to this game that this has lived in our hearts even after TestAway. We did pledge to play this game sometime when we meet again.
Day Two – I want More
Friday, 8th March 2019 – With all excitement we kicked off our day with Aqua Zumba. Disha Reddy was fabulous in making us move our hips in the Swimming pool. It was nice fun to have all the guys splash and jump in the pool for couple of hours.
Aqua Zumba
After a yummy breakfast, we went on to attend a workshop on “How to Test anything faster and better” by our testing Guru Ajay. Ajay enlightened us on techniques of how to set the right strategy and mission. Tips on how to make your brain an idea generator and a thinker rather than a storage device.
He encouraged us to get out of our comfort zone, do things differently, take every opportunity as it comes. He ended his session with a beautiful quote saying, “Testing is a goal for life, is a way of life”.
a
Breathe Testing. Enjoy Testing. Life is Short.
WorkshopBomb defusal game
Ajay also introduced us to two great games. First one was a bomb defuse game – “Keep Talking and Nobody Explodes” – This game task a player with disarming procedurally generated bombs with the assistance of other players who help another team with the bomb instruction manual. Winning this game requires the presence of mind, excellent communication and team work.
Second, Ultimate tic-tac-toe a board game composed of nine tic-tac-toe boards arranged in a 3-by-3 grid. Players take turns playing in the smaller tic-tac-toe boards until one of them wins in the larger tic-tac-toe board. Compared to the traditional tic-tac-toe, strategy required in this game is conceptually more difficult and challenging.
We then went to play War of Cards with a superbly crafted deck of Test Sphere that gets testers thinking and talking about their testing. Testers brainstorm, coach, share knowledge and experiences on the concepts mentioned on a card randomly pulled out. The Team which gives the best explanation wins.
Siquerim beach walk
After Tea, we headed straight to the Coco and Sinquerim beach to enjoy the cool breeze, waves and sand. A walk I will cherish all my life making our bond of friendship even stronger. With a bunch of crazy clicks and our war cry shout, we headed back to our villa.
Post dinner, we continued to play our favorite “Mafia” game and later on testers utilized the rest of the evening for 1:1 mentoring and discussing great Testing ideas.
Sinquerim beach
Day 3 – Just Can’t Get Enough
Saturday, 9th March 2019 – All charged for a bright new day we headed to Chapora Fort also called as the “Dil Chahta Hai” Fort on our bikes. Riding through the lanes of Goa, passing by colorful vintage Goani houses it was all nostalgiac stuff. We sat down and just soaked in the view and place for an hour before returning safe and sound to our villa.
Today we had another workshop on Storytelling (Less Talk more exercise again by Ajay). We discussed on how to write effective testing stories and open our mind to think of NLQ –NEXT LOGICAL QUESTION and be ready with the answers for it.
Another workshop was on “Design Thinking” by Sandeep where he threw light on the solution based approach of solving problems. His insights gave a new meaning on tackling complex problems by understanding human needs, reframing the problem in human centric ways, brainstorming, prototyping and testing.
Each one of us then went on to present their own Audience curated story. Which resulted in coining Manjunath Batti as the “This Guy”, Savita Patil narrating a fairy tale love story and Trina Acharya stunned with the outcome of it all.
Sharing your story
Evening was time to be merry. We headed for candle light dinner to Mama Cecelia’s Beach Café – a shack on the Candolim Beach front and had good laughs over lighter talks and jokes that evening. Sharath stole the evening that day with his standup comedy. We all just couldn’t stop laughing. The day ended with our ritual a game of “Mafia”.
Dinner by the shack
Day 4 – Saying Goodbyes are Hard
Sunday, 10th March 2019 – After a nice breakfast. We wrapped up the TestAway Learning Experience with Mahesh and Niraj gifting us certificates and memento to take home with us.
I literally felt nostalgic writing the final testimonial and deep within my heart wished to have the next TestAway soon. As I complete this I will miss those conversations, the fun, the learning, the Mafia which Priyabrata Das, tried to capture in his photography. Silent Girl Anita Gujrati was no more silent, the spark of knowledge had ignited not just her but us all. I certainly admit “These were the best days of my Life”
Thats me
We are sure you must have loved Geosley’s experience of TestAway. Please feel free to share your feedback, suggestions, queries in the comment box below or shoot an Email on contact@thetesttribe.com
Sharing some of the amazing testimonials that we received from TestAway attendees.
First I want to say Thank You to the organisers for inviting me to this wonderful event.
Before coming here I was filled/my mind was filled with lot of questions. What is Tester career, where is testers career path, what to do get something in my testing path. I got answers for all of these and my mind is now relaxed now.
Savita Patil
TestAway is an awesome experience where you will love and enjoy lots of Testing related things.
Manjunath Batti
TestAway organized by TTT was one of kind from and for the Testing Community. It was an excellent learning platform and helped in unlearning many things which were not good practices.
Kudos to Mahesh and Niraj for organizing it perfectly. Ajay’s and Sandeep’s workshop were amazing and it opened new avenues and perspectives for me. I will look forward for more such events in the future 🙂
Continuing the tradition Mansi being one of our Meetup attendees shares her experience. Here she goes –
23 September 2018! FIRST EVER NCR TESTING MEETUP!! What a day it was!!
The first ever testing meetup held at 91 Springboard Okhala New Delhi. We received a tremendous response from testers, developers and young aspirants of the IT Sector. And the event turned out to be houseful.
The meetup was divided into two sessions.
First session was taken by Mr. Ankit Giri, who is working as a Training and development head at Enciphers. He briefed the Tribe about security testing and his experience on Bug Bounty. He also threw some light on Burp suite, a tool which is being used extensively for security testing.
The session went on for 45 minutes and ended with the question and answer session. The entire gathering heard him with rapt attention on the technical terms.
The second session was taken by Mr. Karundeep Gill, a veteran in the IT industry. He shared his experience with the gathering and explained the Agile process involved in STLC at length. The session lasted for about 30 minutes.
Both the sessions were followed by a quick tea and snacks. Participants used the breaks to interact with fellow attendees and the whole room was buzzing with murmurs 🙂 We were happy to see people coming and discussing, after all, this is how the community should be.
The meetup ended with thanks to all. All people left the venue with a bright smile and hoping to meet soon.
Few snaps from the event. Do spread and share with your friends and do not forget to join The Test Tribe Facebook group.
It would not be wrong to assert that Software Testers meets maximum stereotypes in Software fraternity. And it’s not only other guys stereotyping Testers, in fact, many times they themselves tag the label. But the matter of fact is that a bulk of stereotypes are greatly generalized and stands without a base.
We asked people from across the Technology sector to share what they think about Stereotypes Software Testers face in their professional sphere or something they themselves have faced. We received wonderful responses and here we are collating them.
Let’s have a look at the most common stereotype a Software Tester faces
1. Developer to another Developer: Testers won’t understand this, they are not technical people.
This is one of the greatest stereotypes of the 21st century. It is imperative for any Functional Tester to understand the underlying technology in order to do a comprehensive testing. Not all the developers are technical and not all the Testers are non-technical.
2. Every Manual Tester wants to be an Automation Tester.
Though its a matter of opportunity still those who have tried out both know how difficult it is working as a Functional Tester and how boring it can be scripting Regression Test Cases and troubleshooting failed Automation Cases.
3. QA Manager: My job is to prepare dashboard, status reports and share those.
This comes from both the sides, Managers, and Testers.
Some wannabe Test Managers stereotype the Manager role. Planning out strategy and helping the team with whatever the situation requires is also Managers responsibility. Testers feel their Manager just forwards the Email and does nothing.
4. QA Manager: Testing doesn’t take more than 1/10 of development effort, why is your estimation more than Developers
Really. There isn’t any hardcoded fact. What if the Product is extending its support to a new browser. In such a case development efforts are negligible but QA has to perform and extensive testing.
5. A Recruiter: Don’t you think your notice period of 60 days is more, testers have a lesser notice period
No comments 😀
6. Developer to a Tester: Your job is the easy bro, log bugs and then leave for the home on Friday, spoiling our weekends ?
7. In managerial meet: In any case, Dev freshers would not like to report to a QA manager ?
8. Senior Management to a QA Manager: This guy doesn’t look complete fit for the Development role, please see if you can utilize him in Testing. Testing to kar hi lega(He should be able to do Testing though). 😐
9. Senior Management: What are we waiting for? Automate everything 😀
Automation is trending, isn’t it?
10. Senior Manager to QA team: Why do you people always raise a critical bug at the end?
No excuses but a stitch in time saves time 😛
11. Don’t go near the QA cubicle, they will throw a new bug on your neck 😀
12. Developers to Testers: You people always think Negative
Of course not, haven’t you seen the Test Suite? Positive cases are a lot more than negative scenarios 😛
Do comment if you loved the post. And do not forget to share the stereotype that you have faced in your professional experience and especially how did you handle it.
Disclaimer: We have tried our best to keep the comments from the contributors as original as possible.
Special Thanks to the contributors of this post (Shrinivas Kulkarni, Abhaychandra Chede, Aditya Prabhu, Arokya Swamy, Mahesh Chikane, Shreya Khillare)
On the eve of the celebration of first 500 members of The Test Tribe Facebook group, an involuntary initiative took the shape of a varied and formed a rich list of crowd-sourced software testing tips.
Software Testers from various backgrounds, domain and technologies poured their bit which was later cherry-picked and curated to form a list of 138 crowdsourced software testing tips. The tips are listed along with their author with a view that it surely will help fellow Software Testers in some form or other.
Big Thank You to all the Contributors. So here we go.
Ajay Balamurugadas
Be aware of what tests you perform on the application
Revise the basics time and again
Talk to stakeholders. Understand what is important for each stakeholder
Question your assumptions. Question the team’s assumptions
Understand time zones and check the time zone wherever your application references ‘time’
Know how to use Test Obsessed’s Test Heuristics Cheat sheet Test Heuristics Cheat Sheet Data Type Attacks & Web Tests
Arokya Samy
Before starting the testing, write your test ideas in bullet points
Try to use a simulator for multiple browsers, multiple versions
Think of below points when considering Mobile security
1. Device Logs
2. Out of Memory
3. Network Leakages
4. Traffic Interception & Tampering
5. Disassemble the package or mount file
6. Binary Protection
7. Intra & Inter-app Communication
8. Root / Jailbreak your device
9. SQLite data storage
Subscribe testing magazines like women tester, testing magazine etc
Keep a mobile toolkit for mobile testing like how mechanics will have. The kit can have more than one device, USB cables, SIM cards, data cards, sim holder, joysticks, an external hard disk with all the essential software
Follow as many as testers in the Twitter
Try to attend bug bounty program
Install developer version of mobile OS like Android and iOS and contribute your bugs
Read about Android Material design, color theory, Apple cheat sheets, Android iconography, etc
Keep yourself updated about the new features of the Android and iOS. Watch World Wide Developers Conference and Google I/O
Use Genymotion, Android SDK, xCode, Microsoft Visual Studia Emulator and BlackBerry Emulator for the Virtual Devices
Explain your bug Clearly in the Bug Description. Like what is happening? where is happening? Why is it Happening?
The developer should understand our bug in the description itself, if not with the help of screenshots.. if not with Steps to Replicate etc
Try to replicate the Customers Issues. So that we can get more knowledge on the product. if possible take previous customer tickets, and try to analyze it.
Read the following software Testing books
1. Lessons learned in Software Testing
2. Testing Computer Software
3. Beautiful Testing.
4. How to break software
5. How Google Test Sofware
6. Hands-On Mobile App Testing (My Favourite One)
7. Software Testing in the Real World
8. The Art of Software Testing
9. Software Testing Learn in 1 Day
10. A friendly Introduction to Software Testing
Do not hesitate to ask questions of anyone and at the same time do not show ego in answering to any of the questions from anyone.
Below is the list of software which can be considered to take screenshots
Mobile Testing- Download Crash File( Android) and plist file (iOS) and analyze the reasons and root causes for the Crash.
Learn about ADB commands and shell command for the mobile testing
Learn about how trigger pseudo calls and pseudo messages by using ADB commands in the android testing
Spend time on the android manifest for Android security testing
If you test android app, ask iOS user to test and get the feedback and do the vice versa
Explore Android SDK as much as possible
Use Burp suite for intercepting the request with mobile apps
Learn about different error codes
Try to use the computer without a mouse. Use it with keyboard shortcuts
Use IPCU to analyze console logs of iOS apps
Abhaychandra Chede
While reporting application crash bug/ game crash bug, do attach the crash log.
Check the UI on different screen sizes.
Designing for all the varying screen sizes — especially in the Android market is a big challenge. The app has to perform consistently with all of them. If the user sees a screen with elements that don’t align or worse, bleed off the page there’s a good chance they will uninstall the app immediately. For this reason, you need to map all the models the app will support and test the app in each screen size on each device. If two different models have the same screen size, it’s not necessary to test the UI in both devices. For example: If the app supports both the iPhone 5 and iPhone 5s, a test of only one of them should suffice.
Test for the brute-force attack wherever possible.
Check for host header injection. Just change the host: value and check whether it’s redirected to the host or not.
Session ID Prediction- Many web applications manage authentication by using session identifiers (session IDs). Therefore, if session ID generation is predictable, a malicious user could be able to find a valid session ID and gain unauthorized access to the application, impersonating a previously authenticated user.
Check for CSRF related issues.
Check for DDOS attack
Verify that restricted page should not be accessible by the user after session timeout.
Verify that Error Message does not contain malicious information so that hacker will use this information to hack website.
Keep an eye on how fast the app is draining Battery while doing Mobile Application Testing
Mahesh Chikane
Ask yourself if you are performing the important(as per your context) tests first.
Consider discussing your tests/test strategy with fellow tester/developer in your team. Brainstorming brings awesome results.
Ask your Dev about Root Cause of the defect he just fixed.
Ask your Dev if there is any impacted area(to be regressed) for the defect he just fixed.
Are you communicating constructively? Remember that it matters a lot in our Job.
Practice the skill of Note Taking. It helps almost all the time to a Tester.
Staying aware all the time is a skill. Practice that. Eg. You want to complete a flow from step 1 to step n. That’s your end goal, but you should still notice the spelling mistake in an overlay message which was there just for a second.
Study and practice Storytelling.
Keep developer tools(console) open while you test and keep an eye on script(js) errors if any.
You are able to add a record. Great. But how much time it took? Keep an eye on response time.
Catching UI glitches? Great. But are your noticing UI inconsistencies as well?
Eg. In/on same form/module/page
Name*: Age * : Not ok.
Browser Developer Tools: Get familiar with the Network tab. Helps a lot to see what requests are going and what response you are getting even when nothing is reflected on UI due to possible error.
Browser Developer Tools: Try out Browser compatibility modes in IE. Not 100% same as the actual browser but comes very handy when you need to test on different versions of IE when you actually have just one.
Do view page source(right click on the page or through developer toolbox) once in a while. See if any information revealed which ideally should not be revealed.
Try URL tampering.
Login. View doc. Copy URL. Logout. Hit the copied URL. You should be redirected to the login page again.
XSS: Try simple script in all the text boxes you see. After that try submit/edit/view. It’s fun. If it executes, that’s a problem. alert(“hello”)
XSS: See a parameter being passed in the URL of the particular page? Try some basic script there and load the page again. alert(“hello”)
Security: Have an open sign up page but no captcha/recaptcha implemented? Suggest having so asap to your product owner.
Use the spellcheck plugin. One click and you get any/all spelling errors on the page.
Be a part of at least one testing community. Hustling together will open up way too many learning and growth opportunities
Consider testing your web app on different screen resolutions/sizes.
Ahmed Khan
Be aware of the environment in which the application is tested. A defect should be accompanied by the environment details and evidence. This makes the defect clear to understand and reduces to and fro of Developer and Tester.
Anita Gujju
Ask people from another department to evaluate the product or feature the product under test. It will certainly bring unnoticed review comments.
Deepan Kumar
Look deep into Services and Database layer while testing
Never ever tell the identified bug orally to developers unless the project process states to do so. It’s better to be formal in communicating the defects via Email or logging it into the Defect tracking tool.
Dipak Kumar Das
While testing a web application try to switch user agent by using User Agent Switcher
Ganesh Gupta
Review plays an important role in Testing, let the seniors review your testing at least once. So that we get to know some missing cases if it’s available. In this way, we also learn the perspective of senior/other Tester on the given task.
Always share the new things with teammates & introduce the better way of testing if we learn any good thing.
If junior/senior or any teammate missed anything while testing then avoid doing or saying anything which may demotivate him/her. Just handle the things in a proper way. Do make him/her understand the impact of missing on the project. It will help him/her to improve their skills & make them responsible for their own work.
If you are in a good network or community then try to involve your teammates as well in this it will help everyone
Always respect the suggestions of every member of the team. And finally, decide on the things which are good for everyone.
Do review our own test cases at least once in 2 weeks (mostly in free time)
Monkey testing is also important sometimes mostly for the e-commerce/ games kind of apps. (As The person who doesn’t know more about the product give some better ideas & bugs)
Don’t test anything in pressure even if the timelines are closed. Do ask regarding the timelines and take a proper time for testing and do it properly. Else end user will face problems and company repo affect due to that. Give go ahead of your project when you are satisfied. That improves the quality of the product & our testing skills.
Try to do testing on real devices & if it’s not available then take help of simulator/emulators.
Geosley Anrades
Make sure you have a solid understanding of requirements before starting the test. No Business Requirement. No wiki article. Boils to No RTM. No effective testing. Ask Product Owners, Dev to ensure one is created.
Hamza Bhamla
Tests cases are to improve the software efficiency, not to demoralize the developers. Be constructive while defect discussion and not defensive.
Brainstorm the Test cases written. 100 minds lead to 100 different ideas.
Communication is the key. Persuasive communication can take one tester far ahead than planned.
Connect with other teams in the project as well. Such as Support Team, Dev Team, Delivery Team. This networking helps you get to keep yourself abreast about their process flow which can of use when fixing on timelines, deliverable dates etc.
Test to improve not impress
Jits Motabhai Pamnani
Provide all relevant information in the bug. As much as that dev shouldn’t be feeling the need to put the bug in need more info state. And hence save the overall turn around time.
May it be browser details or a scrolling screenshot, or in case If steps are little complicated, attach a bug reproducing video.
Make sure to document your results, not just keep it to yourself, but keep it always published in Confluence. And that way the next iterations of the report would be easily comparable with previous data accessible and available.
Kunjal Mehta
Don’t be afraid to reject story/build/release in case basic validation fails or the software is very buggy. A stitch in time saves nine. It’s better to get the issues fixed early rather than fixing when the client reports them
Lucky Jain
Start testing with a positive mindset. Ensure that the happy flow path is covered first and then focus on the negative scenarios. It may happen that to break the software we spend too much time focussing on negative plots and later on face time crunch to cover the functional cases
Niraj Yadav
Test like a child, test like a techie, test like a tech ignorant, test like dog thumping his nails on screen, test like the laziest, test like a hyperactive
Don’t forget to add a buffer in overall estimation
A bottom-up approach where estimation flows from engineer to the manager is found to be better
Shout out at the slightest feel of estimation going wrong
Estimations are just estimations they are bound to change. Keep the plan B ready
Pratik Sidam
See that HttpOnly and secure flags are put to use in making the cookies more secure. Read more about the topic here Protecting Your Cookies: HttpOnly
Use check my links chrome extension to identify broken links
Priti Visaji
Create test cases against bugs logged (if missing) and add them into your test suite
Keep overlapping sessions with your teammates after a sprint ends, so that fellow colleagues are aware of the features you tested and the entire team is updated with latest features in the application
Do not test the application with a single global role user, always use a different set of users having specific roles
Example in the e-learning domain. Teacher & student Role
In procurement, Requester & buyer Role
Pay special attention to API Testing. Its important in the world of integration, to understand the connections between systems, databases, and networks to find out the flaws
Nishant Gohel
Analyse the requirements and try to get in touch with the client with a view of understanding their expectation from the QA team. It happens that sometimes the client expects out of the box scenarios and extensive testing from the QA team. It is always recommended at least to get the scenarios reviewed by the client or project coordinator.
Rohit Mishra
Try to test the web application on maximum version of each browser. You can make use of Cross Browser testing tools
Look at UI from a layman user perspective. Ultimately it won’t be that only engineers using the application rather people who may not be that used to technology using it.
Sandeep Garg
Continue Building a strong foundation of integrity, courage and honesty. Continue shaping your career on that foundation by working smart and hard on your testing skills
Shreya Khillare
Try to understand the logs as well before showing it to devs
Understand the severity and priority of every bug. Not every bug can be critical or marked as high
Communication with fellow testers to avoid duplicacy in bugs
Note down the eta required for resolving any kind of blocker or critical. As time is also an important constraint.
Shubham Karun
Peer review always adds value to your testing effort, don’t forget it!
Testing seems to be more easier when you have an idea of how’s the architecture working for your feature at backend…
Practicing well planned and well-designed flow of your testing effort is what makes you a better tester in long run
Questioning always helps you build a clear picture of how your testing approach for a feature should be like…
Steffy Thomas
Keep a track of customer issues and ensure that the same is not faced in upcoming releases
Log every bug that you find in the application, especially not reproducible ones with proper documentation
Trina Acharya
In a situation of time crunch, test the riskiest and important modules first based on complexity and frequency of use by the end user
Create your test design always keeping the end user in mind. The geographical distribution, the browser and/or device usage, etc
If anything changes in the requirements down the line, ensure that the changes are mapped on all levels of STLC as well.
Yogesh Badgujar
Do a regular analysis of problems to trace the bottleneck in the overall process. Its recommended making use of a Pareto chart or fishbone diagram as they help in narrowing down the root cause of problems. Read more with an example Fishbone diagram and Pareto principle
We wish not to stop with 138 tips but keep the list growing. Do share your tips by writing it down in the comment box below.
Disclaimer: Testing tips listed above are completely crowdsourced. Opinions expressed/vocab used are/is their own. The Test Tribe team has just made negligible formatting alterations in the original content.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.
