Author: Tribal Bot

Founder Tribal- The Test Tribe
My Experience at Cignithon Testing Hackathon

Cignithon Testing Hackathon, A mega testing hackathon in India was organized by Cigniti Technologies on 9th Feb 2020 at T-Hub (IIIT Hyderabad) and was powered by The Test Tribe Community. It was a rocking start to the New year for the testing community, especially from Hyderabad’s point of view. A sleepy, cozy, overcast Sunday was not sufficient to dampen the spirits of the Hyderabad Testing community, which came forward to constitute one of the biggest testing hackathons of India. More than 118+ testers from 52+ different companies turned up for the event which was fun-filled and challenging at the same time with opportunities for making cash, friends and a reputation. 

Some key highlights of Cignithon Testing Hackathon:

  • 3 Products to test from varying domains and on different platforms
    • Oropocket – A universal Investment platform wherein you can invest in precious metals
    • Hisab – An online Accounting Application
    • Younify – A social network to connect students across University campuses
  • Prizes worth 2 lakhs up for grab
  • Opportunity to network with 118+ testing professionals
  • Potential hiring opportunity with one of the leading pure-play testing companies in the world Cigniti
  • 1600+ bugs found ( A mind-boggling number by any standards)
  • Testers from 52+ companies participated
  • 9 winning teams across 3 products
  • 3 miscellaneous awards
  • Lots of fun, networking, SWAG, and smiles. All around.

The day started at 11:30 AM with the T-Hub auditorium completely jam-packed. An enthusiastic lot of testers, TTT volunteers and Cigniti leadership were geared towards making this event a great success. Paras, our host for the day, wove his magic and was the thread that held the entire event together. Cigniti leadership led by Subhendu and especially Raghuram set the ball rolling. Raghuram’s enthralling rendition of the history of software in the Indian context and especially the part on software testing captivated the audience as it is always good to know how the career you are a part of came into existence. 

As a precursor to the actual bug hunting, Mahesh walked us all through the Event format, followed by a brief overview of the products provided by the three Startups I mentioned above.

The teams of two were allowed to be formed and asked to give some unique name to it. Teams were told to determine their strategies as to how to go ahead with their bug -hunting activities. Ajay provided his valuable inputs on how to go ahead with the bug-hunting activities with the intent of winning the hackathon. Then the teams took a break for lunch (which was quite delicious) where there were umpteen opportunities to network and form teams if not already done. 

The actual bug hunting exercise then started at 2:15 PM. The teams were all set. The product URLs, instructions and good luck wishes were shared with the teams, and the actual hackathon began. Teams deployed multiple strategies to outwit the competition and put their best feet forward to claim the prizes. Strategies ranged from picking up a single application to picking all applications with a time-boxed approach, going through the instructions in detail or directly jumping into testing. So on and so forth.

The apps were from varying domains with a mix of platforms(Web/Mobile) and that enabled people with different skillsets and experiences to leverage their strengths. Teams with a varying mix of experiences definitely had a stronger chance of winning. 

The time flew by and soon the ending was near. Teams rushed in to scour through any untouched areas and logging bugs in a hurry. The battle continued for a good 3.5 hours. Testers were not ready to stop. No time to look at the clock. Fingers waving their magic as fast as they can on the keyboard, logging as many bugs as possible. There were tea and snacks to enjoy in between the testing duration, but were we ready to stop and enjoy it? No, all we wanted is to log as many good bugs as possible.

Like all good things has to end, the hackathon window got over and bug submissions were stopped. We all were tired but super happy. Who says you can’t feel adrenaline rush while you test? 

There was a breather finally and we all were actually relaxing for the first time after a good 3.5 hours of intense work. This was also a very good opportunity to network with other testers out there and learn from them.

A whopping 1600+ bugs were logged in the process by 118+ testers in a matter of few hours. If you are in the Software world, you know how huge is that number.

The sheer number of bugs meant evaluating was a huge challenge for the product teams and this meant needing more time for the same. Hoe to engage the team. In stepped Paras and then there were a few sets of fun events to enable people to collect swag and goodies. Ample games to network with others out there of course.

When the final results were to be announced there was excitement all around. Some of the teams were extremely confident of winning while some were skeptical. However, the confidence or lack of it was not the deciding factor but the efforts spent and the quality of bugs raised that differentiated the winners from the rest.

Finally, the results were out:

Oropocket

  • Winner: Team Bug Eaters (Pottumurty Manikant & Sandeep Jinde from Qapitol QA)
  • 1st Runner up: TribeTesters (Ashwin Chordiya from HCL & Saurabh from ZenQA)
  • 2nd runner up: SomethingFishy (Vaibhav P & Shaik Rahman)

Hisab

  • Winner: Amigos (Rohit Anney & Laxminarayana Boga from CBRE)
  • 1st Runner up: Da Vinci (Arun Nandireddi & Vishal Vala from EPAM Systems)
  • 2nd Runner up: Phinox (Rajesh Nemani from Cigniti & Suneetha Garlapati from First Tech Consulting)

Younify

  • Winner: Automatons (Sandeep Uppala from Ebix Software & Satheesh Valluri from EMIDS)
  • 1st Runner up: Team Autobot (Nadimpalli Babu & Venkatesh Salagrama from Sureify Labs)
  • 2nd Runner up: anOnymOus (K.V. Yoganand from Innominds Software & Surya Krishna from VMax E-Solutions)

A big congratulations to all the Winners. However, anyone and everyone who turned up was a Winner as they chose to spend the Sunday in a worthy manner as compared to the lazing or other umpteen ways they could have. The success of this event would not only stoke the fire of passion that burns in the Hyderabad testing community with respect to their trade of testing but would also act as an encouragement for the thousands of other testers who were not able to take part but may take heart from this and chose to participate in future events to keep the flag of testing flying high.

Cignithon Testing Hackathon

Meanwhile, a lot of testers also shared their feedback for the event and about the things they are looking forward to from The Test Tribe. Tribals also agreed that there has to be a way to stay in touch with each other and there it was, official The Test Tribe Facebook Community. If you are a Tester and reading this, Join the Tribe NOW- http://bit.ly/tttcommunity


About the Author:

Ravi has 12+ years of experience in software testing with expertise in test automation. He has worked for Infosys, TCS, Expleo Group and currently working as a Test Consultant at Microsoft. He is a keen and avid learner and on the lookout for learning new skills primarily related to technology.

Linkedin: https://www.linkedin.com/in/ravishankar1985/

00
5 Tips to win your next Software Testing Hackathon

My first Software Testing Hackathon (or Bugathon, or Testathon) was way back in 2009–10 and it was known as Zappers and conducted by TCL. My team won the first one and We were thrilled. The next one we lost, and we again won and this continued with many other Software Testing Hackathons. I won most of them and lost a few on the way. Winning gave the money and losing taught me the most. I also wrote a book called 50+ tips to win testing contests. 

As someone who has participated and won many Software Testing Hackathons, I want to share five actionable tips to help you win your next time you participate in a Testing Hackathon.

Tip 1: Keep your Weapons ready

For testing a product, one needs good test ideas, good devices, and tools. I have seen many testers come to the hackathon with laptops that always need to be plugged in for a charge, mobile phones with low battery, no cables to transfer data and the highlight of all, only 1% come with their own internet dongles or WiFi hotspots. I mean why would you take that risk? Why would you want to rely on venue Wi-Fi which will anyways be shared by 100s of participants? 

Here is my checklist for a hackathon:

    1. My laptop — I know which keys work and which don’t. There are no surprises.
    2. My mobile devices — I exactly know the device settings and the bugs on my phone. I know the speed at which things happen on my phone and I know the passwords for all the accounts on this phone.
    3. Chargers for both laptops and mobile phones
    4. Spare power banks (fully charged)
    5. Pen drives
    6. Internet dongles
    7. Test data — Accounts, images, files of varying sizes and formats

Tip 2: Practice Probable Bugs Exercise

Tell me a feature or element and I would give you a list of what can go wrong. I call it the probable bugs list. I consciously practice it when there is no need for it. What can go wrong with Pagination, what can go wrong with Search results, what can go wrong with file upload, I already have a list in my mind. No wonder the list of 400 common software bugs by Dr. Cem Kaner was an inspiration. You can access the PDF here. Go through the pdf and have a mind full of probable bugs for the next testing session/hackathon.

Tip 3: Practice filing bugs

I find it strange when testers take their own sweet time to file bugs in a hackathon. Especially when you are also judged for the duplicates. The one who files the bug early gets the credit. The focus is not on the details but just enough details and move on to the next bug. There are testers who write ten steps for a simple bug. They don’t attach screenshots or videos. Even if they attach, the video is of a few MBs in size and takes forever to get uploaded on the slow network. Amazingly, the tester is watching the upload progress and not focusing on filing the next bug. Some testers are not even aware of the tools other than the default ones available with the OS. Also, what if your favorite tool failed? One should have 2–3 tools for each category (screenshot, test data generation, note-taking, file converters and so on.

Tip 4: Focus on your Strengths

Hackathons are not for trying out new techniques or quality criteria unless you are fine losing the top prizes at stake. Each one of us is good at specific quality criteria and should dive deep in that during the hackathon. Also, know the tools that can give you an overview of the quality criteria you are not an expert at. W3C checklists, GTMetrix, Quixxi, WAVE are some of the tools for Compliance, Performance, Security, Accessibility respectively. 

Tip 5: Know your speed and Never Give Up

If you have practiced enough times, you would know how much time you would take to know an application, how much time it takes to upload a screenshot and how many minutes would you take to complete a bug report. Without knowing your current speed, you would not know if 20 bugs are enough or 40 bugs is a good performance. Practice so much that you can file a bug within 30–45 seconds and you can find a new bug every 60 seconds of testing. This would ensure that you can easily file 30–40 bugs every hour and you can easily touch 60 bugs in two hours. It is a decent number considering that many participants are first-timers and might not even cross 30 bugs. Having such a steep target also forces you to think of diverse ideas and attack the same application in multiple ways. 

Bonus: Do not waste time discussing bugs with your partner. Find it? Log it.

You may also want to read my free ebook — 50+ Tips to Win Testing Contests

Hope these tips were useful. See you in the next hackathon!

Join The Test Tribe Community here to stay updated with future Testing Hackathons amongst other events.


About the Author

The Test Tribe Testing Community

Ajay Balamurugadas
A graduate of Problem Solving Leadership, BBST Courses by AST, Rapid Software Testing, Rapid Testing Intensive workshop, Lean Software Testing Workshop, Ajay doesn’t hesitate to spend on his learning. Starting his career as a software tester, he continues to be a hands-on software tester along with training new testers, meeting testers in person, presenting at conferences, conducting workshops, and sharing his thoughts via blog and tweets.

00
TestAway Shimla- From Attendee Perspective

“This is an amazing, amazing, amazing experience!”, exclaimed Subham as Mahesh trained the camera at him. Mahesh was live streaming the experiences of the participant testers of TestAway Shimla on Facebook as the fifteen of us strolled from the playground, back to The White Haven in Shimla.

Although poor Subham was targeted for his antics on live camera and earned himself the nickname “Amazing Subham”, what he said reflected the thoughts of everyone at the end of the event.

I recently moved back to India from Australia, where I learned the value addition that networking, and community activities provide to professionals and how it helps them get better in their job and in life. I was on the lookout for opportunities to meet with the Software Testing community in India. I found The Test Tribe and took a look at their website. It was just what I was looking for. I visited their Upcoming Events page and saw that they had a workshop on Usability Testing and TestAway.

I got curious and explored further. A cursory glance was enough for me to decide that I need to be part of this. Gamifying Testing, Workshops, Unlearn to Learn, Reset – all the right words to tick off my interest. Long story short, I applied, Mahesh called to interview, and after a short while, said I was in. I managed to put all logistics together and was soon on a flight to get to the event!

I have attempted to pen down the proceedings of the event by retrieving whatever my memory could store, adding my personal takeaway and experience. I tried to group experiences to the best of my creative ability with no one sub-topic having more importance than the others. They can be read in any order. If this attempt doesn’t appeal to you, it is because of my inability to tell a story effectively and you shouldn’t undermine the effort gone into setting up the various aspects of the event, the contributions of the participants, and the impact the event had on all of us.

 

The White Haven, the chefs and the food

TestAway Shimla

A little away from the city, in a quaint neighbourhood of Shimla, stood The White Haven. Typical of many Hill Station properties, you climb down the stairs to get to the different parts of the property.

Our hosts were wonderful. I remember the name of one person I met – Ajay Thakur. The chef and his assistants who helped us were down to earth and agile. Without their support, active participation throughout three days by all participants would have been a challenge. It’s rude on my part to not mention their names here, but I have forgotten them. I could ask someone and write but I won’t, so that I remember names in future. A big Shukriya to them!

The chefs dished out rotis, sabjis made from a range of greens, selection of meats, and dal, parathas, omelette, and toast. To complement all this was a yummy pickle, dahi, salads and fruits! We loved the food so much that a majority of us didn’t want to experiment eating anywhere else on the last day when there was an opportunity to do so.

The Tribe Leaders, Introductions and the Welcome Kit

When I first spoke to Mahesh, I got the impression that this guy is doing something meaningful. In his WhatsApp DP, where he holds a mike and is talking, I could see a spark in his eyes. However, until after dinner on the first day at Shimla, I didn’t understand the full extent of this man’s passion to help testers in whatever possible way he can. Throughout the event, if there was one person keeping an eye on the clock and the schedule and keeping us on our toes, it was him. In every game and activity he orchestrated, I could see the love he has for testing and testers.

There is a saying in Kannada – Thumbida Koda Thulukola (very loosely translated, it means pots which are full don’t wobble or jump about). This is every bit true about Niraj Yadav and I didn’t realize this until we spoke, when we sat next to each other on our way back to Delhi. The number of topics about which this man could converse with ease amazed me. During the event, he went about his job of ensuring that all the logistics for each activity were in place so quietly, that you almost wouldn’t take notice of him.

Add to this, these two guys went a day ahead to setup and gave us a warm welcome! They handed us a Welcome Kit (co-sponsored by Moolya), that comprised of a surprise t-shirt and a water sipper among other things. The sipper idea was come up with, based on feedback from TestAway Goa to reduce the use of bottled water.

I had been following Ajay and his work for a while now. I met him at one of his workshops just a week before the event. He commands a focused attention in his blogs and when talking testing, but is a very humorous person. I thoroughly enjoyed every bit of his jokes, puns and comments!

Tribesmen

One of the participants – Jitendra, has accurately described each participant in his article here, and that makes my job easy. He has modestly excluded himself from the list. He is an enterprising professional who understood the value he adds to organisations early in his career and has broken away from the shackles of the corporate structure.


In my opinion, the group was as diverse as it could get. The testers were of different levels of experience, from very different domains, and organisations of different sizes catering to different segments of the market. Most importantly, the group was fun!

After the first few hours on Day 1, most of us felt we knew each other well, although, by then most of us had bonded in groups of twos and threes. The rest was History!

Mahesh’s Games

Each of the games that the team had designed helped drive home a point for testers. From observing an image (a web page in reality) for three seconds, and attempting to reproduce it, to guessing a mobile app’s name by asking five questions to using the Ministry of Testing’s TestSphere card deck, to diffusing time bomb emulators, to understanding Visual Auditory Kinesthetics (VAK) learning styles by putting first thoughts about a word down as a drawing, each game helped testers understand that observation, questioning, note taking, collaboration, modeling, strategising etc. are some vital skills they need to learn and improve upon continuously.

Ultimate Tic Tac Toe and Mafia during after hours helped us to connect and have fun.

Ajay’s advice to Testers – Online Portfolio 101

TestAway Shimla

How many testers do you know? How many testers know you? How many testers do you know outside of work and outside of your social circle (predominantly engineering friends)? How many testers do you know in your city, country and in the World? How many testers do you know, with who you can randomly strike a conversation about Testing? How many people will reach out to you when they want answers to questions in Software Testing? Are you reputed enough to be head-hunted? What reputation and credibility have you built? What does a search engine return when you are looked up?

These are few of the questions that Ajay asked the group at the beginning of the session. He went on to explain the need for individuals to have a portfolio of their work. For Testers, use of mediums like a blog, videos, GitHub, etc. can be used to publish learnings and ideas. A Github account with sample of work for various aspects of Testing can be setup so that interested people can understand the work of publisher better. I knew I had to let people know that I exist, but the question “How many testers do you know, with whom you can randomly start a conversation about Testing?”, has hit me hard!

The Workshops
Liberating Structures

Getting people to work well together is one of the biggest challenges today, across the world. Organisations of all sizes and shapes consider this as one of their top challenges. To foster a culture of inclusion and engagement, to motivate teams to work together and to generate ideas from unexpected sources, organisations need to demonstrate to their employees that this is possible (rephrased from the liberating structures website). Liberating Structures is one way to do this.

Ajay used 3 of the 33 structures to demonstrate how ideas get generated quickly for any problem statement. The problem statements were interesting enough to keep the participants involved. ‘How would you increase your company’s revenue by 15%?’ ‘If you had unlimited resources, what would you do to improve your testing skills?’


The Liberating Structures we used were 1-2-4-All and 15% Solutions. With the 1-2-4-All microstructure, individuals first come up with a set of ideas, and then group themselves into twos and compare and improve the ideas. Two groups of twos then come together to further improvise. This way at each step two sets of ideas are studied and improved. Eventually this will lead to a possible solution that has the ideas of the entire group. Although, it is easier said than done, it is possible to generate quite a few ideas within a short time. This is exactly what happened.

The 15% Solutions is structured very similarly to 1-2-4-All. However, here at each step the group votes to identify 15% of all the ideas that they generated as the best ones. Again, within a short time a lot of people’s thoughts are collected and the group decides which of them would work.

There is a lot to know about Liberating Structures. For the purpose of this event, the idea was to get people familiar with the concept.

The Testing Lab

3 Teams of 4 Testers, 3 advisors – 1 for each team, Slack’s Notification feature, 3 charts and sketch pens to write a test report, 3 hours to Test with deadlines for interacting and getting information from Stakeholders, brainstorming test ideas and getting feedback, testing and documenting, and finally writing a report. 

How did the teams fare? Below average. Not enough questions were asked to the stakeholder, which means the mission of the project was not understood. Not enough time was spent to make the test report meaningful. The teams didn’t think of who their customers’ customers were, thereby not understanding the context of where, when, why and how the testing needs to be structured.

Jitendra’s story to freedom

Like I said earlier, Jitendra understood the value he was adding to organizations early in his career, and in turn what he was losing by continuing to work for them. He decided to do something about it. It was not easy, and it usually never is, but it takes a lot of grit to experiment and make this decision. He still has challenges, but is taking them one at a time, head-on.

Ulhas’ free money advice

Ulhas is Jitendra’s partner in crime and between them, they had exciting stories to tell which stem from the bond that has nurtured their relationship. Ulhas’ USP is his way of managing his personal finances and how that has helped him partner with Jitendra to help solve interesting testing problems. Of course, here too there are challenges which the two of them are solving very wisely.

Lightning Talks – Ashwin and Pranav

Ashwin briefly spoke about using matrices to map automated checks to tests and features. He went on to explain how this helped him deal with Root Cause Analysis and communicate effectively to his management when a bug  escaped to production.

 

Pranav is a young, energetic and an eager tester. He was intimidated by the the experience around him and the rest of us by his questions. He courageously spoke when asked to, about Message Queues, their uses in a Microservices architecture and how they are effective in propagating changes between the client and the server in an asynchronous manner. 


Pranav is learning to play the flute and is discovering his learning styles and the challenges of learning to play a musical instrument. With a little prodding from Ajay, he was able to quickly try a few tunes and I realized that while practice is important, it is also important to try different things while practicing.

Ashutosh, NPV and Automation

The value of Rs. 100/- today is a certain amount lesser one year from now and we all know it. What I didn’t know is that a variant of this is used in project management during feasibility study to decide if a project makes sense or not. i.e., if we start a project based on current costs, will it have provided the ROI, by the time it matures?

Ashutosh told us that a mind boggling number of factors go into trying to make these projections. Now, Ashutosh has cleverly attempted to use this to project the value of investing in Automation projects. This is a work in progress and he has attempted to create a basic framework to establish the $ value of writing an Automated (or a Computer-assisted) Test.

TestAway Shimla

As an extension, this can be applied to everything we do in life.

Group Discussions – As One big group

Staying relevant as a tester

If you don’t adapt, you become irrelevant. However, in India, the problem is still a few steps behind. People don’t realize that they need to adapt, at least a portion of the techies. So, when Mahesh asked the group as to what he could do to help Testers in India adapt with changing times, there were a few ideas – which I can’t recollect much of. However, a few of us were of the opinion that even though there were several people extending their hand out to help, there are very few takers (including me, until a year ago). The good news is, this is changing. However, there is a lot of work to do and The Test Tribe is saying and doing the right things to take this forward. I am sure there are many smaller groups who are attempting something similar. These ideas will gain momentum and soon there will be several initiatives like The Test Tribe!

TestAway Shimla

RPA

Ganesh helped the team get their brains around what exactly RPA is. Robotic Process Automation is being used to automate several business processes. There was a little bit of a debate that ensued. Is it like Selenium? Is it going to automate what a “Manual” Tester does? Is it building Computer-assisted tests without writing code! We concluded that no matter what the capabilities of this technology is, it won’t make the Human Tester extinct.

Heuristics

If there is one concept used popularly by several testers today that seems very simple to understand, it is Heuristics. Simply put,

Heuristic is a fallible way of learning something about an application. – as defined by renowned testers. Very simple, isn’t it? Now take a look at this.

Ajay did a wonderful job of explaining what it is in the thirty minutes that we spoke about it. In my opinion, it will take several months of testing, reading, writing, listening to and speaking with multiple renowned testers to get a good grasp of what Heuristics in Software Testing is and how to effectively use it.

Bonfire

TestAway Shimla

Amazing Subham set the tone for the evening by singing. Ajay followed it up with a spoof version of a popular Bollywood song. Ajay then put a question “Who is <person’s name>?” 

As the group sat in a circle and started answering the question, I asked myself the same question. I kept floating between thinking about what my answer should be and listening to other’s answers. The answers were fun, intense, revealed stories of courage and determination and of happiness and sorrow. Most of us are constantly looking for an answer to this question. I have realized that the answers keep changing as we grow and mature and yet can never be complete. As we learn, explore and interact with more and more people over the years, the answers will change rapidly and probably will settle down at some point.

Jugal then entertained us by reading a Marathi poem he had written. He also shared how The Test Tribe helped him find a new job, not directly, but as a result of being an active part of the community.

Playground and Yoga

Niraj had us stretch our legs a little bit by taking the team to a playground in the morning on two days. I made it just on the 2nd day. To avoid the risk of injuring myself, which I am prone to, I stat in a corner while the guys threw a tennis ball around and even played lagori. On the 3rd day, I believe Niraj introduced people to the basics of pranayama, asana and meditation.

Group Discussions – Two’s, Three’s etc.

 

Ajay, Geosley and I traveled together from Chandigarh to Shimla. Geosley and Ajay reminicised the events of TestAway Goa. I got a little more insight into what the event is about. We also shared each others’ stories.

Subham, Shubham and I had interesting discussions after sessions and exchanged thoughts and ideas. We spoke about automation, challenges of testers in terms of stakeholder communication, companies’ belief that 100% automation is achievable, that a Green looking automation dashboard doesn’t prove that there are no bugs etc.

Pranav and I had an intense discussion around Testing, Data Science, going back to college for a masters degree, getting an MBA, music and learning to learn.

Ulhas and I spoke about AppAchhi and the kind of performance metrics it captures for mobile applications.

Ajay and I discussed about Python and the challenges of breaking away from being a “student” programmer.

Mahesh and I discussed how to get better at Testing and ways in which I could give back to the Tribe.

Niraj and I spoke about work, interests, running, yoga, religion, politics, ancient systems, climate change, economics and a few more. I am still amazed at how Niraj spoke with ease about each of these topics.

My memory can recall just these conversations, but I do remember conversing with each of the rest about their skills, experience and of course Testing!

The Mall Road, Apples and Chaat

After all the learning (which in itself was a lot of fun), it was time to have some fun and explore Shimla. The Mall Road houses several heritage sites that offered a rustic backdrop for group pictures. With night falling by the time we got there, the photos came out to be mystic.

TestAway Shimla

Chaat and Rasmalai at a 120 year old halwai were delicious and so were the Apples. There was plenty of shopping opportunities as well!

Key Takeaways, Commitments, Testimonials, and Celebration

In my opinion, the best thing about TestAway is the format. With most day workshops and corporate trainings, the format is usually 9 AM to 5 PM. Since humans are very fallible, by the time everyone is involved in the event, significant time is lost. Further, as the end nears, people start getting restless, as they need to think about their families, dinner plans etc. Even though a lot of smart people take away a lot from these workshops, at an event like TestAway where people are closeted in one place for three full days, the scope for learning increases. We didn’t spend more time than in a day workshop, but the fact that we didn’t have anywhere else to get to allowed us to be relaxed and involve ourselves entirely in the events of the day.

My key takeaway from the event was a lot of inspiration and motivation to experiment with all aspects of life. I am committed to bringing about changes in the way I look at everything about Testing.  

At the end of the event Mahesh requested us to write our testimonials. We attempted to explore our creative side for doing this and a glimpse of it can been seen in the photo.

TestAway Shimla

We also celebrated the end of an awesome three days!

In Summary

I want to thank Mahesh, Niraj, Ajay and the team behind TestAway Shimla for orchestrating this event in such a fluid manner. I want to thank each participant of TestAway Shimla for their time, sharing their thoughts, knowledge and experience. I want to thank Pradeep, Dhanasekar and Chandini from Moolya for allowing me to take leave soon after I joined them, to be part of this event.

TestAway Shimla

To sum up the experience of TestAway Shimla, I would shout “High!” in response to someone asking me “How’s the josh?”. TestAway stood true to the Tag Line coLive. coLearn. coGrow. 🙂

Regards from Author,

 

 

 

 

 

Chidambaram Ganesan

Proud TestAway Tribal

Test Manager’s Dream Team – In a Buzzing Bees’ Way

In the current age, acquiring new technical skills are emphasised more and more. Although, it is key for career development, on a hindsight tester’s behavioural/soft skills are given lesser priority. Eventually, behavioural trait tends to last through individual career compared to short-lived ever-changing technical skills. Any test manager would aspire to have the dream test team from day one, which is very unlikely for many practical reasons. Said that there are opportunities that the test manager can adopt to make any team into a dream team.

Bees are my favourites due to their surviving instinct & discipline. In analogues to bees’ qualities within their colony, sharing my experience and suggestion to build a good quality test team. These skills are very much essential for a diversely skilled test team (i.e., if you’re managing a team which has both functional and non-functional team or different skilled test team)

Call out: Following suggestions are not only limited to test manager, test lead or tester but very much applicable to other workstreams as well. Examples considered are more testing team focus. Feel free apply the context with your workstream.    

Bee a Hive – One Team

A bee colony in peak season can house even up to 50,000 bees that work cohesively within a small confined space. In return, bees win are maximised to achieve the common goal of survival. Bees will put their life in line to defend the colony and such scarifies is possible ONLY because of their sense of belonging within the hive. 

In the tech world, fortunately, there is no need for such sacrifice. Instead, it is important for each member to be part of a team – ONE TEAM. Having a team with such a spirit makes you a winner already. The test manager should give more importance to coach ‘One Team’ ethos and monitor its health. 

Why does it make the difference?

Once an individual has the belonging to a team, team goals are prioritised over the individual. 

Few suggestions, which favoured me

  1. Instigating the belief that ‘When a team win everyone wins’ to the funny contrary to ‘Operation success but the patient died’. Supporting nature will become involuntary when realisation kick-in to help each other for all to win
  2. Inculcate the common or customer ways of working within the team as it gives clarity for everyone. Quick Tip: Remember, that each members’ ways of working could have been different from their previous experience 
  3. Organising team building activity can show the great result of inclusiveness within the team

Team Character Profile 

  • Test Manager: Must have
  • Test Lead: Must have
  • Tester: Must have

Bee Positive – Positive Spirit 

During winter, a bee colony can dwell from 50,000 bees to 20,000 that is beyond 50% loss. Still, a healthy colony stays strong and phoenix back during spring. Bees’ resistance to negative influence keeps them moving forward for their survival. 

Software development is a very complex activity with many moving parts performed by different people. Chances are very high to bump into frequent hurdles and harm the team spirit by temporary failures. Having a positive team or a member is a gold mine for a test manager. Even a few positive souls can be infectious to a team in a very good way and inspire many to follow.   

Why does it make a difference?

Positive messaging provides hope to team and assurance to stakeholder. In addition, being positive will help a long way beyond work 

Few suggestions, which favoured me

  1. Start with few key influencers within the team (esp. test lead or sr. tester) and lead them with examples while noticing any negative messaging

Just to help you understand the positive message impact. Let us perform a quick experiment. 

Imagine yourself in either of these roles (tester, developer, project manager) attending a daily stand up meeting and hearing following a voice from a tester. Which of the below voice would make you feel positive?

Voice 1: I am blocked, Cannot proceed with testing due to the data dependency. Dev team is responsible for the data. This will delay the test timelines 

Voice 2: Shall work with the dev team and need their help to resolve the data dependency. Shall assess the impact and come back, if any

Both the voice conveys the same message but voice 2 makes anyone feel positive. Try this within your team and share your experience in the comment. 

  1. During daily stand-up, pick a person and ask their positive experience that happened in the last 24 hrs and do not restrict this with work. You will be amazed to hear teams experience. Keep this rotational within the team by not stressing an individual. Come on! This should not create a nightmare for an individual 😉
  2. Assign the team to share positive quotes/story as a mailer to the team – this can be rotational activity between team members to ensure each gets an opportunity

Team Character Profile 

  • Test Manager: Must have
  • Test Lead: Must have
  • Tester: Good to have

Bee Explorer 

Honeybees are known to travel up to 13.5 km in search of nectar. While this is very instinct nature within the bee’s community, the same resides down for humans to post their learning life.

By Explorer – I mean the hunger for learning. Technology is changing at a faster rate than many skills has a shorter lifetime. A tester should always look out for the latest industry trend put in use within their project. Skill development is a lifelong activity and does not have an end state. The test manager should a play key role to encourage this quality within the team 

Why does it make the difference?

Few explorers can bring in the ‘Out-of-box’ thinking within a team. There could be many benefit potential such as process improvement, better testing techniques, right area of coverage, faster ways of testing etc. 

Few suggestions, which favoured me

  1. The test manager should push & guide the right member to explore

Sharing one of my best experience:

During SIT & UAT test activity, there was an opportunity to automate the input data from the various system. Automation tester did a fabulous job of using trail version UFT tool to meet the objectives. As a test manager, wanted to provide this as value to the business postproduction. However, the current implementation was not feasible due to the incurring cost of the tool. Initially, tester resisted any viable option. However, after some pushback & guidance, a bespoke option was developed which not only meet the business requirement but also was much efficient than the previous solution.  

  1. Have a monthly/bi-weekly learning session where a team member can present a topic across the team – This can be planned on a rotational basis

Team Character Profile 

  • Test Manager: Identify and Guide the team
  • Test Lead: Good to have
  • Tester: Few in the team 

Bee Proactive & Solver

If the bees’ environment becomes undesirable, they are efficient in identifying the issue and finds a better setting to relocate. Such adaptability has made them survive for more than ~40 million years on earth. Fact tip: human are known to be from ~2 – 6 million years

Being proactive is an essential quality for Test manager, Test lead. Sensing a risk and creating a controlling measure saves the project than responding after it happens. Problem solvers are another hot skill that goes in tandem from the problem identifying skills. The solving capability tends to evolve through experience. However, by careful awareness and observation within the project, this is not a difficult skill to acquire.

Quick Evaluation Tips

Following metrics can help to self-evaluate by analysing the test related RAID log 

  • Which is higher? Number of risk vs issues raised by the test team

Note: Risks are the challenges within the project before it happens. Issue are the challenges within the project after it happens. 

    • If your ISSUE count is more than RISK. Then, you must perform more homework to identify risk
    • If your RISK count is more than ISSUE. Then, you have started well. However, hold on! The sheer raising of risk is not sufficient.  Let us move to the next metric 
  • How many risks have got converted into issue vs risk mitigated without impact

This metric helps to evaluate the quality of handling the identified risk.  

    • If the ratio of risk conversion to an issue is more. Then, concentrate more on risk mitigation skills 
    • If the ratio of risk mitigated without impact is more. Then, Congratulations! You are doing a fabulous job and keep up the good work. 

At the same time, do not give a hard time for you if the risks are beyond your control line. Give the best shot to work with other workstreams to resolve and if you still could not close due to external factors, then do not worry.

You deserve to be proud of your efforts and log it with leadership as a lesson learnt for a wider project team. 

Why does it make the difference?

Remember, Good test manager not only highlights the challenges but resolves the same as well 

Few suggestions, which favoured me

  1. Firstly, schedule a knowledge session around RAID management. Highlight the need and its importance to the team. Guide them through the RAID template. Please do not assume that everyone within the team knows. The answer is NO. There is a high possibility that template & approach followed in their previous experience could be very different from your expectation. This will, in fact, make the problem worse between your expectation and team assumption on RAID
  2. Having a weekly RAID log update is good practice. At the same time, empower the team to update the same in Adhoc basis. Quick Tip: It is of NO use to raise risk, issue and keeping silent. A person who raises the risk should make the action owner aware of the same  

Team Character Profile 

  • Test Manager: Must have
  • Test Lead: Must have
  • Tester: Good to have

BONUS TIP

The test manager should make the best effort to identify & recognise those individuals who go beyond his/her call of duty. The sense of appreciation will encourage others within the team to inculcate as well.  As a leader, you might need to set an example by helping the team wherever possible. 

Hope you found this article useful. All the very best. 

Do comment your thoughts and feedback about this post.


Author of this amazing post

Sugandh has 10+years of rich cross-sector & cross-regional experience in software testing. Currently, he is working in the UK for the last 5+ years and specialize in Test management with retail domain expertise.

Blessed with varied experience in delivering small to large scale transformational program covering both legacies to the next-generation cloud solution. He has managed a multi-skilled team in both functional and non-functional testing across the different delivery model.

Sugandhraj Balasubramanian

00
Burp Suite Demonstration

In this round up post, Gaurav Narawani gives us a glimpse on the Burp Suite.

When a request is sent from a browser, it goes through a series of steps before it comes back to the browser.

Burp suite can be used to modify the request being sent and capture the response received.

Also one can analyze the requests coming from the server.

Sounds interesting? Do check out the video below:

https://www.youtube.com/watch?v=ZP4tT1x5ERI&t=828s

About Tools and Testers:

Tools and Testers is an initiative by The Test Tribe to give testers a glimpse of the tools that are of help in carrying out testing activities, not necessarily in the likes of automation tools.

On this thought, its helps burst the myth that ‘”Manual Testers” do not use any tools, as we believe – Tools doesn’t mean only Selenium, Eclipse and JMeter rather all software which helps us in our task.

This is more of a knowledge sharing with the fellow tribes.

AMA session with James Bach on “All things Software Testing”

Hello Tribe,

Here is the recording of our third session from the AMA series we started wherein we have James Bach answering questions on “All things Software Testing”.

Know more about James here-

LinkedIn: https://www.linkedin.com/in/james-bach-6188a811

Blog: http://www.satisfice.com

Twitter: https://twitter.com/jamesmarcusbach

It was a Zoom Live session and as promised we are making it available to everyone.

 

 

Bonus: We also have a couple of Mindmaps which at a high level covers up learnings shared by James. Thanks to Sandeep Garg for taking notes and creating wonderful deliverables.

Click on image to see it full screen. 

Before you start watching the video, you may want to have a look at few(but not all) of the questions which James Bach answered during the AMA:

  • With the growing popularity of the open source tools, do you foresee the adoption of paid software tools dying?
  • Where should the future tester focus to master the open source tools or paid tools?
  • Will testing survive without automation in the near future?
  • As testers, how can we give still better products to the world? Are we doing enough? Or should we do more? What else should be done?
  • How to cope up with automation testing and security testing challenges and internet of things testing?
  • What would be your approach to scheduler based testing?
  • How is that Facebook and Google are getting away with programmer centric testing, all driven from unit test, with the tolerance of bugs gone big throwing lights on risk is not that big.
  • Tester into manual testing wants suggestions to move into automation testing with no or minimal coding
  • What should be the tester’s focus in the beginning of his career for a long-term success in the testing career?
  • What should a tester posses – multiple types of testing, working around all of them or just one and sticking to it.
  • Would love to know about your journey, how you overcame the testing mess in your earlier days
  • If not getting enough opportunities in India for a particular skill, what needs to be done?
  • There are situations when we are not valued as a quality team or a tester. Nothing can be done about it, but do just what is asked. What is your advice to handle such situations?
  • Who are the influencers in your professional career?
  • It is said that testers can become good product managers. What is your take on it?
  • What is the most demanding technology in Software Testing?
  • What do you call a designs patterns thinking?
  • What are your thoughts on the way estimations are asked in testing?
  • How to be prepared for the release of cycles that happens in few hours?
  • Tell us more about the Rapid Software Testing Methodology
  • Lots of testers are negative when it comes to upgrading their skills. What would you tell them?

Regards,

The Test Tribe Team

00
138 Crowdsourced Software Testing Tips

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 crowdsourced 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 the other.

Big Thank You to all the Contributors. So here we go.

Ajay Balamurugadas

  1. Be aware of what tests you perform on the application
  2. Revise the basics time and again
  3. Talk to stakeholders. Understand what is important for each stakeholder
  4. Question your assumptions. Question the team’s assumptions
  5. Have Backups
  6. Think Cost vs Value vs Risk
  7. If you can think well, you can test well
  8. Serve the stakeholders. Don’t be the gatekeeper. Read Testers: Get out of the Quality Assurance Business by Michael Bolton
  9. Have your own testing syllabus and follow it
  10. Tools I wish I had known about when I started coding: Revisited
  11. Don’t miss this treasure http://www.huibschoots.nl/wordpress/?page_id=441
  12. Check if someone has already solved the problem for you. Find out if you can solve it in a better way. Understand the importance of context
  13. Work as a team. Any target that looks impossible becomes possible with a good team
  14. Understand different domains
  15. Learn how to learn
  16. Understand the standards set by industry – W3C, Human Interface Guidelines (HIG) by Apple
  17. Learn shortcuts of the applications, tools you use
  18. Talk to other testers. Talk to programmers. See how they perceive testing
  19. Learn to communicate well. Learn to engage in a healthy discussion
  20. Don’t pay a lot of attention to numbers alone. They don’t tell you the complete story. Accompany numbers with stories that matter.
  21. Don’t just think about your customer. Think about your customer’s customer also
  22. Automation enthusiasts: this is for you: 50+ resources for test automation engineers
  23. If you are stuck, try different heuristics. Testing Mnemonics – Desktop Download
  24. 36 Days of Web Testing
  25. Understand personas based testing
  26. Understand time zones and check the time zone wherever your application references ‘time’
  27. Know how to use Test Obsessed’s Test Heuristics Cheat sheet Test Heuristics Cheat Sheet Data Type Attacks & Web Tests

Arokya Samy

  1. Before starting the testing, write your test ideas in bullet points
  2. Try to use a simulator for multiple browsers, multiple versions

Think of below points when considering Mobile security:

  • Device Logs
  • Out of Memory
  • Network Leakages
  • Traffic Interception & Tampering
  • Disassemble the package or mount file
  • Binary Protection
  • Intra & Inter-app Communication
  • Root / Jailbreak your devices
  • SQLite data storage
  1. Subscribe testing magazines like women tester, testing magazine etc
  2. 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
  3. Follow as many as testers in the Twitter
  4. Try to attend bug bounty program
  5. Install developer version of mobile OS like Android and iOS and contribute your bugs
  6. Read about Android Material design, color theory, Apple cheat sheets, Android iconography, etc
  7. Keep yourself updated about the new features of the Android and iOS. Watch World Wide Developers Conference and Google I/O
  8. Use Genymotion, Android SDK, xCode, Microsoft Visual Studia Emulator and BlackBerry Emulator for the Virtual Devices
  9. 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
  10. 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.
  11. Read the following software Testing books
  • Lessons learned in Software Testing
  • Testing Computer Software
  • Beautiful Testing.
  • How to break software
  • How Google Test Software
  • Hands-On Mobile App Testing (My Favourite One)
  • Software Testing in the Real World
  • The Art of Software Testing
  • Software Testing Learn in 1 Day
  • A friendly Introduction to Software Testing
  1. 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.
  2. Below is the list of software which can be considered to take screenshots
  • Snipping Tool
  • GreenShot
  • ShareX
  • Grab
  • Jing
  • LightShot
  • PicPick
  • FastZone
  • Monosnap
  • Gyazo
  • PrintKey
  • Shotty
  1. Mobile Testing- Download Crash File( Android) and plist file (iOS) and analyze the reasons and root causes for the Crash.
  2. Learn about ADB commands and shell command for the mobile testing
  3. Learn about how trigger pseudo calls and pseudo messages by using ADB commands in the android testing
  4. Spend time on the android manifest for Android security testing
  5. If you test android app, ask iOS user to test and get the feedback and do the vice versa
  6. Explore Android SDK as much as possible
  7. Use Burp suite for intercepting the request with mobile apps
  8. Learn about different error codes
  9. Try to use the computer without a mouse. Use it with keyboard shortcuts
  10. Use IPCU to analyze console logs of iOS apps

Abhaychandra Chede

  1. While reporting application crash bug/ game crash bug, do attach the crash log.
  2. Check the UI on different screen sizes.
  3. 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.
  4. Test for the brute-force attack wherever possible.
  5. Check for host header injection. Just change the host: value and check whether it’s redirected to the host or not.
  6. 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.
  7. Check for CSRF related issues.
  8. Check for DDOS attack
  9. Verify that restricted page should not be accessible by the user after session timeout.
  10. Verify that Error Message does not contain malicious information so that hacker will use this information to hack website.
  11. Keep an eye on how fast the app is draining Battery while doing Mobile Application Testing

Mahesh Chikane

  1. Ask yourself if you are performing the important(as per your context) tests first.
  2. Consider discussing your tests/test strategy with fellow tester/developer in your team. Brainstorming brings awesome results.
  3. Ask your Dev about Root Cause of the defect he just fixed.
  4. Ask your Dev if there is any impacted area(to be regressed) for the defect he just fixed.
  5. Are you communicating constructively? Remember that it matters a lot in our Job.
  6. Practice the skill of Note Taking. It helps almost all the time to a Tester.
  7. 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.
  8. Study and practice Storytelling.
  9. Keep developer tools(console) open while you test and keep an eye on script(js) errors if any.
  10. You are able to add a record. Great. But how much time it took? Keep an eye on response time.
  11. Catching UI glitches? Great. But are your noticing UI inconsistencies as well?
  12. Eg. In/on same form/module/page
  13. Name*:     Age * : Not ok.
  14. 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.
  15. 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.
  16. 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.
  17. Try URL tampering.
  18. Login. View doc. Copy URL. Logout. Hit the copied URL. You should be redirected to the login page again.
  19. 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”)
  20. 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”)
  21. Security: Have an open sign up page but no captcha/recaptcha implemented? Suggest having so asap to your product owner.
  22. Use the spell check plugin. One click and you get any/all spelling errors on the page.
  23. Be a part of at least one testing community. Hustling together will open up way too many learning and growth opportunities
  24. Consider testing your web app on different screen resolutions/sizes.

Ahmed Khan

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

  1. Ask people from another department to evaluate the product or feature the product under test. It will certainly bring unnoticed review comments.

Deepan Kumar

  1. Look deep into Services and Database layer while testing
  2. Create test ideas for UI and Usability
  3. Use browser add-ons to assist your testing. You can refer to Smart Mission Focussed Web Testing With Addons & Tools

Mohammed Ellyaz

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

  1. While testing a web application try to switch user agent by using User Agent Switcher

Ganesh Gupta

  1. 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.
  2. Always share the new things with teammates & introduce the better way of testing if we learn any good thing.
  3. 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.
  4. If you are in a good network or community then try to involve your teammates as well in this it will help everyone
  5. Always respect the suggestions of every member of the team. And finally, decide on the things which are good for everyone.
  6. Do review our own test cases at least once in 2 weeks (mostly in free time)
  7. 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)
  8. 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.
  9. Try to do testing on real devices & if it’s not available then take help of simulator/emulators.

Geosley Anrades

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

  1. Tests cases are to improve the software efficiency, not to demoralize the developers. Be constructive while defect discussion and not defensive.
  2. Brainstorm the Test cases written. 100 minds lead to 100 different ideas.
  3. Communication is the key. Persuasive communication can take one tester far ahead than planned.
  4. 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.
  5. Test to improve not impress

Jits Motabhai Pamnani

  1. 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.
  2. May it be browser details or a scrolling screenshot, or in case If steps are little complicated, attach a bug reproducing video.
  3. 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

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

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

  1. 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
  2. Don’t forget to add a buffer in overall estimation
  3. A bottom-up approach where estimation flows from engineer to the manager is found to be better
  4. Shout out at the slightest feel of estimation going wrong
  5. Estimations are just estimations they are bound to change. Keep the plan B ready

Pratik Sidam

  1. 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
  2. Use check my links chrome extension to identify broken links

Priti Visaji

  1. Create test cases against bugs logged (if missing) and add them into your test suite
  2. 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
  3. Do not test the application with a single global role user, always use a different set of users having specific roles
  4. Example in the e-learning domain. Teacher & student Role
  5. In procurement, Requester & buyer Role
  6. 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

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

  1. Try to test the web application on maximum version of each browser. You can make use of Cross Browser testing tools
  2. 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

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

  1. Try to understand the logs as well before showing it to devs
  2. Understand the severity and priority of every bug. Not every bug can be critical or marked as high
  3. Communication with fellow testers to avoid duplicacy in bugs
  4. Note down the eta required for resolving any kind of blocker or critical. As time is also an important constraint.

Shubham Karun

  1. Peer review always adds value to your testing effort, don’t forget it!
  2. Testing seems to be more easier when you have an idea of how’s the architecture working for your feature at backend…
  3. Practicing well planned and well-designed flow of your testing effort is what makes you a better tester in long run
  4. Questioning always helps you build a clear picture of how your testing approach for a feature should be like…

Steffy Thomas

  1. Keep a track of customer issues and ensure that the same is not faced in upcoming releases
  2. Log every bug that you find in the application, especially not reproducible ones with proper documentation

Trina Acharya

  1. In a situation of time crunch, test the riskiest and important modules first based on complexity and frequency of use by the end user
  2. Create your test design always keeping the end user in mind. The geographical distribution, the browser and/or device usage, etc
  3. If anything changes in the requirements down the line, ensure that the changes are mapped on all levels of STLC as well.

Yogesh Badgujar

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

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.

AMA session with Lalit Bhamare on “Changing Role of a Tester”.

Hello Tribe,

Here is the recording of our third session from the AMA series we started wherein Lalit Bhamare is answering questions on “Changing Role of a Tester”.

Know more about Lalit here- https://www.linkedin.com/in/lalitkumarbhamare/

It was a Facebook Live AMA within The Test Tribe group and as promised we are making it available to everyone.

Before you start watching the video, you may want to have a look at few(but not all) of the questions which Lalit Bhamare answered during the AMA:

  • How is the dimension of hiring testers going to change?
  • Is it a good idea for the testers to excel in all areas of testing like automation, performance etc., or be a master of one in the context of the current hiring process?
  • What is your take on various testing positions popular in the market while hiring?
  • What are the options testers can explore in dev ops field?
  • Career options available from testing and how it can be achieved?
  • If quality is not valued, bugs do not matter. What will tester do?
  • How to change your role from QA to dev ops guy considering company will consider you as a fresher?
  • Roles always keep changing, how do you think testers can stay with the change curve, what they can do and how?
  • What is the one thing that you would tell a candidate going to get hired?
  • Is it good to be an expert in any one domain?
  • What will be the scenario of the tester when artificial intelligence comes into the market?
  • What is the one thing that testers should not do?
  • Certifications, how much of value are they? are there any options other than ISTQB?

Regards,

The Test Tribe Team

AMA session with Shrinivas Kulkarni on “Test Designing”

Hello Tribe,

Here is the recording of our second session from the AMA series we started wherein Shrinivas Kulkarni is answering questions on “Test Designing”. Due to some technical challenges, we could not upload video, but here is the enhanced audio session.

It was a Facebook Live AMA within The Test Tribe group and as promised we are making it available to everyone.

 

 

Before you start watching the video, you may want to have a look at few(but not all) of the questions which Shrinivas answered during the AMA:

-What would be your take on TDD ( Test Driven Design ) vs Traditional testing? What would be the best way to incline engineers to get into this model.

-What technique would suggest for a Tester to best decide that the code is ready to be released in production?

-Could you give your take on what testers need to keep in mind while designing effective test cases?

-Test Design techniques take a certain amount of time how can tester convince or showcase management to adhere to following such techniques in fast-paced sprint delivery.

-Can you mention some tools which will help in designing test cases?

-How can we provide test cases in a smarter way?

-How do we avoid the monotony of designing tests?

-How to ensure 100% test coverage is done when designing test cases

-How do we improve our design approach over the years?

-What are the prerequisites for creating a test design?

-What should be the ratio of negative vs positive scenarios in a test design?

-What points need to keep in mind ..when we are starting the test design process?

-Views about implementing Page Object Model in Automated Selenium Tests.

-Views about implementing Page Factory with Page Object Model in Automated Selenium Tests. The cost, advantages, and pitfalls.

-How is test design done in 1. Agile 2. Devops. Some of the current companies use agile, DevOps. Please explain these concepts in depth with examples.

-I have switched to Test Cases and Test Scenarios as per the context I was in. What’s your take on deciding between writing Test Cases vs having Test Scenarios?
According to you, what context suits either?

-Considering a very short deadline in a sprint, how much effort we need to put on designing test cases, where requirements keep changing.

-How much do you recommend on test management tools?

Regards,

The Test Tribe Team

00
4th The Test Tribe Mumbai Meetup Roundup

The tradition continues and Geosley being one of our Meetup attendees shares his experience. Here he goes –


On an eventful Saturday Morning 91 Springboard Lotus our meetup venue did blossom with budding
Test Tribes Members way before the scheduled time and super excited to be part of this catch-up.
With the frequency of Mumbai meetups increasing there was a lot of confusion which 91 Springboard venue to attend. Some people did land up in the previous 91 Springboard Meetup venue
This is indeed a promising sign for Test Tribe. We all did eventually wait for our lost wanderers and
in no time the meeting room was completely houseful. Might have to think of a Bigger venue next time.
The meeting Kicked off with Mahesh, Founder of the Test Tribe talking about the vision and mission
statement for The Test Tribe.
The meeting progressed with Introductions. The twist in the story was to introduce your buddy to the entire group in just a minute of side talk. Yes, this did test our memorizing power and communication skills. There were some in the midst of all this introducing themselves instead of their buddies.
House turned into a beehive as soon as time started to listen to their neighbors. Introduction session was put live on The Test Tribe Facebook group and people just loved it. This was a nice breaker indeed.

Mahesh introducing the Tribe

Introduction session 🙂

Introduction session getting interesting 🙂

The Theme this time was diversity. First session was on “Overview and Demonstration of OWASP Top 10 Attacks” by Gaurav Narwani, who happens to be an undergraduate student and Bug bounty hunter being among the top 700 on BugCrowd. The session was super interactive with an introduction to BurpSuite, Security Testing Tools and live attack demos on hacking Labs like Web Goat. It’s just a matter of time, you might see more Bounty Hunters in the Tribe soon.

The best part was that he had recorded all the attacks earlier and played the video which made us understand the topic more clearly.

Gaurav demonstrated how SQL injection attacks can be made on poorly coded fields and how severe that can be. Using SQL injection he accessed the complete database and displayed fields of interest on the web form.

Another interesting demonstration was of XSS attack where he executed a script from the input field and created a new admin account on the demo website. Of course, this was frightening. What if such an attack is made on the software we test. It would be a blunder of course.

Glad he covered vulnerabilities and also how to avoid them.

Image may contain: 2 people
Gaurav Narwani talking about OWASP attacks

His session ended with a couple of interesting questions related to Bug Bounty and Security Testing.

We had a quick Tea and Coffee break and returned back for Geosley’s session.

Geosley’s talk was must have for all the aspiring Automation Engineers. He not only explained the importance of having a Framework but also detailed on how the Automation Framework evolved over time.

In his session, he talked about features and structure of Data-Driven framework, Keyword Driven framework, Hybrid framework, Page Object Model and BDD framework. It was a nice session to understand what kind of framework can be applied in which situation. The session concluded with the entire room raising their hands on being empowered to build one on their own soon.

Geosley showing contents of a demo Automation Framework

Post the session, the fun continued. Munching on our quick bites. We discussed on the Session Feedback, Plan for the next meet up, Feasibility of conducting a workshop and the list went on and on. We did surprise our founder by cutting a birthday cake for him which was later enjoyed by us all. A couple of group photographs with our signature TTT pose, this meetup ended with a lot of learnings, a bond of friendship and a ray of hope for the bright future of Test Tribe ahead.

We are sure you must have loved the topic and event. Join us, spread the word and share with your friends.

X