Test Chat

THE TEST CHAT
This book is dedicated to all the frontline workers

who have been working tirelessly to uphold
humanity and help everyone affected due to
COVID-19.
21Days21Tips The Test Chat 1

Foreword
Sachin Sharma:
“Integrated learning is one of the most sincere and insightful forms of spreading knowledge”
– And this was, for me, the core thought behind this Idea. We all have a lot of facts to
share as we learn innumerable things almost every time when we inhale o2 and exhale
co2. This 21Days21Tips came into picture from the passion of The Test Chat community
for developing better methods of helping people to give a platform for sharing their
precious learning and encourage them to let their thoughts shine everywhere. As the
world moves further to the digital age, it gives us the opportunity to reach maximum
minds and at the same time the challenge of how to get the best from everyone and
spread it across. This initiative is the first step towards the journey of sharing
knowledge, fostering networking and encouraging participation on global platforms like
LinkedIn, Twitter and Facebook etc. through the virtue of The Test Chat community.
In truth, we could not have achieved this amazing content without a strong support
group. The incredible enthusiasm by some extraordinary minds has made it so amazing
that we have great tips and fortunately TTC is blessed with a lot of community members
who are always ready to put efforts for any community works. I sincerely want to thank
Sahithya, Arpita, Riddhi and Shailesh for their commendable effort to consolidate all
these outstanding tips in an awesome e-book. We want to thank everyone who
supported us with love and understanding and also, we are grateful to TTC community
members each of whom has provided patient advice and guidance throughout the
21Days21Tips mission. Thank you all for your unwavering support.

Faiz Modi:
I believe that one of the best ways to learn is from Experience. Each person has a unique
experience from which others can learn. And with #21days21tips initiative, people got
the chance to share their experience and also to learn from others’ experiences. And
by that people were able to find their voice, which is one of the core ideologies behind
The Test Chat.
It was extremely delightful to see that people from The Test Chat Community
participated in the initiative very actively on the different social media platforms like
LinkedIn, Twitter, Facebook, etc. And the experience they shared in the form of tips was
very insightful and helpful for the testers. However it would have been great if such
wonderful knowledge can be shared with others as well so that it can make more
testers’ lives easier & better. That’s where Arpita, Sahithya, Shailesh and Riddhi came to
the rescue. They took up the mammoth task to collate the tips shared as part of this
initiative across the different social media platforms and converting it into this e-book.
We are really grateful and thankful for their efforts. And we are really thankful to all
who participated in the #21days21tips initiative. Last but not the least, we are thankful
to all those who have contributed and supported The Test Chat Community in one way
or another, and have made it an amazing place to learn anything related to Testing for
Testers across the world.

Adebayo Jacobs-Amoo:
All over the world, software testers are doing the same job and tasks but under different
circumstances, conditions and realities. The idea behind the #21days21tips gave us a
brilliant idea to get insights into what we do and how we should do them from all over
the world. Direct learning from peers and in this case, peers from all over the world is
always a brilliant way to learn and I am grateful for everyone who participated in the
initiative.
People often say knowledge is power, I say applied knowledge is power. The tips we got
during the initiative are learning from doing the job and also very practical so each of
us can apply those things and use them. Even more beautiful is the fact that we can
reach out to one another in “The Test Chat” community to ask more questions or seek
clarification or ask for help - this is what we do best in the TTC and we shall continue to
do.
This publication goes further to keep those tips in our memory and at our fingertips, so
we can make reference to those tips and things we learnt during the initiative. Thanks
to everyone who participated in the initiative and to all the people who worked tirelessly
to make this publication a reality.

Brijesh Deb:
In the knowledge industry, it is knowledge that is of utmost importance. What is

interesting is the way knowledge is acquired, applied and shared. In order to excel in
our careers, we look at learning things from various sources. We gain experience by
putting to practice what we have learnt. However, we get even better at it when we
share that knowledge. What’s often found wanting is an environment, a culture of
shared learning.
In order to foster the culture of sharing, The Test Chat community started an initiative
called the #21days21tips which was focused on inculcating a habit of sharing and
learning through sharing. And once the initiative started, people joined in and shared
tips that would help others get better. Tips that are practical, tips that are focused and
tips that have been tried and tested. What started as a way of sharing tips turned big
really soon with testers from all over the world participating and contributing. Doing
things differently is synonymous with The Test Chat and going by the tradition, they
came up with the novel idea of publishing the tips as an e-book. This publication is a
culmination of the thoughts, ideas and hard work of testers from around the world and
works as a ready reckoner for all the tips that have been shared as a part of this effort.
A huge thanks to everyone who contributed to the initiative and special thanks
to Sahithya, Arpita, Shailesh and Riddhi for their effort in bringing this e-book to
life.

BRIJESH DEB
Always ask questions. Don't assume anything. Question the assumptions.
DIMPY ADHIKARY
Critical thinking is very important for testers and here goes few tips to build
critical thinking:
1) Solving logical puzzles
2) Playing games
3) Writing daily journals
4) Reading books
SANJAY KUMAR
Feel the pain of repetitive tedious task, you will get the Innovative idea to
automate it!!
SHAILESH GOHEL
Being a tester, never assume anything. If you have any assumption, get is
confirmed or documented and make available to every stakeholder.
TREVOR MALGAS
When you are new to testing (or not) and want to search something related
to testing, do not make a Google search your first option.
Go into the informal forums and search for it there.

Go to the Ministry of Testing slack group or the club
Go to the test chat telegram group.
Go to the TestAutomationU slack group
Go to twitter and search for it there
Try searching for it here on LinkedIn
Go to The Test Tribe Facebook group
BALAJI SANTHANAGOPALAN
Don't hesitate to report if you have observed something strange during
testing

AHILESH MANICKAVASAGAN
Wanted to start with a great quote from Cem Kener.
'Your team may be called “quality assurance.” Don’t let that go to your head.
Your test results and bug reports provide information that facilitates the
assurance of quality on the project, but that assurance results from the effort
of the entire team. '
SUNNY BHATIA
Common misconception is that people who are not good in coding can opt
for a testing field. Just to reiterate again, testing is not a cup of tea for
everyone. Testing is just equivalent to any other profession in IT.
If you want to shine in this, One suggestion, always go beyond what is
mentioned in the duties. Think like a customer and try to use products as if
you are a consumer of that.
SOUVIK CHATTERJEE
You must have heard the phrase "Quality is the teams' responsibility". But
what does that mean?
As QA it is always a good practice to give a walkthrough of the scenarios you
have created to the entire team i.e. developers, product owner, and fellow
testers.
In this way, everyone can pitch in with their own use cases and any scenario
which is not applicable can be removed. This ensures maximum test
coverage especially the edge cases.
ANKITA JOSHI
We normally set a Path in Environment Variable screen while installing most of the things. What
happened today when I had to set up maven on my new pc...
1. I set a path and maven done
2. Again I set a new path for node js and it is done
Now when I checked mvn -version in cmd. Not working. Again I set the path for maven.
We can add all paths in a single Path Variable each separated by a semicolon; like this👇
C:\Program files\nodejs\;%MAVEN_HOME%\bin
VARADHARAJAN SRINIVASAN
RAKSHIT SANGANI
Good Work is the work we don't do. Lesser the
Learn to say NO
work, faster it is and more effective.

MUKTA SHARMA
Plan your day. Prioritise your tasks before you actually start working on
them. When you know what all different tasks you have, list them down and
assign them priority and then do it one after the other
SHIVA PRASAD B M
Tester's make mistakes, so don't beat yourself over a bug in the production
which you left, do an RCA and move on.
ARPITA SWER
First understand your product well, the high level architectural design, tech
stack used, the important business logics. Then move to requirements
analyse them parallelly playing with the product (software or hardware). At
last start the wonderful task called testing.
SONAL GOSAVI
Provide all the proper details with screenshot, logs, video for the bug. It will
be easier for developer to investigate the bug
PRASHANT HEGDE GAURAV MISHRA

SACHIN SHARMA
Work on building your credibility Ask questions even if you feel
Be active on LinkedIn
at your workplace they are stupid. Don't hesitate.
MRUGANKA
FAIZ MODI ASHUTOSH SINGH
PATWARDHAN
Learn to find root cause. Automation is not automatic
Be organized
PAVEL SAMAN
Automation is not a separate branch of testing, it's simply one tool you
have that helps you in testing, but it is not testing in itself.

SAMEER PURANDARE
Never underestimate manual testing. No tool/library is smart enough to test
everything with automation.
PRAVESH BHATT
Don't Priorities Testing type (automation or manual), the goal is delivering
quality product not the more automation cases.
AKANSHA BANSAL
Crystal clear your defects with all possible details you can talk about. If you
want to learn more than try investigating the root cause.
SANDEEP AGGARWAL
Automation execution should be unattended execution, so that we can run
it 24x7
NAVEEN P S
Don't ignore intermittent issues. Anything which is not expected from
product should be reported and discussed
SURESH DUBEY
Don't assume anything while doing testing. There is no place for
assumption in testing.
SHUBHAM KORI
MAHESH M VIVEKANAND YADAV
Don't ignore bug which seems
“Its ok to fail” Don't repeat , Automate
like feature

MITALI DHAMALE
If possible perform testing on PR(pull Requests) it helps in early testing and
feedback to the developers.
HARPREET GILL
While automating test cases the recommendation from my
experience is you should create a branch for the test case itself
to write the object repository and test scripts for that particular
test case and then commit that branch. Same way, create a new
branch for the next test case. Keep pushing the code with small
changes so that it’s easier for the reviewer also and also
prevent you from making big mistakes. So do not keep using
the same branch for each test case.
PRABIR CHAKRABORTY
Understand how the product/solution is actually used by
the end user before you even dive to test. What problem
is the product trying to solve for the user is more
important than the features/requirements of the product
someone would have documented. So always start with
‘why’ it is built and understand how users actually use the
product?
ABHINAY SARKATE PRASAD GOKHALE

SOMIL BAJPAI
Build your quality management Don't hesitate in asking what
Think out of the BOX
system. may seem obvious
SONAL GOSAVI LUKE LIU

Tester should not retest the bug till the developer Automation is the tester's assistant not the other
changes the bug status to Ready for QA. way around.

“Test tip: Take time off to just observe things over a long period. It
might look like you are not working. Don't worry. By observation,
you will learn more than just doing it all time.”
Pradeep Soundararajan

JAYAKRISHNA BELLARY NUNNA
Theoretical concepts of testing are different from practical aspects, ultimately
what you see should be working if not raise a bug. MATRIX Format Analysis is a
key for any testing, unfortunately not many update bugs or test scenarios in
Matrix which is easily readable, does not require much explanations and saves
ime.
PALLAVI RUNGTA
Make sure that the configuration of test environment is close to production
else u may get issue in production though it passed in your test
environment
ANKITA BASU
Continuous observations and analysis
Before testing we need to understand the current system behaviours and

what is expected after implementing the changes.
Sometimes we use the requirement docs as a user manual which is a not so

good approach.
We need to think from an end user's perspective and possible approaches

which can build a better quality product.
AHMED ELSHEIKH
As James Bach once said, testers must seek the underlying complexity
beneath the apparent simplicity.
KISHORE AADADA Having a mindset to break the system which we are testing in any way
SAGAR AGRAWAL
Request For Team Lead's - Always appreciate your junior for their quality bug
finding it will build their confidence.
ANHERUDH KAMATH
while performing testing, stop thinking or rather ignore the passing rate/
pass percentage. That's not for testers to be bothered about. Testers need
to break the system or application.

VINIT AGRAWAL
Business, functional and technical requirements can also be wrong, don’t
underestimate your exploratory finding, if it does not fit against the said
above, bring it on the discussion board.
RAKSHA SHETTY
Always have the discussion points written down somewhere so it is known
to all. Don’t start working if things are communicated orally.
AYAN PAUL
get those defects fixed early whose chances of occurrence is high in case
release needs to be done with known issues
PRIYESH NAIK
Always make an effort to understand the holistic picture of the overall
product/application first. That helps to test any of the features/functionality
of that product/application efficiently.
DEZUL UDANI
Don't stick to QA tools only, try learning tools used by Dev team as well so
that you get to know the smarter ways of testing as well
RITIKA GHOSH
Improve your observation skills. the more you observe the more you
understand
BADARINATH BHASKARA PETER MOORE

MAYUR GAVHANE
Always test the product from Don't be afraid to say it can't
Be Passionate Learner always
user perspective go live
SANDEEP AGGARWAL
Use the CI/CD tool and configure the automation job as downstream of
build deployment to automatically trigger it instead of triggering it
manually.

SHASHANK CHATURVEDI
While performing testing focus on follow the Testing process also. Whether
you're doing Manual or Automation testing always focus on Testing Process
ER JAGRAT GUPTA
Always put "Positive Attitude" but apply "Negative thinking" to
breakdown code during testing.
DWAIPAYAN BASU
Make sure the Test Data you use is not Dummy data but may be some
masked data from production so that the test accuracy is better.
SUDHAKAR SIVANNAGARI
Always think in the end - user perspective while writing test cases.
SHEETAL GADWAL
To document all the scenarios which were identified during exploratory
testing or comes as edge case scenarios.. which will not be slip through in the
next cycle.
APOORVA UTHRA
Never trust anyone blindly in office Anyone who pretends to be your
friend is not really your friend.
JENAB VOHRA
Positive attitude to start testing and critical thinking towards new feature or
product can be the first tip towards testing

ARPANA JINDAL
No bug is small or big, bug is a bug so never doubt just raise it.
ARUNDATHI DM
Attention to details is the most important tip and understand the exceptions
and find solutions.!!!
SHOBHIT KAUL
Don’t just start automation because "client wants it " : do proper
homework first !!

“Don’t let non-testers dictate how you go about your testing.”
James Marcus Bach

PRADEEP K C
Don't blindly start working on requirements, understand the business need
and research on it.
TEJAS AMBEKAR
Keep changing the test data for your test scenarios, sometimes data will
also find the new defects.
SAMEER POTA ANIL KUMAR AAVULA

RISHI KUMAR
Never assume anything in Tester should have curious
Understand what is testing.
testing… mindset of finding bugs
KUMAR CHANDRASHEKAR APPA

I would encourage test teams to also focus on coding standards, code
reviews, etc.,
SHEFALI JAIN
Learn to Say No !! If you think that you have valid reasons to say No to
the situations that you feel is wrong ethically or logically, do not
hesitate to put your point on the table. Do not be a robot , by saying
YES to everything that is been told to you without even thinking at your
workplace.
PRIYANKA K
Try to gather business understanding of the project/product along with the
technical side.
SHEFALI JAIN
Do not be ashamed if you do not know some technology or
PRABHU MOHAN
some language. Instead have a zeal to learn and groom yourself.
Testers should be like 'be positive Always be ready to learn from anyone who has something to
and think negative offer without any hesitation. There are lot of people around you
who are ready to teach and share their knowledge, grab the
opportunity and make good use of it

SHEELA S K
No presumptions, all assumptions and decisions should be based on
available data points.
PRANITA CHIKORDE
NAVEEN KUMAR H T ANAND JAYARAM
Test those functionalities first
Attention to details Be curious
which are error prone
SHANTALA GONAKI
Understand your domain as thoroughly as possible and keep
contemplating on best user experiences
OMKAR CHEREKAR PRASHANT HEGDE

Find a bug as early as possible. It has less cost to Work on building your credibility at your
fix workplace💪
BRIJESH DEB
Testing is never done in a silo. Always collaborate with your developers,
fellow testers, architects, business, product owner and stakeholders while
testing. Share your test ideas, build your test strategy together. Pair up with
other testers and developers and test.
RITIKA GHOSH
Learn to read error logs. Try to understand the exception and try to analyse
the occurrence of exceptions.
ANAND JAYARAM
Work closely with your devs. Get their help to set up the environment in
your local machine. If they don't have one in the local, help them build one.
This will help you test those system down scenarios, integration error
validations etc easily.

MUKTA SHARMA
As a QA, when you come across any bug while doing your testing, repeat the
scenario more than once to make sure that it is really a defect and
something is not working as it was supposed to.
SUNNY BHATIA
Never do testing or checking on developers' environment. Always perform
the task on those machines which had minimal software installed
(concerned to the product or software under test).
APOORVA UTHRA SUNIT BOSE

Research as much as you can till you find perfect “Never and I mean never try to communicate
solution for your problem formally when you are too excited or too angry.”
SHAILESH GOHEL
Always use Production/Real look like data to test any scenario instead of
"asdfg", "test city", 12345" or "lorem Ipsum". It will help to uncover many
bugs or gaps in implementation.
RIDDHI SHAH
If you have been assigned a new project/product/product module, do not
forget to document it properly which covers high level scenarios or create a
mind map and save it for future reference!
It can be life saviour for yourself and your team members, whenever needed!
DIMPY ADHIKARY
Jira is one of the best friends for testers and My personal favourites are
using keyboard shortcuts and creating a browser search engine to search
anything related to Jira quickly.
RICHARD FORJOE
A Bad 1 page cv|20 page cv VS A Great 1 page cv|20 page cv
The content is key, not the number of pages. Don’t put something you can’t
discuss in depth on your cv.

SOUVIK CHATTERJEE
Impact analysis-Whenever the BA or product owner shares the user stories
during the backlog grooming session always analyse if the new
enhancement to the system will have any impact on any of the existing
functionalities.
Raise questions on what is the business need behind this requirement and
the risks associated with it.
SHEELA S K
Use mind map tools to list out the test scenario.
XMind is one such tool available.
'Testing is an idea generation activity, rather than a plan implementation
activity.' -Bret Pettichord
TREVOR MALGAS
Don’t be afraid to ask questions. Your questions are valuable.
If you do not ask questions, you will become the one who eventually suffers
from the lack of asking them.
JYOTI MISHRA
Share with the community. It would solve two purpose
1. You will retain what you learnt
2. You might get to know more efficient way of doing same thing
NAGASRUTHI JALIGAMA
Be clear with the requirements. If you are not clear ask the questions and
proceed further like writing test cases, documentation etc.
GAURAV MISHRA
RAHUL PATIDAR
Get basics in place first before moving to higher
Speak up and show your presence
levels

“No matter where you are on your journey as a tester it’s never to
late to get on a train you have never travelled on before!”
APRAJITA MATHUR

SACHIN SHARMA
Curiosity- Having that burning desire to get ideas on anything and everything
related to testing/product/Customer for which we are working for.
FAIZ MODI
Theory and Hands On both are equally important, whether it's
about the testing skills or about the product and/or domain
knowledge.
BHAGYASHREE SHETH
once developer is ready to deploy the code to QA environment, ask for
demo, and compare the requirements and product he/she is demoing
upfront ask the questions most of the time bugs are found in demo
cost more, can resolve immediately
It helps to build trust between devs and QAs, and deliver quality product.
SONAL GOSAVI
PRASHANT HEGDE List out tasks before starting your SONU TITUS
Be More Assertive work. Set priority accordingly. Observation
ANKITA BASU
'Be the Customer(End user)'
Think like an end user and make a list of all the functionalities you would
like to see in the system. Out of the box ideas can make a huge change and
add value to a quality product. Jot down the ideas, it will be easy to develop
and test a system from scratch and make further changes in advance if
needed.
PRIYESH NAIK

Good observation - It's surely one of the best and most important
qualities of a good tester.
SWAPNA SAMISHETTY
In this agile world, very less importance is given for documentation. But
always maintain what has been tested in a proper channel.
This will help to avoid to take the blame for production issues.
PRICILLA B
‘No harm in asking for help. Nowadays I see many people from
forum's and communities coming forward to help for any technical
help. Make sure to get one, and to return when you get a chance :-
)
MRUGANKA PATWARDHAN
BADARINATH BHASKARA
Do proper analysis, ask questions, don't make
As a QA, always criticize the product but not the assumptions.
producer.
SAMEER PURANDARE
Try to put yourself in the shoes of your clientele. Your business
acumen will improve and so does your test suite.
RACHANA BANERJEE
Always have a transparent discussion with your lead and team members
about what is expected from you as a part of your contribution in the sprint
SAMREEN ADIL
Always know your customer/ end users of the product. If you
don't, ask questions.

BRIJESH DEB
Automation is a tool and not the goal. Use it like a tool.
Use automation to solve your problems such as reducing redundancy and

not because it's a buzzword and almost everyone has jumped on the
automation train. If your product/application does not allow room for
automation in testing then don't chase it. Instead spend time exploring
more.
MUKTA SHARMA
Always speak up in meetings. Give your point of view on different
user stories/requirements being discussed. Think before you
speak but speak up your mind.
ADEBAYO JACOBS-AMOO
Put a lot of thoughts and efforts in your test planning and preparation. The
quality of those activities will drive the quality of the outcome of your Test
execution
SUNNY BHATIA
Testing without requirement documents / SRS / documentation
reveals more quality bugs if done with passion, interest and
enthusiasm.
One must strive to test( I must say use) the product/software as if

they are using Instagram/Facebook/etc. without reading their
documentation.
GAURAV MISHRA AHILESH

SAHITHYA REDDY
MANICKAVASAGAN
KADAPAKONDA Don't let ego overpower when
you're in need/seeking for any 'Assumptions is the mother of
Learn to unlearn and relearn.
help. all failures.' -Anonymous

RIDDHI SHAH
Remember if you want to automate any product/module, you
must have good functional knowledge of the product/module.
It's good practice to do exploratory testing and go through each

scenario, otherwise really difficult to automate even if you have
good coding skills!
DIMPY ADHIKARY
The need of learning more than one programming language is not new for
testers.
SHAILESH GOHEL
While working on automation, be habituated to add any
file(driver.exe, png, txt, xls etc.) within your project folder and
provide its path in script, even if you are doing it for learning.
Avoid giving paths like
"c:/shailesh.gohel/user/desktop.testdata.xls". You never know
when that demo script becomes your actual code and you merge it
with master or use it for actual use.
RITIKA GHOSH
JYOTI MISHRA
Always report bug after analysing complete root
Avoid reinventing the wheel unless existing cause be it small css bugs or big feature bug
solutions is not able to solve your problem
FAIZ MODI
Don't be too hesitant to ask for help.
But at the same time don't be too dependent on help from others.
Try to be self-reliant as much as possible.
SHIVA PRASAD B M
All Green in automation execution report doesn't mean your
scripts are working fine ( in the duty of catching bugs... ) Never
write scripts/ never automate TC for the sake of automation and
never ever make it as pass

“Application security mind set is the master key. Use the key to
unlock the minds of black hat hackers!
Santhosh Tuppad

PRASHANT HEGDE
Be data-driven as a tester.
Make critical decisions backed by data rather than making decisions that
are intuitive. Rely on data and metrics to reflect on how well your team is
progressing towards its goals.
NAGASRUTHI JALIGAMA
Don’t run Out of Time to do high priority testing tasks. Prioritize
your testing work from high to low priority and plan your work
accordingly. Analyse all associated risks to prioritize your work.
ANIRUDDHA BISWAS
While writing automated scripts, If anyone is still there who adds xpath for
each drop down options, please change it now, that is not automation, that
is human intervention using a tool. Automation should help reusability and
reduce repetitive work.
SACHIN SHARMA
"Content without context is useless and the same goes for testing."
Its should always be considered as crucial and a primary step to

understand the context behind the objective and purpose of
testing activity you are going to perform.
ANKITA BASU
'Be open minded' to receive a peer review/feedback.
It's amazing how a peer review or feedback over a discussion can add value
to a product. Sometimes the expert tester can also miss important
checkpoints and peer review can save it. :)
If you are working as a tester, make sure you have a discussion with your
business analyst and developers, if needed include test lead too for expert
advice. Being able to consider different people views can help you grow
both personally and professionally. A win-win for everyone.

SHASHANK CHATURVEDI
According to Test Automation Process first prepare the
manual test cases and mark them as Smoke, Sanity,
Regression etc and on first attempt try to Automate the
Smoke Test Cases and then move forward.
Make sure we should have the Manual Test Cases handy

before working on Automation.
Also try to execute the manual test cases first because this
will help you to get more understanding about the logics and
the flow.
WAYNE ROSEBERRY
"If your product/application does not allow room for automation in
testing then don't chase it."
I think of this different - to which I suggest this silly analogy:
Home Owner: Build me an indoor swimming pool
Pool Builder: We cannot. Your house is on swampland and the pool

demands more structure and support than one can get from
swampland.
Home Owner: Can't you do something to mitigate that and still get
me the indoor pool?
Pool Builder: I don't think lack of an indoor pool is your most

important problem...
Like our house on a swamp, if a product cannot support automation,

that product is fundamentally on unstable ground as it is. The test
team is not the one that needs to engage to "chase it". The
development team needs to re-architect the code to make it more
testable.

SHEELA S K
Most of the time developers comment that artifacts attached in
the bug report are not enough to do root-cause analysis of the
issue reported. The bug reporter should provide enough
information and details related to the reported issue :
Following logs of different forms and types are useful,
1. Test execution logs
2. Network logs – capture of network traffic as part of functional

tests to understand any drop / issue in specific network calls. Ex:
HAR (HTTP archive format) capture can give you a lot of insights
3. Device logs (if applicable)
4. Screenshots, if video recording of the failed test is not available)
5. Corresponding application logs
6. System health logs – i.e. Server-side memory / cpu usage and

response times
SK AMIR ULLAH RAHUL PATIDAR
Assumption is a sin for testers. Feel free to ask. Self rejection can be dangerous, if we are
testers, we should find the issue and then
Expect the unexpected !! definitely go for the solution.
ANAND JAYARAM
Quality is much more than validation of code correctness. Look for
processes that are delaying your releases. Figure out what we
should target to optimise - Time, Effort, Coverage or others?
Even if it's just a 5 min saving in release, it will have a multiplier

effect given the number of times the release happens. So look for
opportunities to reduce the time taken. Show the improvement to
the team so that they can visualise it.

RICHARD FORJOE
Always remember to take a step back and take a holistic view of what you
are working on. Too often I see testers focus on one detail and forget
there’s other things going on that might also need attention. New info often
shifts priorities
YOUSSEF TOUATI
Areas where Automation can be attempted first:
1. Highly redundant tasks or scenarios
2. Repetitive tasks that are boring or tend to cause human error
3. Well-developed and well-understood use cases or scenarios first
4. Relatively stable areas of the application over volatile ones must

be
automated.
SONAL GOSAVI PRASHANT HEGDE

SAMEER PURANDARE
If you are testing website, make Test Automation without a goal
Do not hesitate to explore the
sure that you tested it on all is meaningless. Do not
application/product
supported browsers automate for the sake of it🚫
SWAPNA SAMISHETTY
● Convert customer reported bugs to test cases, so that those

test cases will not be missed in further releases.
● As a tester try to replicate the test environment as same as the
customer environment.
● Try to find customer scenarios ask all the stakeholders for
details
VIKRANT DESAI
MUKTA SHARMA
Always think out of the box and apply different
“Be Thankful, Be Grateful and stay Humble”! 🙏
negative scenarios while testing.

Career tip: Play the long game. Make career decisions keeping the
long game in mind. Not for immediate returns. The short games
are played by stock market traders. They experience huge wins and
also huge losses.”

BRIJESH DEB
Testing isn't just about marking a bunch of test cases pass or fail or raising a
few defects. Go beyond the idea of test cases and focus on test ideas and
test design. The tests tell you a lot more about the product than defects.
SWADHA SUNDAR PANDA

SACHIN SHARMA
Everything can't be or shouldn't be
"You need not to learn or implement any new specific
automated for the sake of Automation even
process and 'do agile', instead you have to keep
though it is not meeting the whole purpose
improving your existing processes to 'be agile' :)"
of Automation…
ANKITA BASU
'Theory of Testing''
Playing with the system is indeed the most interesting part of Testing but
without having basic knowledge and familiarity with terminology might
exclude the purpose of it.
So before jumping to the ocean, let's learn the A B C D of testing and try to
visualize/relate to real time scenarios.
FAIZ MODI
My tip is inspired from one of the things from all the amazing
things discussed today in the WIT Chatterbox: "Always be vocal
and also never be afraid to ask for the things which you think you
can/should/deserve to get by asking."
MUKTA SHARMA
Always ready to learn at any stage of your career. If you are a fresher or even
10yrs.experienced person, learning should never stop. Cuz once you stop
learning, your growth stops.
SAMEER PURANDARE
PRASHANT HEGDE
Very fundamental tip. As a tester
Mimic the way the customer tests the product,
(manual/automation), your aim should not be
both in terms of user behaviour/actions and
passing the test cases. Defects are your bread and
user data.
butter.

JAGADEESH JAYACHANDRAN
Whenever you automate any test script add a checkpoint/assertion wherever
possible. Otherwise, that automation script is a joke, it will never find a bug
though there is one.
RITIKA GHOSH
Before giving Sign Off, always run all regression test cases against
the release ticket. This will give us better clarity on stability of the
product.
please note signoff is done either by PM or QA depending upon
company to company and the above mentioned tips are when QA
is to be considered for giving signoff.
RIDDHI SHAH
Sharing is caring! It will help you to grow in different areas of your interest.
Whenever you are communicating with Dev or QA, be polite and share your
knowledge. You never know when you also need him/her and at that time he
will remember your behaviour and accordingly take steps.
Scenario 1- If you have logged any issue and the scenario is difficult to
replicate for Dev, or any other team members, then please be polite and give
some time to explain it! Believe me this will affect positively later in your
career as well.
Scenario 2 - If you have knowledge in one area and you want to explore
different areas, don't hesitate to share your knowledge with the opposite
person, who has a different skill set. In that way you can learn how to start
with a different skill set which he/she has.

DIMPY ADHIKARY
How to improve the testability aspects of an application? Here is
my tips for identifying testability gaps:
1) Identify all possible states of the system in the requirement
gathering/system design phase. This will help to identify all the
observation points which may need dedicated testing focus.
2) Paying attention to the intermediate states of the system which
may not be directly visible to the end users but important to test
to reduce the overall risk. For example intermediate logs/ temp
files/diagnostics statements which can prove the correct state of
the application for some workflow.
3) Can we test all the components of the application independently
or as a system? If not what is needed to improve the testability?
For example looking for possibilities of changing the scope of
some classes from private to package level so that those can be at
least unit tested.
4) Adding automation testing enablers like unique ui identifiers,
3rd party integration testing switches supporting mocks/real
interference, configurable features in test environment etc can
drastically improve the overall test coverage.
"You can be a great tester if you have programming skills. You can also be a
great tester if you have no programming skills at all. And, you can be a lousy
tester with or without programming skills. A great tester will learn what skills
she needs to continue to be great, in her own style.”— Jerry Weinberg
SUNNY BHATIA
Don't get afraid if the issue found by you has put the release on
hold. The issue unearthed by you is much cheaper than found by
the client in production.
Be bold, communicate well, keep growing and moving.
Build Right foundation to facilitate agility in software development

BRIJESH DEB
𝙏𝙚𝙨𝙩 𝘾𝙧𝙖𝙛𝙩𝙨𝙢𝙖𝙣𝙨𝙝𝙞𝙥 𝙞𝙨 𝙖 𝙥𝙧𝙚𝙘𝙪𝙧𝙨𝙤𝙧 𝙩𝙤 𝙏𝙚𝙨𝙩 𝘼𝙪𝙩𝙤𝙢𝙖𝙩𝙞𝙤𝙣.
So before you begin your test automation journey, learn the basics
well. And during your automation journey, revise the basics from
time to time .
Being a better test craftsman helps you being better at test

automation
FAIZ MODI
Understanding and learning about the business side/impact of the
feature/product you are working upon can be a game changer and can help
you test better.
GAURAV MISHRA SONAL GOSAVI

IMO it is very important to have a growth Acceptance criteria must be added in your story. It is
mindset (a belief that you can learn and easy for testers to write test cases by considering
improve) to achieve any goal/growth. those criteria.
ANKITA BASU
Understand feature suite/test and regression suite/test before
starting automation.
Automation is the trend but it is only beneficial if we are trying to
test a stable system multiple times. Regression is supposed to
cover the existing features with different combinations and if
possible with minimal test cases. Then only the regression suite is
perfect to start automation.
It is risky if we try to automate new features because it won't help
finding bugs and the purpose of testing will not be justified.
PRABIR CHAKRABORTY
It's equally important to identify what not to automate , don’t just automate
all tests blindly. Leave some complex areas for a human tester to check,
human (tester) mind can find special scenarios and identify issues which can
be easily overlooked in automated scripts.

SHAILESH GOHEL
Job of a Tester is not only finding maximum bugs but also to get
them resolved.
In order to achieve it, write your bug summary in a way that dev
team understand it easily, also try covering maximum evidence or
details like steps to reproduce, Test Data you have used, screen
shots/recording, OS Browser combination, Server Logs, if no
server log than at what time you find the error(it will help
developer to find the exception easily from log), console output,
API response etc. All this will help developers understand easily
where a fix to be made and will tempt him/her to resolve the
issue.
ADEBAYO JACOBS-AMOO SACHIN SHARMA

Don't just ask (the difficult) questions, “Testing is not a phase, for which we need to wait
entertain/embrace (difficult) questions too. It till it comes, in fact ‘Testing’ is an activity that
facilitates thinking! should be done every time.”
MUKTA SHARMA
If you are using Java in your automation framework, be strong in
OOPS concepts (Polymorphism, Encapsulation, Abstraction and
Inheritance) so that you can implement them in your framework
and if it is already existing then you can understand or contribute
towards the existing framework as well. This will help you in the
long run. Some references to follow on YouTube:
1. Naveen automation labs
2. Learn automation - Mukesh Otwani
3. Step by step -Raghav Pal

RIDDHI SHAH
When you are logging any issue, Remember to provide all the evidences like
::
1. Screenshots,
2. Recording
3. Log -- Logs are very useful Especially, when the issue is not reproducible in
all scenarios. In such scenarios it will help to debug the issue for Dev, so
accordingly they can fix it.
4. Provide all the steps properly, so that any other QA or Dev can reproduce
the issue.
Do not
1. Do not provide only Screenshots for functional issues or any critical issues,
as it won't help to replicate the issue.
2. Do not provide 1 or 2 liners steps, as it won't help much to replicate the
scenarios
ARPITA SWER
If you are a fresher in Testing. Always stick to the basics. Never
jump to the automation testing first. Understand what Testing is.
Train yourself the basic in practical then target for the next level.
DHANALAXMI OTARI
Taking notes during online workshops, talks, webinars, helps us remember
concepts better, even if those sessions are going to be recorded. In Q & A
session, notes are handy to ask the most relevant questions.
SACHIN SHARMA
DHANALAXMI OTARI
My tip - "First, always be YOU !" and "Align all
Asking questions is an integral part of testing.
your efforts to become a better version of
Questions invite answers and understanding.
yourself every day !" :)

DIMPY ADHIKARY
Is your test data smelling bad? Here are few remedies you can try
to heal the same:
1) Consider identifying all your test data needs at - org level,
project level, teams level etc. and consider those in your test plan.
2) Start building test data as a single point of truth for everyone,
no more BA/Dev/Tester/Customer version of data please.
3) If you are creating test data every time before test execution,
time to focus on the test data generator. Identification of different
data types, patterns, accuracy criteria, logical dependencies can
help to create suitable test data.
4) Time to invest in infrastructure needed for
storing/retrieving/sharing data need basis with ease.
5) Take care of security aspects of data specially when test data is
copied from prod.
6) Direct test data loading in the backend can be done using an api
or db script.
7) Don't forget to apply setup and tear down routines every time
you test irrespective of whether the execution is done using script
or not, to keep your application in stable and known state.
RIDDHI SHAH
When you are closing any defect, (Even if you are reopening multiple
times)Make sure you are giving all the proofs especially Recording, so that
Dev or Your manager will be aware that the issue is actually fixed.
If suppose you are just closing the issue, without no recording, and later on if
someone is catching same issue in PROD or even Client has found same
issue, then It will be pointed to QA, instead if we closed the defect by adding
recording or if any other proofs then we can be confident that it was not Our
fault, but the issue is broken due to some other scenarios.
Believe me this can Protect QA at later stages, once the product is Live.

“The value if a test is measured over time and as such, it must be
continuously maintained and monitored. Tests should grow with
the product and updated as needed. When a test stops adding new
insights or value it should be either removed from the suite or
transformed into a new one based on its objective and the
feedback gathered over time- that’s why versioning test and
treating it as we treat code is recommended”
Eran Kinsbruner

GANDHARV MADAN ARPITA SWER
Tip 1 : Organize Everything. A good QA lead should always be persistent
Tip 2 : Treat testing like a team effort. about her/his choice. Choice can be anything
Tip 3 : Understand the data flow. tool, process, strategies, technology etc.
BRIJESH DEB
Include Testing as a part of the sprint if you are part of a scrum team. Remember
a user story is not done if it's not tested and it's not agile if you have a different
sprint for testing.
FAIZ MODI
Testing is not an easy job but it can be made a little bit easier. To make it
easier one can do one or more of below things:
1. Read Books/Magazines/Blogs
2. Attend Conferences/Webinars/Events
3. Take some courses which really help you learn
4. Do upskilling in proper manner which should include soft skills as well
if one needs it
5. Be a part of a community (And do active participation as and when it's
possible for you)
6. Connect with people on different platforms, but don't stop right there.
Feel free to share your views regarding what they have posted/tweeted
in comments/reply regardless of whether you agree or disagree. That
way you can have a better understanding of that topic.
7. Believe, understand and accept that no one is perfect and no one
knows everything. So don't get disappointed by doing unnecessary
comparisons and just compare yourself with your previous self and try
to be better than that.
PRASHANT HEGDE
Embrace In-sprint test automation
Test automation cannot be a side project. In-sprint test automation is all about
automating your user stories within the sprint window.
YOUSSEF TOUATI SUNNY BHATIA RIJOY GEORGE

𝐎𝐯𝐞𝐫𝐭𝐡𝐢𝐧𝐤𝐢𝐧𝐠 𝐤𝐢𝐥𝐥𝐬. Comprehend your project
Automation is good, but it doesn’t If you start overthinking risks, assumptions,
fix poor test design. anything, ask yourself, "How dependencies and constraints
important is that?” well to help you test better.

SAMEER PURANDARE
If you are in manual testing, start learning about automation. Learn to code,
understand the core features of automation tools used in your project, try to
understand the framework which is implemented. Take time to learn at
home as well.
If you are an automation tester, get an understanding of the application,
understand the test scenarios, test cases written by the QA team, see the
defects logged, understand the process of manual testing, manual testers go
through.
This mix n match will not only be beneficial in upcoming releases, but you will
feel empowered as well.
BRIJESH DEB
𝑺𝒉𝒂𝒓𝒑𝒆𝒏 : 𝑼𝒑𝒅𝒂𝒕𝒆 𝒚𝒐𝒖𝒓 𝒔𝒌𝒊𝒍𝒍𝒔𝒆𝒕 𝒄𝒐𝒏𝒔𝒕𝒂𝒏𝒕𝒍𝒚 Technology is changing
everyday and hence it is important to keep updating our skills. Focus on
being a better tester everyday!
FAIZ MODI
It's absolutely okay if you're not able to reach your goals as per what you had
set initially for things which are professional in nature (but not work related).
Just make sure that rather than stopping or getting disappointed, you
resume from where you had paused and slowly but surely you are working
towards it.
SACHIN SHARMA
"𝗦𝗲𝗲𝗸𝗶𝗻𝗴 𝗲𝘅𝗽𝗲𝗿𝘁 𝗮𝗱𝘃𝗶𝗰𝗲 𝗶𝘀 𝗮 𝘀𝗶𝗴𝗻 𝗼𝗳 𝘀𝗺𝗮𝗿𝘁𝗻𝗲𝘀𝘀"
Do not hesitate in getting guidance from your superiors. Referring
experts, seniors, industry leaders is actually a great habit. One should be
very confirmable at saying "𝙄 𝙙𝙤𝙣'𝙩 𝙠𝙣𝙤𝙬 and I will learn it from experts
in my circle".
Asking appropriate questions to relevant people will always help in
enhancing wisdom and foster the learning of tackling challenges.
It is one of the greatest tips I received from my mentors during my early
days of professional life and I always try to enroot this same habit in my
circle. Take it seriously and sincerely, it helps.

Don't rely on a single automation tool. Always try to learn new automation tools
as the market keeps changing.
Also there is no single tool which can cover all types of testing. So based on the
requirement select, learn and use the tool to its full capability.
JYOTI MISHRA
Remember when we were kids, while playing Prince of Persia, Dave,
Mario etc our focus was always on completing the final level and if we
used to fail in any level, we used to learn from those experiences and
restart again with double the excitement. As we knew that in this
attempt we have learned of our previous attempt.
Playwright (or Puppeteer ) and Selenium
1. Playwright (or Puppeteer) is based on devtools api which is developer focussed
and won't mimic how a user would perform ( if it won't no point in using
something like that for E2E tests)
2. For quick reproducible tests those are great(be it Puppeteer or Playwright)
3. Playwright is so patchy that it comes within their own browser which Firefox
and Google don't ship, so you are not testing on browsers that your users would
do... And so on...
RIDDHI SHAH
Start learning Programming language. Preferably Java/Python/C# when
you are new to programming and if you already have good experience in
automation using one programming language then Learn a new
language and practice different frameworks. Even though it's slow, keep
moving.!
1. Choose one programming language

2. Follow YouTube channels for learning Programming basics.
3. For each video other than explained examples, try practising with
some new examples, so that particular concept will be much clearer.
4. Focus on learning OOPS concepts and make your base stronger.
5. Even though it takes time, do not stop or disappoint.

BRIJESH DEB
𝑻𝒆𝒔𝒕 𝒚𝒐𝒖𝒓 𝒅𝒐𝒄𝒖𝒎𝒆𝒏𝒕𝒂𝒕𝒊𝒐𝒏
Any documentation that you consume as testers must be tested for the validity of
the content. It may be requirements, release notes, test data, etc.
Any documentation that you create such as a test report must also be tested
thoroughly before you pass it on.
GAURAV MISHRA
Practice and Intensify by Sharing/Teaching what you've learnt :: This not
only gives an opportunity to recall/revisit the knowledge(if not in touch)
but also helps in strengthening the understanding that we have gained
on a specific area
ANKITA BASU
Collaborate. Testers and developers are just 2 sides of a coin. As a tester, explain
to your developers how you are expecting the system to behave, both of you
should be on the same page. If needed, reach out to the business for proper
clarification. Collaborating with patience can bring impactful changes into the
team to work together for a quality product.
FAIZ MODI
If you know when/how to say "Yes" and when/how to say "No" then it
can be really helpful for your professional life as it will help you for your
career growth and would save you from unnecessary pressure.
Testing is a diverse field and can be divided into many sub categories like UI
testing, performance, security etc. A tester can learn and work in all fields if he
manages to do so but always remember that whatever field you select first deep
dive into it and then move on to the next field.
ADEBAYO JACOBS-AMOO
It is Okay to make mistakes, we all make mistakes. Learn from the
mistake and move on. However, what is not acceptable is a habit of
making mistakes, especially the same ones. It has a lot of meanings and
none of them is good!

MUKTA SHARMA
While working in scrum and while starting working on a user story, we must first
analyse if we are meeting “DOR” (definition of ready), if it meets the DOR then only
you can start working on a user story else as a QA, you have full rights to NOT
accept it. Similarly, when you accept it which means that it meets DOR then after
you finish testing, we must check whether it meets “DOD”(definition of done). It
should match the criteria set for DOD.
SACHIN SHARMA
"𝙏𝙝𝙚𝙧𝙚 𝙞𝙨 𝙖 𝙙𝙞𝙛𝙛𝙚𝙧𝙚𝙣𝙘𝙚 𝙗𝙚𝙩𝙬𝙚𝙚𝙣 𝙠𝙣𝙤𝙬𝙡𝙚𝙙𝙜𝙚 𝙖𝙣𝙙 𝙞𝙣𝙛𝙤𝙧𝙢𝙖𝙩𝙞𝙤𝙣, have
information about almost everything but it is mandatory to have
knowledge about your field's upgradations , your work stream's
modifications and your industries newness.... just information will never
suffice."
Get the difference and approach accordingly!
JYOTI MISHRA
Importance of RCA!
Understand the RCA of all critical and high priority bugs. As part of a preventive
action, look for the opportunities to make procedural/structural changes that will
help us in catching these in the early phase of development and testing.
e.g. In my first organisation I had read one issue where in browser zoom of 110
prevented users from loading images in the Media Library, then after a few years
in different organisations I came across a similar issue which was raised by users
where in on browser size less than 100 users were unable to enter CVV.
Issues like these educate us that there are so many permutations and
combinations of browser type/size and here is where we can leverage
automation. Yet what we do is we automate cases the way we tested it and hence
less ROI.
In a microservices world, contract testing is very important to ensure any
changes in the producer do not impact any of its consumers. This can
prevent regression issues and avoid huge e2e testing.

“As a tester, remember and try to make other people understand
that software testing should not be limited to verifying that a
system does what it is expected to do. Challenging assumptions,
learning how the system really works, investigating under which
conditions it might fail: all that should be a must.”
Ileana Belfiore

MUKTA SHARMA
Let’s revise some API responses status codes :
▶️200 OK
General success status code. This is the most common code. Used to indicate
success.
▶️201 CREATED
Successful creation occurred (via either POST or PUT). Set the Location
header to contain a link to the newly-created resource (on POST). Response
body content may or may not be present.
▶️204 NO CONTENT
Indicates success but nothing is in the response body, often used for DELETE
and PUT operations.
▶️400 BAD REQUEST
General error for when fulfilling the request would cause an invalid state.
Domain validation errors, missing data, etc. are some examples.
▶️401 UNAUTHORIZED
Error code response for missing or invalid authentication token.
▶️403 FORBIDDEN
Error code for when the user is not authorized to perform the operation or
the resource is unavailable for some reason (e.g. time constraints, etc.).
▶️404 NOT FOUND
Used when the requested resource is not found, whether it doesn't exist.
▶️500 INTERNAL
The general catch-all error when the server-side throws an exception
BHAGYASHREE SHETH
once developer is ready to deploy the code to QA environment,
ask for demo, and compare the requirements and product. He/she
is demoing upfront ask the questions, most of the time bugs are
found in demo cost more, can resolve immediately. It helps to
build trust between devs and QAs, and deliver quality products.
RICHARD FORJOE
Learning test automation takes time, dedication, it’s not easy
so make time for it daily. I’d highly recommend doing
100DaysOfCode to get into the habit of coding in a language.
Learn to write code devs can support vs code devs run away
from

Become so confident in who
you are that no one’s opinion,
DEVIKRISHNA R Change your life in a year
rejection, or behaviour can
rock you
ANIMESH MISHRA RAJESH KUMAR

Benefits you are looking for from Software Testing keep yourself up to date with latest
are directly proportional to the importance (Time, technologies/tools. Always set short term goals(6
Budget, Resources) given to Software testing. months) and work on them.
SAURABH SONI
Org culture and testers empowerment plays an important role as well.
Testers are not superhumans to pinpoint and locate every defect, even when
you cater to them with a plethora of time! It's the team responsibility to
ensure quality... We as testers are headlights of a vehicle (consider vehicle as
a release) and not drivers!!
INDU SHARMA SRI PRIYA P KULKARNI
Don't forget to reward high value defects :) As a Tester, one should have patience while testing,
communicating the defect or issue and all over the
process. Patience is the key factor for a tester..!!!
INDU SHARMA
Use Test Cases Quality / Coverage, Defects Quality/Quantity, Defects slippage
, No. of great defects, Automated tests code Quality , flakiness of Automated
Test case counts, No. of complex features tested, Innovative tools developed,
No of process improvement instances , new skills learnt etc metrics in the
performance Appraisals .
However, don't forget the importance of collaboration, attitude , taking

responsibility, going extra miles in mission critical situations, analytical ability,
team player etc which are not directly measurable/ comparable yet , they are
very critical aspects for the success of customer, product , org and hence
team. Agree ?
If you want to change things How long should you try?

in a big way, then you gotta DEVIKRISHNA R
make some big changes Until you SUCCEED

PRAVEEN MATHEW
Do you know you can use the DOM breakpoint feature in chrome browser
to break the DOM rendering to inspect short life span elements like
spinners, drop downs , tool tips etc .
See an example on how to inspect the linked in profile settings using the
DOM breakpoint.
1. Just right click the html or body tag and use break on subtree
modification ,
2. Click the UI component (profile icon) to trigger UI rendering
3. Keep pressing F8 to continue execution till the indented element is
rendered in the screen.
3. Now you can inspect the element , the UI remains in breakpoint till the
break point is removed and execution is continued.
TRISTAN LOMBARD
INDU SHARMA
Join every software testing community that you
Before closing your laptop, make sure all your
can find. I am in 182 communities and counting
cloud resources are terminated. Make it a
and always find a different value proposition for
regular habit :)
each one.
TREVOR MALGAS
When you do sessions, treat them as pomodoros. Focus and actually
defocus after each session.
If you cannot concentrate for 90 minutes straight, do three pomodoros

within the 90 minutes.
Distractions and defocusing is important as it can help you gather your

thoughts to new test ideas or help you see something you might have
missed.
Dream big! There are no limitations

The biggest wall you’ve gotta
to how good you can become or
climb is the one you build in DEVIKRISHNA R
how high you can rise except the
your mind.
limits you put on yourself.

AVISHEK BEHERA
Never hesitate to ask your team about contribution to testing. Being a
tester, you are not the only one responsible, sometimes apart from the
tester , others ignore to contribute, thinking it will be done by the tester.
Sometimes asking them to help or contribute, works and if everyone from
the team starts looking at it, there might be many uncovered scenarios and
aspects.
SRI PRIYA P KULKARNI DHANALAXMI OTARI

According to me, to be an efficient tester, you need If someone has decades of experience in a
to avoid guess work & assumption work. particular field, and they put it into a book, that
Also one should focus on communication & also means you can download decades into days. -
should be attentive all the time. Quote by Jim Kwik
INDU SHARMA
Testing is not knowing java
Testing is not knowing Python
Testing is not knowing framework Development
Testing is not knowing Data bases or any other complex technologies
Testing is not coding
Testing is not writing tests
Testing is not running a checklist
Testing is not any low pay job than any other development.
Testing is also a Development, development here doesn't mean writing
code, building features only.
Testing is all about arts , science and continuous analytics which helps to
create prototype versions of many end users to "One you" and all the tools
in above list provide some level of assistance.
RAM PRASATH APOORVA UTHRA

DHANALAXMI OTARI
ESWARASAMY Be transparent no matter what
Collaborate more, talk to the team
the situation is as transparency
As a tester, never assume more to get their perspective on a
is imperative if you want to rise
anything. user story, feature or a bug
in your career.

PRABHAKARAN RAJENDRAN
Always have Test-specific status meetings that can serve to monitor testing
efforts, to report test progress, and to identify any test-related problems.
Testers can meet separately and use test measurement data and related
documents to specifically discuss testing status.
Following this meeting we can then participate in the overall project status
meetings
Ever tried. Ever failed. No

matter. Try again. Fail again. DEVIKRISHNA R Climb it, go through it, or work
Fail better around it.
JYOTI MISHRA
Spare some time in understanding how systems are designed, this gives you
a holistic overview of an application.
Know your customer and his/her journey and by knowing how the system is
designed helps you understand what goes behind the scene in that journey.
The moment you’re ready to quit is

DEVIKRISHNA R usually the moment right before
Set goals like a boss the miracle happens
JYOTI MISHRA
Ensure any crucial discussions you have regarding the feature/product with
stakeholders, it's updated in JIRA/email.
Once we found a bug which had cost us in crores and on retrospection we

got to know from team that mentioned flow was never tested or developed
after discussion with PM as it was not part of phase 1 development, and
while making feature live same was not conveyed to onboarding team so
they went ahead and enabled that feature. Ironically the PM for that
feature was not in the system when this bug was found and there was no
paper trail for this discussion.
This incident taught us why it's important to have things in written, also
while making features live one should call out such scenarios/flows
explicitly to ensure everyone is on the same page.
Everything boils down to one thing, Never Assume.

DHANALAXMI OTARI
workshops, talks, webinars, help us remember
Don't forget to take notes that you see and hear
concepts better, even if those sessions are going
during meetings ,conversations and when testing
to be recorded. In Q & A session, notes are
the software.
handy to ask the most relevant questions
INDU SHARMA
Make sure to use "sql Injection Datasets" from FuzzDB for testing the "data
Input" fields across your UI application for identifying the SQL injection
vulnerabilities.
Example : You can use the strings from this dataset to test if you can
bypass "User Name" and "Password" validation in your application.
Time management tips:

Set goals correctly, Prioritize wisely, For true mastery, you need to
Set a time limit, Brain workout, DEVIKRISHNA R focus more on the output, rather
Organize yourself, Remove non than the input.
essential tasks, plan ahead
JYOTI MISHRA
It's important to understand your user and his/her journey while testing a
product.
Yesterday only I was reminded of this tip where I spent some time finding
one corner case but on further discussion with the PM got to know that it's
very rare that a user will do what I did.
Understanding algorithms If your are testing web-services

always helps to solve complex APIs: make sure to cover API
problems regardless of any testing, API contract testing , API
INDU SHARMA
role in the Tech industry. Integration Testing, API Security
Don't let your role restrict you testing and API Error Handling
:) testing
MOHANRAJ PANNEERSELVAM
Accept Mistakes during Testing. If any scenario is missed from your side
and due to that a bug has been captured by someone other than you and
pointing at you, let's accept it.
This helps avoid unnecessary arguments between the team with whom you
are going to work tomorrow.

Speak to someone with a background in burglary to get the
security mindset and a deeper understanding of your
application security.
Santhosh Tuppad

BRIJESH DEB
Work on your communication, reporting and storytelling skills. Keep
sharpening the saw and get better.
No matter how good your testing has been, there is very little value or no
value if you can't put it across well enough in your report or if you cannot
explain defects to developers.
GAURAV MISHRA ANKITA BASU

Feel proud of whatever work you are doing, since until you can't Test your product not only
hold a strong side, how/why will anyone else value it. user stories.
FAIZ MODI
If you want to be more knowledgeable then don't be that person who keeps
the knowledge with him/her only and doesn't share it with others in fear of
others becoming more knowledgeable than yourself. Because it works
exactly the reverse way, the more you share your knowledge with others
the more knowledgeable you become in one or other way.
SAMEER PURANDARE
As you learn things in testing, don't be hesitant in sharing your thoughts
on the concept in the testing community, even if you are not sure if you
are right or not. If you are wrong, there are people to correct your
understanding. If you are right, then you may be clearing someone's
concept.
SHAILESH GOHEL
When learning any new tool or framework, best learning resource will be its
documentation. Read and understand that first before looking for a blog or
you tube video.
Tool's documentation would explain on all core features while blog or video
may be designed on some specific scenarios.

RIDDHI SHAH
Have you ever handled rude/attitude boss/Lead? have you ever worked
with the person who doesn't believe in you and you have to give them
proof for your work assignments?
Believe me these people teaches us a lot, if you start taking him/her

positive way then it may happen that after few days/months people would
believe in you more than anyone else
ARAVIND M
Be strong in Fundamentals!
Fundaments is the core of any field. It is like basement of any construction

structure. If the basement is weak then there are greater chances of the
structure falling!!
In the same way if the fundamentals of testing is weak then you won't be able
to excel in other areas!
Fundamentals may include core concepts, different techniques, strategies,

design patterns etc. that will answer the five W's and one H questions - Who,
What, When, Why, Where and How
Be strong if fundamentals of testing to become a better tester!
Be strong in fundamentals of API to become a better API tester!
Be strong in fundamentals of Performance to become a better Performance

tester!
Be strong in fundamentals of Programming to become a better Automation

tester!
The list goes on...
MUKTA SHARMA
In amidst of everything (working from 9:00-5:30),learning, upskilling,
contributing
tocommunities,YouTube,discussion,debates,talks,blogging,speaking), please
don’t forget to take a BREAK to rejuvenate yourself from all the hustle and
bustle of life. Self-love is as important as other things are. Take care of
yourself!

Choose your tools for automation testing wisely. Every tool have their
own pros and cons. Some points given below
1.Check what type applications you will be testing using the tool.
2.Check if you want an open source or a licensed one, if it is licensed one
check if you can bear the costs
3.Check if tool you are selecting supports the applications you have to
test
4.Check if the tools can be integrated with CI pipelines.
5.Check if it integrates or has third party plugins for integration with JIRA
and ALM integration or any other test management tools your project
has
6. Don’t always stick to the same tool, the market is evolving keep track
of the same, you never know some of the existing issues of your current
tool might have been fixed.
ADEBAYO JACOBS-AMOO
Remember, it is not always about who is right, it about what is right.
Use the full strength of your team and get things done. Where our
individual effort falls short, our team is there to pick us up.
SACHIN SHARMA
"Managi𝗻𝗴 𝗰𝗼𝗻𝗳𝗹𝗶𝗰𝘁𝘀 𝘀𝘄𝗶𝗳𝘁𝗹𝘆 𝗶𝘀 𝗮𝗻 𝗶𝗻𝘁𝗲𝗴𝗿𝗮𝗹 𝗽𝗮𝗿𝘁 𝗼𝗳 𝗹𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽: There is
natural potential for conflict at work. People experience conflict
when problem-solving, making decisions with others, and
agreeing on plans. From simple to complex situations, the
conflict will occur. For some, moderate conflict is expected and a
source of creative energy. For others, it is debilitating and
avoided if at all possible.
People, especially leaders, need to anticipate conflict and have

plans for handling it. And when conflict happens, effective
conflict managers explore and identify the real source of the
conflict and work to collaboratively solve it. We are should be
cognizant about the fact that conflict is normal but dealing with it
calmly and effectively is a learned skill.
In short: 𝘼𝙡𝙬𝙖𝙮𝙨 𝙧𝙚𝙢𝙚𝙢𝙗𝙚𝙧, 𝙖𝙙𝙙𝙧𝙚𝙨𝙨 𝙩𝙝𝙚 𝙞𝙨𝙨𝙪𝙚, 𝙣𝙤𝙩 𝙩𝙝𝙚 𝙥𝙚𝙧𝙨𝙤𝙣.

JYOTI MISHRA
Leverage analytics to find information like
1. Browsers used
2. Devices used
3. Usage trend
For example: Browser analytics revealed that 90% of our customer base
was using Chrome. So, we decided to run the regression tests on Chrome
and only Smoke tests on the rest of the browsers. It ensured that most of
our bases are covered and saved some time & effort on our part.
SUNNY BHATIA
Always have a desire to ask questions. Remember there are no dumb
questions.
But it's better to ask smart questions. One such tip - Do not ask
questions whose result is in either YES or NO. Prefer to ask open-ended
questions involving WHAT, WHERE, WHEN, HOW, WHO, WHY.
ARAVIND M
Mail communication is often underestimated.
As testers, we are involved in multiple tasks. Some of them involve a great

deal of planning and discussions such as requirement analysis, sprint
planning, product design review, meetings with BA/Product Owner for
requirement clarification, defect investigation and defect triage meetings,
etc.
It often happens that we raise good pointers during verbal discussions but
don't put it across in the mail or our mail is not well written and lacks
clarity. Sometimes imp things such as last-minute requirement updates,
last-minute defect fixes are discussed verbally or over skype but not ●
communicated in the mail.
We should always make sure to communicate all the important things in

the mail. It will not only serve as written proof but also can be used as
reference points for any future assessment. Our mail communication
should be crisp and clear that is well understood by the intended
audience.

VARADHARAJAN Adapt a culture of continuous Improvement
SRINIVASAN
SUNNY BHATIA
Testing is not about finding defects or raising/logging issues/bugs.
It's about 𝑹𝑬𝑫𝑼𝑪𝑰𝑵𝑮 𝑹𝑰𝑺𝑲 by finding and fixing the problems

which customer might face while using the application.
RICHARD FORJOE
“Don’t let perfect get in the way of good” Balance and
prioritisation. Something that might be a huge concern now turns
out to be nothing in the wild and vice versa
Choose your battles and inform the right people.
BRIJESH DEB
It's important to know the learn about your product and the business it
caters to (the domain). Understand the context of the product and the
problems it solves before you jump into testing the product.
FAIZ MODI
Communication gap can be one of the biggest pain point for any
team member, especially for a tester. So try to be as collaborative
as possible as a team regardless of you are a tester or not and
make sure that testers are involved as early as possible in the
lifecycle.
ADEBAYO JACOBS-AMOO
SHIVA PRASAD B M
Be calm at all times. In all the chaos that may
Extension of this "INVEST/EXECUTE THAT
come along during the life of a project, be
LEARNING" because learning without execution
calm. Calmness focuses the mind, which
is of no use
consequently enhance thinking which is a key
ingredient in what we do. Practice it! 'INVEST IN LEARNING" later "INVEST THAT
LEARNING"

“Do not forget your core testing skills, end of the day we are
testers.”
Naveen Khunteta

GAURAV MISHRA
RIDDHI SHAH SACHIN SHARMA
Divide/Break complex
Work on "Practise what you preach or change tests/task/work intro parts to
communication skills! your speech :)". increase achievability and
visibility on the progress.
SUNNY BHATIA JYOTHI MISHRA

LOGS are very important. When you see any While taking interview, let's not focus on what
erroneous behaviour in the application, consult we know rather understand what interviewee
the application logs or system logs too. These has worked on and ask question around
logs will give you some extra information that those topics to understand how well he knew
will help the software team in analysing and the system which he was testing, be it's
doing something to resolve the issue. architecture, pain points or problem it was
solving.
SACHIN SHARMA
"L𝙞𝙨𝙩𝙚𝙣 𝙩𝙤 𝙪𝙣𝙙𝙚𝙧𝙨𝙩𝙖𝙣𝙙, 𝙣𝙤𝙩 𝙩𝙤 𝙧𝙚𝙥𝙡𝙮: Listening is the best
quality that one can have and the super best thing would be to
master the art of listening. It is not hard to make a mistake
while listening is to preparing your answer during that time
and then reply as soon as the other person finishes. This is a
big problem.
You know, we always learn more if we listen instead of we

speak. We get great opportunity to know about something
new if we listen (more than we speak). So, I encourage you all
to listen and in fact listen with the intention to understand
the thing.
In short: 𝙇𝙞𝙨𝙩𝙚𝙣𝙞𝙣𝙜 𝙖𝙩𝙩𝙚𝙣𝙩𝙞𝙫𝙚𝙡𝙮 𝙞𝙨 𝙏𝙃𝙀 𝙗𝙚𝙨𝙩 𝙨𝙠𝙞𝙡𝙡 𝙩𝙤 𝙝𝙖𝙫𝙚 𝙞𝙣 𝙩𝙝𝙚

𝙟𝙤𝙪𝙧𝙣𝙚𝙮 𝙤𝙛 𝙞𝙢𝙥𝙧𝙤𝙫𝙚𝙢𝙚𝙣𝙩𝙨.
RIDDHI SHAH
If you have been given KT on particular feature, product until you
understand it clearly, "Do not say you understood everything! You don't
need further explanation!
Take time to clarify all your doubts at initial stage, other wise later on it
will become difficult, when you will be suddenly asked to complete work
within given timeline and you are still unaware about certain features!

ANKITA BASU
When you are exploring a product always
record your sessions or try to create a mind Choose your testing type carefully based on the
map or note down observations in black and model(SDLC) followed by your project. For
white. Those references will always help you example, testing in waterfall, v model and agile
to learn more and also if you want to look differently
back and check.
DEEPTI BHOVI
Whenever we are doing data migration to Third Party system which
includes a set of activities (Creation, Updation through API)
As a part of Migration activity once testing with data samples is done.

We have to mock the complete activity of migration in the test
environment by taking the snapshot of real data from production
and test it. This plan can help us to unveil some hidden bugs that can
be related to the performance of the application, unknown
behaviour of API's based on the volume of data, etc.
ANAND JAYARAM
While implementing a solution based on someone's else advice or from
blogs/ stack overflow answers, remember that the solution would have
been based on what "their problem" was "at that time".
You wouldn't know what challenges they had later after implementing this
solution, whether they are still using this solution etc.
Find multiple solutions in for your problem. Understand the concepts

from these. Tweak the solution to your problem and then implement.
ADEBAYO JACOBS-AMOO
SUNNY BHATIA
Pay attention to details no matter how minute. We
Throw away your To-do list. Schedule your
don't usually start afresh each new day, we often
daily tasks, prioritize them on your daily
continue from where we stopped. Remember
calendar
where you were and where you are, it is important.

BRIJESH DEB
As testers our job is not done when a product is deployed to production.
Seek feedback from production, analyse customer reviews and feedback,
monitor the application in production and look for defects and potential
areas of improvement. All of these will feed into any upcoming release
and will enhance your test basis. It will show the business and your
customers that you really care.
SHAILESH GOHEL
Always try to reproduce any observation (UI or Functional) one or to times
before raising it as a bug. Its helps to avoid un necessary "Its working on my
machine" kinda argument. Sometimes you may get some observation due
to network glitch, browser cache etc.
RICHARD FORJOE
When doing automation/testing for an
app/system which does api calls, find out how As a tester never get complacent even if you are
it stores the data after getting a response eg working on the product for a long time. Always
Local Storage. Mock this data directly there be vigilant you will always get something new
instead of the api to reduce the need to make every time you explore it.
unnecessary api calls
What’s In a "Testing Strategy?"
Simply put, a testing strategy is a plan of how you will accomplish quality
goals through a set of activities. While a testing strategy includes
technologies used to perform testing, if the answer to a testing strategy is
“we use Selenium and Jenkins”, there is a fatal blind spot to the
importance of including “why” and “for whom” in the existing definition of
strategy.

MUKTA SHARMA
Learn the difference between “Authentication” and “Authorisation”
while working with APIs.
Authentication - Validating a user or a service. It refers to proving

correct identity. Example: Checking the ID card of Amazon
employee before handling him the return parcel at your door. You
cannot handover your parcel to any unknown person, right?
Authorisation - It refers to allowing a certain access/action like what

access do you have to avail the services? Or the access to a certain
resource on a server.
Example: You are not authorised to take premium benefits of a site

unless you are paid member.
JYOTI MISHRA
Earlier if I decided to learn anything new, I used to read about it, watch
multiple videos on same topic but in doing so I found it was very slow
process and it took some time before I started contributing.
This is what I do now and have found it effective.
I go for crash course videos, with these I get basic understanding and get
familiarised to terms. As I get basic understanding, I start picking task and
now further R&D depends on problem statements which I face while working
on those task.
I think this is what we call on the Job training :)
SUNNY BHATIA
𝐄𝐟𝐟𝐞𝐜𝐭𝐢𝐯𝐞 𝐂communication
People who miss communicating well are due to the level
difference.
3 levels -
1. Technical level - Here people mostly talk in technical
fashion,
2. Management level - Here people talks in terms of process,
measurements, standards, etc.
3. Executives level - Here talk is done in terms of money.
So the tip is while talking to other level people, understand
their level first and talk in their language. This will assist you
in putting your point clearly

ANAND JAYARAM
GOPAL CHOUBEY
In the most dysfunctional organisations,
signalling that the work is being done becomes Work regularly on upgrading your domain
a better strategy for career advancement than knowledge, as its a crucial factor in achieving
actually doing work. If this describes your improved test coverage
organisation you should quit now- Peter Thiel
FAIZ MODI
If you want to be more knowledgeable then don't be that
person who keeps the knowledge with him/her only and
doesn't share it with others in fear of others becoming more
knowledgeable than yourself.
Because it works exactly the reverse way, the more you share
your knowledge with others the more knowledgeable you
become in one or other way.
ANKITA BASU
Learn to say NO with proper clarification and propose your idea to the
business. Most of the times, requirement documents include test
scenarios and not exactly test cases. A tester's 'out-of-the-box' thinking
can add value to specific test cases and help prepare an user friendly
product for the future.
FAIZ MODI
When estimating efforts for any task, always ANKITA BASU
keep some buffer for the
Revise what you already know.
unknown/unexpected challenges which may
significantly impact the estimates.
GAURAV MISHRA
If time permits, plan and go for testing beyond the scope to find
the grey areas in the application/system.

SAMEER PURANDARE
Agile methodology/DevOps is more about culture rather than usage of

bunch of tools (Docker, Kubernetes, Jenkins etc..). Central philosophy is
delivering continuously and getting feedback continuously and improving
continuously. Understand this first. Tools are merely just catalysts to
inculcate such culture.
GAURAV MISHRA
Create a repository for the evidence of tests and related work. This can
not only always be beneficial for creating a comparison of any system
behaviour with past but also proves to be a strong reference for
referring the tests execution in past.
SUNNY BHATIA AHILESH MANICKAVASAGAN

Always have 𝐓𝐑𝐀𝐍𝐒𝐏𝐀𝐑𝐄𝐍𝐂𝐘 in your work by Quality can never be owned by a testing team.
proactively share your findings and seeking It involves everyone from management,
feedback on them. developers, business analysts and product
Nothing should be hidden as we are working owners. Try to build the right culture of quality
professionally for testers in your organization.

“Design is not just meant for developers. A good understanding of
design helps testers understand the product better and build
better tests.”
Brijesh deb

ANKITA BASU
It is more important to test negative scenarios.
Positive scenarios are always certain ones but the product validity goes
with the way negative scenarios are handled.
Be a passionate critic.
SHAILESH GOHEL
Learn to say No. Do not over commit anything. Instead its better to say that
you can not do all these work in given time, either you need additional
timeline or additional resource. Its okay to ask for additional resource
instead of getting fail to deliver, that to on the last day of the timeline.
SACHIN SHARMA
𝙋𝙡𝙖𝙣𝙣𝙞𝙣𝙜 𝙞𝙨 𝙞𝙢𝙥𝙤𝙧𝙩𝙖𝙣𝙩, 𝙛𝙤𝙡𝙡𝙤𝙬𝙞𝙣𝙜 𝙖 𝙥𝙡𝙖𝙣 𝙞𝙨 𝙣𝙤𝙩 𝙚𝙨𝙨𝙚𝙣𝙩𝙞𝙖𝙡: Most people
work on multiple projects, may have multiple matrixed managers, and
are involved with multiple teams. All of these commitments make it
critical to know where to spend time and energy for the best results.
And that's where the importance of effective planning comes into the
picture.
When working on the plan, it's important to first ask clarifying
questions about the purpose, goals, and targets the plan is designed
to achieve. As a next step, It is ideal to follow plans and ensure the
completeness of tasks as per planned timelines, but as we do not
know everything in advance and we do not have the capacity to plan
every step that we should be taking in the future, the most critical
thing to understand and accept is we should modify the plan as per
the current situations. Just for the sake of following a plan, we can not
do what is not right even though it was appropriate at the time of
planning.
Think about it.
𝙄𝙣 𝙨𝙝𝙤𝙧𝙩: We should remember Taylor's lesson - “Just because you
made a good plan, doesn’t mean that’s what’s gonna happen.”
AKASH ANAND
Share best testing practices/experience/ideas SHEELA S K
with others ::
We should not ignore timeouts in automation
This not only brings out the ideas to others but
runs, there may be hidden issues.
you also have a good chance of getting some
feedback.

ADEBAYO JACOBS-AMOO
A large aspect of what we do as testers are not written down (nor
follows any concrete written guidelines), hence treat every observation
as important. It might be nothing or something but don't be the sole
judge of that. Ensure the information is shared with the decision
makers and as early as possible.
JYOTI MISHRA
The error message which application throws on performing any invalid
action should be self explanatory .
Educate PM/ tech writer not to give generic error message else customer
might not understand what caused that error plus keep in mind
localisation and internationalisation as well for the error/warning text.
RICHARD FORJOE
BRIJESH DEB
if you don’t have the technical knowledge or in
When you are testing a product, understand
depth domain knowledge to test a product eg
who the users of the product are, follow the
Mainframe/Niche legacy system etc, identify
user journey, understand usage patterns and
who it’s SME’s/Users are in the business and
user behaviour. Focus on user experience.
coach/Support/Pair with them to do the testing.
This will help you design better tests.
Guide them
SACHIN SHARMA
Considering today's time and life style "𝘿𝙤𝙣'𝙩 𝙬𝙤𝙧𝙧𝙮 𝙖𝙗𝙤𝙪𝙩 𝙩𝙞𝙢𝙚
𝙢𝙖𝙣𝙖𝙜𝙚𝙢𝙚𝙣𝙩, 𝙨𝙩𝙖𝙧𝙩 𝙡𝙚𝙖𝙧𝙣𝙞𝙣𝙜 𝙨𝙤𝙢𝙚 𝙚𝙣𝙚𝙧𝙜𝙮 𝙢𝙖𝙣𝙖𝙜𝙚𝙢𝙚𝙣𝙩 𝙨𝙠𝙞𝙡𝙡𝙨."
This will definitely help in long run. I mean, All we struggled with, since long,
is having less time, and now when we all feel like having enough time, we
started facing lack of energy ( not talking about power or strength).
An intelligent mind is he who, in my opinion, is a master in an art of focusing
on how to optimize energy and stay connected with whatever he is doing at
particular moment carefully, attentively and thoroughly - be it work, family
or society.
SHAILESH GOHEL
Automation is not limited to automating your Functional or Regression
Test Suite. It's more than that i.e. Preparing Test Data, Setting up test
data on fresh environment, generating Test results and Matrices, Deep
diving through your logs etc. Automation will be even more useful in
those areas.

ADEBAYO JACOBS-AMOO
Dear Testers, you are the ultimate test tool. Any other tool is your
assistant and we sure have loads of them. This will guide you in knowing
how to deploy your 'assistants'.
ANJANA I V
Like CI CD CL(Continuous Learning) should be new KRA for every
tester, be it domain, product, testing technique, testing tool,
technology etc. In today’s world tester does multiple roles like BA,
DevOps, QA (manual/automation/performance/API/mobile), adding
one more layer to it not a rocket science at all. With this initiative
21days21tips great step is already taken, sharing knowledge & learning
from others experiences can help us inherit their wisdom and
knowledge.
Let us all head towards the learning curve!
DEEPTI BHOVI
With the arrival of micro services, the growth and adoption of API's have
skyrocketed. It becomes really necessary to have well-documented,
readable, maintainable, and intuitive API level documentation. As a QA
you should emphasize having such documentation which is easy to
understand, helps in debugging. The documentation is also beneficial for
Product Managers and Support teams where they exposure to various
endpoints of API.
JYOTHI MISHRA
We should try these invalid scenario, just to see how system handles
them. For effective testing, you can talk to dev and find out what are
the fields where validation is not added and design your cases
accordingly.
Also, you can tell PM to have some tip/instruction somewhere in the

page stating format, valid values if possible for these fields in a color
which is eye catching.

"Certification is a disciplined way of learning"-
The time requires to fix a defect in
Anonymous
production is 150 times the time
required to fix the same during But if the certification does not provide you the
requirements knowledge to become a better tester then it is just a
piece of paper which has no value.
BRIJESH DEB
𝑹𝑬𝑨𝑫
That's right... As a tester you must constantly read...
- Books
- Blogs and Articles
- Testing notes from self and other testers
- Product documentation
- Customer Feedback
- Product test results and reports
- Product defect history
- About the competitive products
- Release notes
- Posts and comments on social media
GAURAV MISHRA
ANKITA BASU I believe I draw my tip from here only. Work on your
patience level to perform any activity, be it testing,
Understand the difference between reading, writing or anything that really needs your time
static and dynamic testing. Knowing and attention. Without right patience in place, we can't be
exactly what to test, when and how affirmative for our approach leading to a desired outcome
is the key. and we may even miss what might be the most important.
SACHIN SHARMA
Lets me keep it simple today, here is a very very important tip and request
to all the testers our there. Do nothing, simply follow Naveen , Mukesh, and
Raghav. That's enough to stay ahead in game and see yourself growing
automatically.

RIDDHI SHAH
Do not get satisfied with what knowledge you have! Be always a
child where ever you reach in your career, and keep exploring
different areas.
If some one says testing has nothing to do, must say its deep
ocean and we have to dive in and always keep swimming deeper.
"Just keep working on your skills at any point of time."
Since the day I started learning testing, I am always surprised to

see new technologies and tools which I come across everyday
and trying to learn at least basic of that and then slowly going in
deeper when time permits.
BRIJESH DEB
𝐈𝐧𝐯𝐞𝐬𝐭 𝐢𝐧 𝐥𝐞𝐚𝐫𝐧𝐢𝐧𝐠
Just like you invest in stocks and properties for better living, INVEST IN
LEARNING. Participate in conferences, Meetups, workshops, webinars,
AMAs. Invest in books. Investment in learning makes you a better tester, a
better human being.
RIDDHI SHAH
It’s
good practice to learn to write/speak moral of stories, instead of
writing/telling full big stories!!
People (Either you take your office staff or in general as well) are busy
with their work and every time writing a long email or tell them big
stories, then chances are there, that in middle they may loose interest,
so its good practice to make it smaller and sweet.
Talk only context related stuff and make it short and simple.

“Tool tip: Build tools. Write your own. For yourself. This helps you
understand the end to end process of thinking building and
releasing software.”

JYOTI MISHRA
Few tips on database testing.
1. Verify that leading and trailing spaces are removed when saving to
database
2. Verify that your DB supports all your API's operation
3. Verify that sensitive data, such as user password are encrypted in the
database
4. Verify that the parameters set on the fields in the database match the
parameters in the API and UI
5.Verify that fields that are required in database are also required in the
API and UI
6. Verify that the data fields are of correct type
AKASH ANAND AHILESH MANICKAVASAGAN

"Software development skills" - The Testing is not a 9-5 job. Collaborate with
intersection of Core Testing skills and Test different testers apart from your office, attend
automation skills is - Test automation conferences, webinars, AMA sessions, learn and
Engineer. An SDET has to have development apply them because there is always something
skills along with testing skills. more to learn.
FAIZ MODI
Remember that as a tester your job is to communicate the information
as clearly as possible and try to convince/aware the team and
stakeholders for the consequences (especially the risks) something can
bring.
Now the call (and/or actions) which will be taken upon that can be based
upon it or can be altogether different than what you
communicated/suggested; and in either case it's absolutely fine.
No need to stress about it especially if it's the latter case.
And if possible try to have the communication in a written manner so

that it can be used later for reference if required.

BRIJESH DEB
While in sprint automation is a good idea, you must identify the tests in
the right layer to be automated. Without planning the tests in the right
layer, the automation effort would only seem like a huge mountain.
DIMPY ADHIKARY
If you need to test an application in a new domain, here are some
tips to start with:
1) Start with understanding the frequently used terminologies in the

domain. Make notes of the new terms with meaning when you come
across, for your future reference.
2) Find a mentor who has the knowledge, can be anyone in your

team/organisation/community. This will speed up the learning
process and you can make sure you are in right direction. Use your
leaning outcome from step 1 and go deeper into the specific focus
areas.
3) Time to identify the real users of your product and understand

how they will be using the it. Best way will be paring up with BA/sales
person to understand the real customer needs and come up with
critical user journeys.
4) Start adding the missing links between domain and technology

stack now. Time to work with your mentor again.
5)If the product is already available start exploring the same with the
knowledge you have from steps 1,2,3 and 4 and uncover the
remaining unknown areas.
By the end of step 5 you will have confidence on the new domain and
the product as a whole. Do not forget to document and share your
knowledge with others.
ADEBAYO JACOBS-AMOO
If you find yourself working on/talking/thinking more about your
#automationtools or #frameworks than the actual Product, you have
missed the Point. Time to refocus!

RIDDHI SHAH
Never hesitate to accept your mistake and Failure and still move on.
Its ok to make mistake and its ok to FAIL and learn from your own
mistakes. Nobody can be expert in each area. But that doesn't mean
that by keeping the fear of failure you do not add new skills.
Remember FAILURE can give the lessons, which SUCCESS cannot give!
SACHIN SHARMA
"𝗦𝘁𝗮𝗿𝘁 𝗮𝗻𝗱 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲 𝘄𝗿𝗶𝘁𝗶𝗻𝗴 𝗮𝗻𝗱 𝘁𝗲𝗹𝗹𝗶𝗻𝗴 about the testing actualities to the
world, do not let people assume that testing is easy, low grade, second
choice or less paid alternative to consider for career. Be proud of what you
are and what you are doing as a tester" :)
Remember, 𝙐𝙣𝙩𝙞𝙡 𝙩𝙝𝙚 𝙡𝙞𝙤𝙣 𝙡𝙚𝙖𝙧𝙣𝙨 𝙝𝙤𝙬 𝙩𝙤 𝙬𝙧𝙞𝙩𝙚, 𝙚𝙫𝙚𝙧𝙮 𝙨𝙩𝙤𝙧𝙮 𝙬𝙞𝙡𝙡 𝙜𝙡𝙤𝙧𝙞𝙛𝙮
𝙩𝙝𝙚 𝙝𝙪𝙣𝙩𝙚𝙧.
Be the lion and start writing/telling/sharing things !!
RIDDHI SHAH
I am getting many emails/messages for freelancing/remote work. So
would like to give some very useful tips, which I learned from my
experience.
1. Initial stage do not think about money and search for projects
according to your financial goals, instead consider it as long term goal
and start exploring areas of interest.
2. Be ready to always learn new skills either in QA/development/website
designing/Article writing and many other non-IT areas too.
3. Be ready to work independently, for e.g. if system has some issues or
you are not able to install certain softwares, then resolve by yourself.
4. Do not disappoint, if client doesn't select you or after selecting
suddenly decide to remove you from project due to many reasons,
instead take it as opportunity to learn new skills.
www.utest.com
www.testerworld.com
www.fiverr.com
www.guru.com
www.upwork.com
This list is never ending, but shared few, if anyone is aware of more
reliable websites, then please free to share , so others will get advantage
of it

A tester apart from his testing craft and automation skills should also
possess domain knowledge. The better the tester understands the
product the better one can test.
SUNNY BHATIA
Doing testing by the flow mentioned by the team is not always helpful.
Go against the flow and do your testing. Test for what
product/application is not supposed to do.
SOUVIK CHATTERJEE
It is always a good idea to revisit your regression suite after every
release.
Analyse which tests cases to include and which ones can be excluded.
Over time as the application grows and becomes more robust, some
functionalities may change while others might not be in use anymore.
So always make sure to keep the regression suite updated.
JYOTI MISHRA
Once we receive a feature from the developer, we should have a quick 15
minutes connect to go through the merge request and understand which all
files have changed and its correlation with the feature under development.
Advantages:
1. Uncovers hard-coded values: we should ask or mention if any hard-code

value would remain the same or needs to change when feature will go-live.
2. Uncovers environmental dependency: There are some features that work

based on environmental parameters e.g. creating batch of import file .
While testing ( tester-dev discussions), if we notice any such limit, then we
should understand how these dependencies are managed, i.e. is it through
a config file or through some DB parameters etc.
SHAILESH GOHEL
Always keep notes in form of hard copy book or in notepad application while
going through a KT session or any other learnings. Hand made notes are
always better than video recordings when you want to recall anything.

BALAJI SATHANAGOPALAN
Do research deeply about the domain that you are testing and also about software
testing.
ANAND JAYARAM
Computers serve us best when we use them to more efficiently and
accurately do what we already know how to.
In test automation vocabulary, if you automate BS, you get automated BS. So
make sure your tests are good enough before automating it.
SONAL GOSAVI
While re-testing of any bug test all the corner cases related to that bug
BRIJESH DEB
Remember automation is not limited to regression testing or conversion of
test cases into automated scripts. Even a simple script to generate test data
or format your test report adds value to your test automation capabilities.
VINAYAK TITTI
Test Automation tips: 1) Do feasibility analysis about the tool that is going to be used
before jump into automation.
2. Analyse the test cases that are automatable and repeated scenarios.
3. Create a reusable framework with Hooks, user-defined/helper functions, custom

reports, etc.,
4. Use Page Object Model to store page objects for ease of maintenance.
5. Store all strings or text in a json file or properties file for reusability instead of
hardcoding in the spec file.
6. Choose a build tool such as Maven or Gradle for managing the packages and auto-
build.
7. Health-check and update the scripts regularly as per CR.
8. Continuous testing plays a key role in regression to schedule nightly builds and
trigger notifications for failed builds and CI-CD integration.
9. Follow (Write Once Run Anywhere) principle - scripts should successfully run
without breakage on all browsers and all OS.

“The easiest way to get to get started with application security is by
asking your developers about Top 10 OWASP proactive controls.
Are you doing that?”
Santhosh Tuppad

SUNNY BHATIA
As a tester, do not hesitate to put and set the right expectations in front of
customers. Always bring clarity to the customer in terms of testing that what
can be done and what is challenging.
SACHIN SHARMA
"Improvement begins with "I". Focus on what you can improve in yourself
and in your work to be more impactful than earlier. This become
mandatory thing to do if you are leading group of people. "
ARPITA SWER
Always try to get the teams collective decision for progressing into common
goal. We know we cannot satisfy all. Balance is the harmony to #success.
INDU SHARMA
Make sure to use "sql Injection Datasets" from FuzzDB for testing the "data
Input" fields across your UI application for identifying the SQL injection
vulnerabilities.
Example : You can use the strings from this dataset to test if you can bypass
"User Name" and "Password" validation in your application.
RICHARD FORJOE
Find your growth zone in your current testing role, where you use your
strengths, you feel challenged or constantly challenge yourself, you’re excited
about what you’re doing, you feel some fear. Don’t stay in your comfort zone ,
least growth.
HIMEN PATEL
Use proper naming convention in test scripts so we can identify easily as when you
or other testers on the team are looking through the Test Case, it should be easy to
find out which Test Case is the one you need.

Always run sanity test soon after you get the fresh build, like how you quickly
glance at your pizza/food to confirm if it matches with your order as soon as it is
delivered to you. Showstopper bugs can be easily spotted during the sanity
check. If any bug found, this early finding would give a time for a dev to fix it.
ADEBAYO JACOBS-AMOO
Testers do not have the luxury of making assumptions so do not assume
anything. Also, Test the assumption of Others. The conversation is better
when you tell people what they will see if they do something a certain way
(you have done it and observed that behaviour) compared to telling them
they might see something if they do it a certain way (you assumed they
would). Let's do it!
SONAL GOSAVI
Follow up on issues pro-actively till closure
Eliminate waste to improve efficiency
In shifting left, teams see huge benefits such as finding bugs much earlier,
sometimes even before code is ever written. This results in a higher quality
of code and a far less expensive way in achieving such.” — Angie Jones
Know when to stop testing:: You can never finish testing, tester will keep suspecting
and doubting the developers code, always plan when to stop, better approach
would be to map the requirements to your test scenarios to prove 100%
requirement coverage (aka RTM), get the scope agreed and live stress-free.
If time permits in a sprint you can test beyond the scenarios planned.

PALLAVI RUNGTA
Know when to stop testing:: You can never finish testing, tester will keep
suspecting and doubting the developers code, always plan when to stop,
better approach would be to map the requirements to your test scenarios
to prove 100% requirement coverage (aka RTM), get the scope agreed and
live stress-free.
If time permits in a sprint you can test beyond the scenarios planned.
GANDHARV MADAN
“Software testers do not make software; they only make them better.” – Anonymous.
BRIJESH DEB
As a tester, always have the Test strategy in mind. If you don't have a test
strategy then make one now by collaborating with fellow testers,
developers, architects, product owners and other stakeholders. Don't just
look for a template because what works for others may not work for you.
So make your own.
MUKTA SHARMA
Instead of learning multiple tools/technology, focus on one and have strong
knowledge on that. Get in depth understanding of the related concepts. (Primarily).
Other areas you can start with basics/fundamentals then gradually improve. One can
not be an expert in all areas. All I mean to say is avoid jumping into race. Make a
secure place for yourself.
Let’s learn from each other and share our knowledge
MUKTA SHARMA
When you find a bug and developer says No and doesn’t accept it. Please do
“Risk/Impact analysis” first. What risk it can cause if it occurs in production? Can
it occur in real time? Can end user find such bug while performing so and so
scenario?
Needless to say, documentation of a defect is most important task any QA must

know. That’s it for today. Thank you!

RIDDHI SHAH
How much ever experience you have remember this, no one is expert in
any area, It just improves over the year of experience.
If you are tester that doesn't mean , you should feel low about it. There are
many tools and techniques which you should be always ready to explore
"Never set Limit to yourself!"
1. Functional Testing - Which all of us can do, that's what we believes, But I
would say It improves over the years. As a fresher if you can keep an eye on
10 issues, after 7-8 years of experience you can find loads of issues if you
are given the same product for testing. That is called learning and
improving yourself.
2. API Testing
3. Security Testing
4. Performance Testing
5. Database Testing
6. Accessibility Testing
7. Localization Testing
8. Different Device testing
This list never ends.........
ADEBAYO JACOBS-AMOO
Use #automation #tools to test your product, do NOT use your product to
test your automation tools framework. One is beneficial, the other is not!
SACHIN SHARMA
I think it is one of the most important practice that one should follow in
today's world of 𝙒𝙚𝙗 𝙥𝙤𝙡𝙡𝙪𝙩𝙞𝙤𝙣. Everyone is writing something and we all
are reading almost everything hence it is critical to analyse and realize
about what is right or what is just a smart arrangement of words to spread
lies/fakeness.
𝗦𝗼 𝗺𝘆 𝘁𝗼𝗱𝗮𝘆'𝘀 𝘁𝗶𝗽 𝗶𝘀 - "𝘉𝘦𝘧𝘰𝘳𝘦 𝘣𝘦𝘭𝘪𝘦𝘷𝘪𝘯𝘨 𝘪𝘯 𝘵𝘩𝘦 𝘤𝘰𝘯𝘵𝘦𝘯𝘵, 𝘱𝘭𝘦𝘢𝘴𝘦 𝘦𝘯𝘴𝘶𝘳𝘦 𝘸𝘩𝘦𝘳𝘦 𝘪𝘵
𝘪𝘴 𝘤𝘰𝘮𝘪𝘯𝘨 𝘧𝘳𝘰𝘮 𝘢𝘯𝘥 𝘸𝘩𝘰 𝘪𝘴 𝘵𝘩𝘦 𝘢𝘶𝘵𝘩𝘰𝘳/𝘱𝘳𝘰𝘱𝘢𝘨𝘢𝘵𝘰𝘳 𝘣𝘦𝘤𝘢𝘶𝘴𝘦 𝘪𝘵 𝘪𝘴 𝘵𝘩𝘦 𝘰𝘯𝘦 𝘸𝘩𝘰
𝘭𝘪𝘷𝘦𝘴 𝘪𝘯 𝘵𝘩𝘦 𝘩𝘰𝘶𝘴𝘦 𝘸𝘩𝘰 𝘬𝘯𝘰𝘸𝘴 𝘸𝘩𝘦𝘳𝘦 𝘵𝘩𝘦 𝘳𝘰𝘰𝘧 𝘭𝘦𝘢𝘬𝘴"
In short, "𝗖𝗵𝗼𝗼𝘀𝗲 𝘆𝗼𝘂𝗿 𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲𝘀 𝘄𝗶𝘀𝗲𝗹𝘆".
This matter is so serious and dangerous that in one of the very popular
Japanese proverb they say "𝘐𝘧 𝘺𝘰𝘶 𝘣𝘦𝘭𝘪𝘦𝘷𝘦 𝘦𝘷𝘦𝘳𝘺𝘵𝘩𝘪𝘯𝘨 𝘵𝘩𝘢𝘵 𝘺𝘰𝘶 𝘳𝘦𝘢𝘥, 𝘣𝘦𝘵𝘵𝘦𝘳
𝘯𝘰𝘵 𝘳𝘦𝘢𝘥"
Mind it !!!!!

SHAILESH GOHEL
Story can help you to decide a way to test the product but testing should
not be limited to a story. You can cover more edge cases if you test beyond
your story.
JYOTI MISHRA
Make sure you do result analysis of automation run and for every genuine failure, you
do the fix asap.
Here is how we learnt this tip:
We had marked few cases disabled as they were failing consistently and we forgot to
track the same via JIRA and missed fixing it.
After few days we got a high sev bug and lot of escalation from client due to this bug.
On retrospection we found that this issue could have been caught in automation
provided it was enabled.
From that day onwards we ensured that we did analysis of automation run and marked
them in below categories for finding trends in automation failure and getting them fixed
asap
1. Sync issue 2. Script Issue 3. App Issue 4. Configuration issue 5. Data Issue
These trends also helped us in understanding how to design the cases to ensure less
false failure.
So, if we wanted to teach anyone about importance of test design for automation script
we used to assign him/her this task for a month :)

“when you hear someone speak of “x testing”, where x is any word
or words, a good guess is that it means “testing intended to
examine the product according to some model of x”
James Marcus Bach

Remove dependencies to accelerate test
Testing is similar to art. It can never be defined by a standard process. Each tester
have to build their own craftsmanship.
Hence never fall into trap of some predefined testing process.
How one can build their own Craftsmanship is by experimenting with the product,
with the help of heuristics build by great testers and collaborating with fellow testers.
Time might sound crazy, but it will be fun: If you want to perform real user
testing before deployment, visit places where you can meet those real users
of similar app/web apps, handover the device and watch what they do with it,
see if they are able to navigate through the user journey.
When done, or before you get help give them a small gift/ buy a coffee to
recognize their time (Of course it should be project funded)
MANSOOR SHAIKH
Be realistic with your estimates. Add buffer time. I have burnt my fingers several
times by being optimistic when it comes to estimation. Take time. Say no (a lot). Stay
focused on what you aimed for. There are too many distractions which will deviate
you and will eventually make you miss deadline.
ADEBAYO JACOBS-AMOO
Use #automation #tools to test your product, do NOT use your product to
test your automation tools framework. One is beneficial, the other is not!
BRIJESH DEB
As testers when you get your requirements, focus on testability... Collaborate with
stakeholders, developers and business and ensure that the requirements are indeed
testable. Requirements that are not testable often lead to poor products

SACHIN SHARMA
"𝑭𝒐𝒄𝒖𝒔 𝒂𝒏𝒅 𝒑𝒓𝒊𝒐𝒓𝒊𝒕𝒊𝒛𝒆: 𝘐𝘵'𝘴 𝘦𝘢𝘴𝘺 𝘵𝘰 𝘨𝘦𝘵 𝘤𝘢𝘶𝘨𝘩𝘵 𝘶𝘱 𝘪𝘯 𝘣𝘶𝘴𝘺-𝘯𝘦𝘴𝘴. 𝘔𝘦𝘦𝘵𝘪𝘯𝘨𝘴 𝘤𝘢𝘯
𝘲𝘶𝘪𝘤𝘬𝘭𝘺 𝘧𝘪𝘭𝘭 𝘺𝘰𝘶𝘳 𝘥𝘢𝘺, 𝘢𝘯𝘥 𝘦𝘮𝘢𝘪𝘭𝘴 𝘢𝘳𝘦 𝘦𝘯𝘥𝘭𝘦𝘴𝘴. 𝘐𝘯𝘵𝘦𝘳𝘳𝘶𝘱𝘵𝘪𝘰𝘯𝘴 𝘧𝘳𝘰𝘮 𝘱𝘦𝘰𝘱𝘭𝘦 𝘢𝘯𝘥
𝘱𝘳𝘰𝘣𝘭𝘦𝘮𝘴 𝘭𝘢𝘳𝘨𝘦 𝘢𝘯𝘥 𝘴𝘮𝘢𝘭𝘭 𝘢𝘳𝘦 𝘤𝘰𝘯𝘴𝘵𝘢𝘯𝘵. 𝘏𝘰𝘸 𝘵𝘰 𝘮𝘢𝘯𝘢𝘨𝘦 𝘵𝘩𝘦𝘯 ?. 𝘏𝘦𝘳𝘦 𝘪𝘴 𝘢 𝘵𝘪𝘱 -
𝘐𝘥𝘦𝘯𝘵𝘪𝘧𝘺 𝘵𝘩𝘦 𝘵𝘩𝘳𝘦𝘦 𝘵𝘩𝘪𝘯𝘨𝘴 𝘺𝘰𝘶 𝘯𝘦𝘦𝘥 𝘵𝘰 𝘢𝘤𝘤𝘰𝘮𝘱𝘭𝘪𝘴𝘩 𝘵𝘰𝘥𝘢𝘺. 𝘞𝘩𝘢𝘵 𝘥𝘰 𝘺𝘰𝘶 𝘯𝘦𝘦𝘥 𝘵𝘰
𝘮𝘰𝘯𝘪𝘵𝘰𝘳? 𝘛𝘢𝘬𝘦 𝘵𝘪𝘮𝘦 𝘵𝘰 𝘪𝘥𝘦𝘯𝘵𝘪𝘧𝘺 𝘱𝘳𝘪𝘰𝘳𝘪𝘵𝘪𝘦𝘴, 𝘳𝘦𝘷𝘪𝘦𝘸 𝘵𝘩𝘦𝘮 𝘢𝘨𝘢𝘪𝘯 𝘸𝘩𝘦𝘯 𝘺𝘰𝘶 𝘧𝘪𝘯𝘢𝘭𝘪𝘻𝘦
𝘢𝘯𝘥 𝘵𝘩𝘦𝘯 𝘩𝘢𝘷𝘦 𝘴𝘰𝘮𝘦 𝘸𝘢𝘺 𝘵𝘰 𝘵𝘳𝘢𝘤𝘬 𝘵𝘩𝘦𝘮. 𝘌𝘷𝘦𝘯𝘵𝘶𝘢𝘭𝘭𝘺 𝘦𝘷𝘢𝘭𝘶𝘢𝘵𝘦 𝘵𝘩𝘦 𝘰𝘷𝘦𝘳𝘢𝘭𝘭
𝘢𝘤𝘤𝘰𝘮𝘱𝘭𝘪𝘴𝘩𝘮𝘦𝘯𝘵 𝘰𝘧 𝘵𝘩𝘦 𝘥𝘢𝘺 𝘢𝘯𝘥 𝘬𝘦𝘦𝘱 𝘱𝘳𝘢𝘤𝘵𝘪𝘤𝘪𝘯𝘨 𝘵𝘩𝘪𝘴 𝘴𝘢𝘮𝘦 𝘩𝘢𝘣𝘪𝘵 𝘦𝘷𝘦𝘳𝘺 𝘥𝘢𝘺. "
In short: 𝗦𝘁𝗮𝘆 𝗮𝗯𝗼𝘃𝗲 𝘁𝗵𝗲 𝗳𝗿𝗮𝘆 𝘁𝗼 𝗳𝗼𝗰𝘂𝘀 𝗼𝗻 𝗜𝗠𝗣𝗢𝗥𝗧𝗔𝗡𝗧 𝗣𝗥𝗜𝗢𝗥𝗜𝗧𝗜𝗘𝗦.
MUKTA SHARMA
Please do NOT lose hope after failure/rejection in interview. You have tried your best.
One, two or Infact three interview rejections does NOT define you. Learn to accept
the rejection. But, in a positive way.
Learn from your own mistakes. Revise your interview questions and observe the
areas where you lacked. Could it have been better? Can you work on those areas
now? Can you improve? Comment below and tell me. Work on yourself more than
you did yesterday. Right opportunity is waiting for you right there. ✨
Keep going! Keep your focus. Don’t let negative thoughts divert you from your goal.
You are about to get the job which you dreamt of. All the very Best!
RIDDHI SHAH
Build a strong professional network via LI, Twitter and even Telegram.
Join different communities, and try to participate in different activities

performed by any community.
ADEBAYO JACOBS-AMOO
Don't limit your test execution to your test cases alone, allow yourself some time to
wander around in the application/system under test and do some off the script
exploratory tests. You might just catch some surprises early. Let's go!

JYOTI MISHRA
Try to have DB assertions in your automation script. In past we have found
few bugs via automation just because we had added DB assertion in our test
script.
Sharing an interesting bug which we found via automation because of this tip.
For air booking there was a particular table where all the flight detail used to
get saved and this was one of our very early test cases which we had
automated as manually verifying same required lot of data creation and
steps. And it's been years since any development was done around this
feature. Later there were some refactoring done and in its impact area dev
mentioned to validate this scenario. We decided to leverage automation
script for verification as unfortunately existing team had less idea about this
feature.
On running automation we saw all UI verification passed but db verification

failed.
When we did result analysis of failed cases we found that data was being
saved in different db column which was not accepted.
SHAILESH GOHEL
User appropriate Tags in your Jira Ticket/Defect/Test Case/Task. This will help
fetching historical data easily, creating status report, dashboard etc.
Example: While writing Test Cases, if you are adding labels like Sanity, Regression,
Automation-Candidate, Automation-Pending etc. whenever you want to get number
of Sanity Test cases which are yet to automate or number of automated regression
test cases, you can easily fetch those.

SACHIN SHARMA
"𝗕𝗲 𝗖𝗼𝗮𝗰𝗵𝗮𝗯𝗹𝗲: Being coachable means being eager and open to seek and
receive feedback and advice. Most people love to help others prosper and
grow, but they are hesitant to provide feedback when they do not perceive
openness. Everyone needs feedback to perform better now and to build a
career for the future.
Coachable people know they don't know everything. They recognize they may
have personal blind spots. They assume positive intent. They learn to assess
the value of the feedback—separating the worthwhile from the trivial. Then
they act on what's worthwhile. Above all, they are appreciative of feedback to
help them reach their full potential."
In short: 𝘽𝙚𝙞𝙣𝙜 𝙘𝙤𝙖𝙘𝙝𝙖𝙗𝙡𝙚 𝙞𝙨 𝙖 𝙢𝙞𝙣𝙙𝙨𝙚𝙩 𝙩𝙝𝙖𝙩 𝙡𝙚𝙖𝙙𝙨 𝙩𝙤𝙬𝙖𝙧𝙙𝙨 𝙚𝙭𝙘𝙚𝙡𝙡𝙚𝙣𝙘𝙚.
Automation sometimes is considered as hit on run button and provide the results.
But it seldom works like that. For an automation script to work, it also depends on
the below factors apart from the quality of script
1.The application environment performance should be good to avoid loading or sync

issues.
2.The cloud machines used for execution should have required hardware
configuration to run scripts.
2.The test data should be checked every time a test suite is run. Even if the data is
reusable, it should not be reused after certain amount of time as it could lead to
performance issues.
3.The periodic maintenance of script often underrated many times has to be done.
4.Finally automation is automation it is not automatic it can never replace the human
part of testing.

RIDDHI SHAH
Before starting automating any product/Features of product,
1. Take time to discuss with QA Team to understand the product features
2. Take time to discuss with your manager and Team Lead that why we are
going to automate the product/Part of product?
3. Take time to divide the test cases which can be automated and which can
not be automated , other wise at later stage, once we have automated a
scenario/a feature, we will realise that it was wasting of time to automate a
particular feature/test case due to so many reasons like...
------the test script has lots of dependencies, so to execute them in framework

make other test cases fail
------the test script need dynamic set of data, where as all other test cases
need fix set of data, and vice versa so while executing them together it may
fail
4. If automation team is new to the product/feature, its good practice to

manually execute few scenarios, instead of jumping in to automation.
BRIJESH DEB
When doing exploratory testing, always have an objective (which may not be the
same as an expected result). Remember exploratory testing is not about random
clicks. So organize your ideas and have a strategy.
FAIZ MODI
If you are a Tester, you have to be technical regardless of you coming from
tech or non-tech background or you are dealing with test automation or not.
So rather than staying afraid of it, start learning about the technical side of
things.
GAURAV MISHRA
Engage in discussions which don't even seem relevant for your role but is part of
your execution project, since you never know when you may come across some
insights which can hold utmost importance.

RAZA SOHAIL
ANKITA BASU Exploratory testing is a sight for sore eyes, particularly when testing
Apply Heuristic. broad domain softwares with poor code architecture. Before
beginning testing of a feature, it is always nice to spend 5-10
minutes writing 'exploratory actions' for a test scenario and then
explore the way. Test Rail is preferred choice for documentation.
ADEBAYO JACOBS-AMOO
If you feel tired, unproductive or getting worked up because something is not
working - take a walk, give yourself a break. Make a cup of tea or something,
step away from your desk. Completely abandon the task you are doing and
totally distract yourself for a few minutes. When you are able to focus again,
that is when you should continue.
VINAYAK TITTI
“Testing team to collaborate with all the stakeholders early. ”In all levels of the
software development lifecycle, it’s better QA should involve from the
beginning of the development process.
When it comes to the traditional approach, testing starts after development

done, but in Agile, requirements change at a rapid pace, it’s always good
practice QA’s to involve from an early stage of a life cycle — Requirements
gathering, Design phase, and Development.
“Defect prevention is better than Defect detection”.

“Sometimes your train is going to take longer than others but
what’s important is you keep driving it, is the destination still
serves you. Keep the fuel going, keep the momentum up !”
Aprajita Mathur

ADEBAYO JACOBS-AMOO
Advertise your skills always (especially if you are out of work or looking to
switch
jobs). Your skills should be out there, not your responsibilities or your
personality. Think about the interview question "Tell me about yourself" and
let your profile answer that at all times.
SACHIN SHARMA
This time my tip is inspired by IPL Cricket, It is very effective tip. Try this : "𝗜𝗳 𝘆𝗼𝘂 𝗮𝗿𝗲
𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗶𝗻 𝘀𝗰𝗿𝘂𝗺 𝘁𝗲𝗮𝗺𝘀, 𝗵𝗮𝘃𝗲 𝟮 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝘁𝗶𝗺𝗲𝗼𝘂𝘁𝘀 𝗮𝐬 𝗽𝗮𝗿𝘁 𝗼𝗳 𝘆𝗼𝘂𝗿 𝗰𝗲𝗿𝗲𝗺𝗼𝗻𝗶𝗲𝘀, 𝟭𝘀𝘁
𝗼𝗻𝗲 𝗶𝘀 𝗿𝗶𝗴𝗵𝘁 𝗮𝗳𝘁𝗲𝗿 𝟰 𝗱𝗮𝘆𝘀 𝗳𝗿𝗼𝗺 𝘀𝗽𝗿𝗶𝗻𝘁 𝘀𝘁𝗮𝗿𝘁𝘀 𝗮𝗻𝗱 𝟮𝗻𝗱 𝗼𝗻𝗲 𝗶𝘀 𝗷𝘂𝘀𝘁 𝗯𝗲𝗳𝗼𝗿𝗲 𝟰 𝗱𝗮𝘆𝘀 𝗼𝗳
𝘀𝗽𝗿𝗶𝗻𝘁 𝗲𝗻𝗱𝗶𝗻𝗴."
Strategic timeout, is a short and effective time wherein teams can analyse the
current situation and adapt modified strategies (or carry-on same strategy with
more confidence after re-evaluating things) so that team is focused and assured
about the accomplishment of Sprint goal. Cricket lovers can easily understand and
ratify this very well. :)
MUKTA SHARMA
Whenever you learn anything new, you must share it with others. There
are 2 benefits of doing this:
1. You will remember the concept in long run.
2. When sharing with others, you will get new thoughts to listen to, new
ideas to implement and new ways to improve or increase your
knowledge.
MURALI DOMDA
1) Instead of automating look and feel of your application, Prioritize automating
critical business value cases
2) Automate API tests instead of UI layer tests to bring down execution time and
maintenance costs
BRIJESH DEB
𝐀𝐬 𝐚 𝐭𝐞𝐬𝐭𝐞𝐫, 𝐚𝐥𝐰𝐚𝐲𝐬 𝐟𝐨𝐜𝐮𝐬 𝐨𝐧 𝐂𝐈/𝐂𝐃 𝐟𝐨𝐫 𝐬𝐞𝐥𝐟.
We must strive to be better versions of ourselves as testers everyday so

focus on how we can get better at what we do and how we do it. And
that's why we must Continuously Improve and Continuously Develop our
skills, knowledge and experience.

SHEELA S K
Instead of doing performance testing after the functional testing, check for
performance issues from the start of the cycle:
Instead of not only thinking about whether a test passes or meets the
requirements, think about whether the end user will be delighted with the
performance of the feature. See the app through the end user eyes.
Check performance throughout the cycle. Think about all of the areas that need
to address performance. Ask if the requirements include the right performance
criteria.
As we learn to apply performance to a given situation, we will definitely see areas

where the team is not considering performance. Since the whole software
development life cycle is considered, we aren't limited to thinking just about the
testing phase.
JYOTI MISHRA
Want to avoid Dev Vs QC Situation. Here is what you can do.
1. If you have any checklist, share it with Dev.
2. Make sure you add details like steps to reproduce , actual and
expected result and any other info you can while opening a bug
3. Always focus on bug and not the person
4. Be informed about development practices/architecture to have

meaning full conversation. I have come across developer who share lot
of details about the code if they see you understand stuff and are
interested in knowing how things work
5. Most of organisation have concept of Pat on the Back, Thank You

Award etc, make sure you nominate your developer for all the good work
person has done.
FAIZ MODI
To do test automation for an application effectively, one first needs to know about
how the application (and its different components) works and/or what it's
supposed to do.

RICHARD FORJOE
Know your API formats and their differences as this impacts how you
approach
testing them - There’s REST(scheme|json) , SOAP(wsdl|xml),

Graphql(json).
Be aware of differences between System, Process and Experience api’s.
Google is your friend
GAURAV MISHRA
Don't be afraid to ask for help if any of your commitment has gone beyond
timelines for any reasons. Always remember that a known delay is much better
than a last minute shocker.
ANKITA BASU
We can't automate 100% of a system. Proficient manual testing is
mandatory even after automation.
Don't get into trap of fancy designations for testers provided by the organisations.
Always remember whatever designation you are given. Your primary role will be
tester
SUNNY BHATIA
While focusing on your testing, do not allow social media or spam emails
to
interrupt your workflow. Schedule and manage your time for responding
to
such stuff.

JENCY STELLA
It's Day-21 marking the last day of the fantastic drive. Got to know many great
and interesting tips past 21days...
Towards the end of this chain one tip from end too...for the Last Day....
although my first post in this community chain.
Learning is a lifelong process, it is a self-directed and self-paced journey of

discovery. The purpose of learning is not to arrive at a particular level of
proficiency. As long as we live, most people are continually learning, and the
journey never ends. The concept of continuous learning is even more pertinent
when it comes to the constantly evolving world of Technology where new
techniques and concepts are introduced nearly every day. Enjoy Learning :-)
SACHIN SHARMA
"𝙁𝙤𝙘𝙪𝙨 𝙤𝙣 𝙩𝙝𝙚 𝙦𝙪𝙖𝙡𝙞𝙩𝙮 𝙤𝙛 𝙩𝙝𝙚 𝙥𝙧𝙤𝙘𝙚𝙨𝙨 𝙖𝙣𝙙 𝙮𝙤𝙪𝙧 𝙥𝙧𝙤𝙙𝙪𝙘𝙩 𝙦𝙪𝙖𝙡𝙞𝙩𝙮 𝙬𝙞𝙡𝙡 𝙗𝙚 𝙩𝙖𝙠𝙚𝙣
𝙘𝙖𝙧𝙚 𝙖𝙪𝙩𝙤𝙢𝙖𝙩𝙞𝙘𝙖𝙡𝙡𝙮, make sure about the enhancement of agility in your
process as much as you can. "
𝘈𝘴 𝘱𝘦𝘳 𝘵𝘩𝘦 𝘛𝘘𝘔 (T𝘰𝘵𝘢𝘭 Q𝘶𝘢𝘭𝘪𝘵𝘺 M𝘢𝘯𝘢𝘨𝘦𝘮𝘦𝘯𝘵) 𝘵𝘩𝘦 𝘲𝘶𝘢𝘭𝘪𝘵𝘺 𝘰𝘧 𝘺𝘰𝘶𝘳 𝘱𝘳𝘰𝘥𝘶𝘤𝘵 𝘪𝘴
𝘨𝘦𝘯𝘶𝘪𝘯𝘦𝘭𝘺 𝘥𝘦𝘵𝘦𝘳𝘮𝘪𝘯𝘦𝘥 𝘣𝘺 𝘵𝘩𝘦 𝘲𝘶𝘢𝘭𝘪𝘵𝘺 𝘰𝘧 𝘵𝘩𝘦 𝘱𝘳𝘰𝘤𝘦𝘴𝘴 𝘵𝘩𝘳𝘰𝘶𝘨𝘩 𝘸𝘩𝘪𝘤𝘩 𝘪𝘵 𝘪𝘴 𝘱𝘳𝘰𝘥𝘶𝘤𝘦𝘥
𝘢𝘯𝘥 𝘩𝘦𝘯𝘤𝘦 𝘱𝘳𝘰𝘤𝘦𝘴𝘴 𝘪𝘮𝘱𝘳𝘰𝘷𝘦𝘮𝘦𝘯𝘵 𝘴𝘩𝘰𝘶𝘭𝘥 𝘣𝘦 𝘵𝘩𝘦 𝘱𝘳𝘪𝘮𝘢𝘳𝘺, 𝘳𝘢𝘵𝘩𝘦𝘳 𝘮𝘢𝘯𝘥𝘢𝘵𝘰𝘳𝘺 𝘧𝘰𝘤𝘶𝘴
𝘧𝘰𝘳 𝘵𝘩𝘦 𝘤𝘰𝘮𝘱𝘢𝘯𝘪𝘦𝘴 𝘸𝘩𝘰 𝘢𝘤𝘵𝘶𝘢𝘭𝘭𝘺 𝘤𝘢𝘳𝘦𝘴 𝘢𝘣𝘰𝘶𝘵 𝘵𝘩𝘦 𝘲𝘶𝘢𝘭𝘪𝘵𝘺 𝘰𝘧 𝘵𝘩𝘦𝘪𝘳 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘴.
ADEBAYO JACOBS-AMOO
Getting over the finish line is not usually the end, there is always more so apply
the knowledge gained from all the tips for the past 21 Days and let them guide
you. We are a community and you can reach out to the author to get more
perspective from them - Use it!
Today being the last day of #21days21tips should not stop you applying those
nuggets you have gained over the past 21 days of #21days21tips to what you
do, and it is also no the end of teaching so don't stop dropping tips for others to
learn from.
SUNNY BHATIA
In testing, Do not jump to start testing as soon as you get information.
Its better to SLOW DOWN.
Take some time in understanding the information deeply, analyse the events that
will come in flow and then go about it.
The better you understand it, More it will be beneficial in long run

TREVOR MALGAS
In testing, Do not jump to start testing as soon
JYOTI MISHRA
It's day 21 of the initiative! Remember my #Day 1 tip ( Just Do it).
On #Day21 I would like to leave you with one of important lesson which I learnt
very late in my career. Don’t let anyone define what you can and you can't do. Yes,
it may take time initially as what you are trying to do is not your strength yet if you
continue focusing on yourself, you will be able to convert your weakness to
strength.
So, JUST DO IT!
JYOTI MISHRA
We redesigned our application and assumed that user will access the
application in normal flow i.e he/she will login and access different tabs of
application which will have redesigned pages BUT when feature went live
we started getting escalation, that for client page is not opening. We were
unable to reproduce the same scenario in production's test account as we
were accessing the application in the way I mentioned above.
On further discussion with client we got to know that they had bookmarked
some of frequently used pages and now when they were accessing those
page they were seeing issues after login and user were being redirected to
overview page rather then page which they had book marked.
Tip- If we will focus on testing of the product w.r.t what is given in

requirement, we will always miss these kinds of issue.

ARAVIND M
Sometimes it happens that we testers are not involved from day 1 of the
project initialization phase. It can be due to any reason like Management is
not willing to involve testers or in your organization this culture is pre-existing
from long time and no one in your team has voiced their opinion.
Whatever may be the reason always be very proactive and try to be involved
in every phase of project life-cycle. Participate in all the requirement
meetings, brainstorming sessions, development code review. Ask questions,
give suggestions and challenge the assumptions. Don't have any of your
queries unanswered or not discussed and regularly re-evaluate your
assumptions regarding the product.
The more you know about the product the better you can test the product.
SUNNY BHATIA
In testing, Do not jump to start testing as soon as you get information.
Its better to SLOW DOWN.
Take some time in understanding the information deeply, analyse the

events that will come in flow and then go about it.
The better you understand it, More it will be beneficial in long run

What's the goal of your bloody test suite.
"Under no circumstances, should the goal of running a test

suite be to have all the tests pass, being this, at most, the
result you may reasonably hope for.
The goal of running them is to discover, as soon as
possible, if there’s something wrong within the system which
needs your attention."
Ileana Belfiore

THARANI PARAMASIVAM
Thank you Test chat community for this 21 days learning tips which
gives us many insights. It's simply a superb initiative!
Shift left Testing- TDD
Do you come across such TDD implementation challenges and what

is your solution? Please add in the comment section. The listing
below generic challenges.
1.Testers are not familiar with the Unit Test tool
-We can contribute writing unit tests in plain English or pseudocode.
-Until QA learning the tool dev can help us to convert these into
executable unit tests.
2.Ratio of dev-test pair is not always 1-1 or no QA team Exists
-Have another team member play the role of a tester(PO/SE/Dev).
3.Dev and Test team use different tools for unit tests
- Negotiate and agree to use one tool to avoid duplication of effort.
- We end up with Angular for front-end - development, Jasmine -

unit test case development, karma - code coverage
FAIZ MODI
Testing is a very vast subject, and as a Tester it is good to
have basic idea about various areas/aspects of it.
However one needs to understand and accept that it's

impossible to be excellent at all those areas/aspects, so as
per your interest and other things find one or two areas and
focus on being excellent at those for better career growth.

There are always questions on the testing career scope for a tester especially in
a service-based company. Well a tester can have a great career path on his own
interest. Some of them are given below(not limited to)
1.Test Architect
2.Test Coach
3.Test Trainer
4.Testers can also become PO's/Scrum Masters/BA's
5.Finally a tester can also become a part of CXO's. They just need to have the
faith in themselves.
VIKRANT DESAI
MUKTA SHARMA
Always think out of the box and apply different
“Be Thankful, Be Grateful and stay Humble”! 🙏
negative scenarios while testing.
BRIJESH DEB
Sh𝐚𝐫𝐞 𝐲𝐨𝐮𝐫 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞
We learn everyday. However to grow our knowledge, we must share what

we
have learnt. The best way to learn is to teach someone else.
So don't be passive learners. Spread the light of your knowledge.
But before you spread that knowledge, validate your knowledge from
experts,
take their feedback and share.
This may be the last day of 21 days 21 tips but by now I hope you have
inculcated the habit of sharing which was the goal of the whole initiative.
Apply the tips and keep sharing, keep learning!

“Staying in present and staying focused has a great importance if
you are to test better. Therefore, whenever you come across some
boilerplate announcement from anybody in your network that says
“we don’t need testers or we are good with only automation” etc.,
read that by adding the prefix “in our context”…and maintain
peace of your mind for something more sensible and meaningful.
Lalit Kumar Bhamare

Authors
APRAJITA MATHUR JAMES MARCUS BACH

https://www.linkedin.com/in/apraji https://www.linkedin.com/in/james-bach-
tamathur/ 6188a811/
SANTHOSH TUPPAD LALIT KUMAR BHAMARE
https://www.linkedin.com/in/santh https://de.linkedin.com/in/lalitkumarbhama
re
osh-tuppad-338b7412
ERAN KINSBRUNER
ILEANA BELFIORE
https://www.linkedin.com/in/eran-
kinsbruner-4b47a81/ https://www.linkedin.com/in/ileanabelfiore/
PRADEEP SOUNDARARAJAN NAVEEN KHUNTETA
https://www.linkedin.com/in/tester https://www.linkedin.com/in/naveenkhunte
tested/ ta/
ABHINAY SARKATE
ADEBAYO JACOBS-AMOO
https://www.linkedin.com/in/abhin
aysarkate/ https://www.linkedin.com/in/jacobsamoo/
BRIJESH DEB AHMED ELSHEIKH
https://www.linkedin.com/in/brijes https://www.linkedin.com/in/ahmedmagdy
hkumardeb/ elsheikh/
ANAND JAYARAM ANHERUDH KAMATH
https://www.linkedin.com/in/anan https://www.linkedin.com/in/anherudh-
d-jayaram-736358b/ kamath/

ANIL KUMAR AAVULA ANIRUDDHA BISWAS
https://www.linkedin.com/in/anil- https://www.linkedin.com/in/aniruddha-
kumar-aavula-2506aab3/ biswas-122838182/
ANJANA I V ANKITA BASU
https://www.linkedin.com/in/anjan https://www.linkedin.com/in/ankita-basu-
aiv 803a48166/
APOORVA UTHRA ARAVIND M
https://www.linkedin.com/in/apoo https://www.linkedin.com/in/aravind-m-
rvauthra/ 3b3995b8/
ARPANA JINDAL
ARPITA SWER
https://www.linkedin.com/in/arpa
na-jindal/ https://www.linkedin.com/in/arpita-swer/
ARUNDATHI DM ASHUTOSH SINGH
https://www.linkedin.com/in/arun https://www.linkedin.com/in/ashutosh-
dathi-d-m-431b69148/ singh08/
AYAN PAUL BADARINATH BHASKARA
https://www.linkedin.com/in/ayan- https://www.linkedin.com/in/badarinath-
paul-b2a75127/ bhaskara-b85b5624/
BHAGYASHREE SHETH
https://www.linkedin.com/in/balaji
-santhanagopalan-82a63a108/ https://www.linkedin.com/in/bshree3191/
DEEPTI BHOVI DEZUL UDANI
https://www.linkedin.com/in/deept https://www.linkedin.com/in/dezul-udani-
i-bhovi-a7682457/ 25b259b2/

DHANALAXMI OTARI DIMPY ADHIKARY
https://www.linkedin.com/in/dhan https://www.linkedin.com/in/dimpy-
alaxmi-otari/ adhikary/
DWAIPAYAN BASU ER JAGRAT GUPTA
https://www.linkedin.com/in/dwai https://www.linkedin.com/in/er-jagrat-
payan/ gupta-3bb07126/
FAIZ MODI GANDHARV MADAN
https://www.linkedin.com/in/faiz- https://www.linkedin.com/in/gandharv-madan-
%E0%A8%97%E0%A8%A8%E0%A9%8D%E0%A8%A7%E0%A8%B0%E0
modi/ %A9%8D%E0%A8%B5-
%E0%A8%AE%E0%A8%A6%E0%A8%BE%E0%A8%A8-552891162/
GAURAV MISHRA
HARPREET GILL
https://www.linkedin.com/in/gaura
vmishra-uba/ https://www.linkedin.com/in/sandhk9/
HIMEN PATEL INDU SHARMA
https://www.linkedin.com/in/hime https://www.linkedin.com/in/indu-sharma-
n-patel-4271a787/ 22842427/
JAGADEESH JAYACHANDRAN JAYAKRISHNA BELLARY NUNNA
https://www.linkedin.com/in/jagad https://www.linkedin.com/in/jayakrishna-
eesh-jayachandran/ bellary-nunna-7b44a8188/
JENAB VOHRA JYOTI MISHRA
https://www.linkedin.com/in/jenab https://www.linkedin.com/in/jyoti-mishra-
-vohra-6aa969147/ 9563274a/
KISHORE AADADA KUMAR CHANDRASHEKAR APPA
https://www.linkedin.com/in/kisho https://www.linkedin.com/in/kumarchandra
re-aadada/ shekarappa/

LUKE LIU
MAHESH M
https://www.linkedin.com/in/lukey
uliu/ https://www.linkedin.com/in/mahesh-m/
MANSOOR SHAIKH MAYUR GAVHANE
https://www.linkedin.com/in/mans https://www.linkedin.com/in/mayur-
oorshaikh/ gavhane-87564b56/
MITALI DHAMALE MRUGANKA PATWARDHAN
https://www.linkedin.com/in/mitali https://www.linkedin.com/in/mruganka-
-dhamale-159b6346/ patwardhan-19a36865/
MUKTA SHARMA MURALI DOMDA
https://www.linkedin.com/in/mukt https://www.linkedin.com/in/murali-
a-sharma-sss4me2017/ domda-51166a150/
NAVEEN KUMAR H T NAVEEN P S
https://www.linkedin.com/in/saina https://www.linkedin.com/in/naveenperiya
veenht/ patna/
OMKAR CHEREKAR PALLAVI RUNGTA
https://www.linkedin.com/in/omka https://www.linkedin.com/in/pallavi-rungta-
r-cherekar/ 9bb13152/
PAVEL SAMAN PETER MOORE
https://www.linkedin.com/in/pavel https://www.linkedin.com/in/peter-moore-
saman/ 9045283/
PRABHU MOHAN PRABIR CHAKRABORTY
https://www.linkedin.com/in/prab https://www.linkedin.com/in/prabir-
humohan09/ chakraborty/

PRADEEP K C PRANITA CHIKORDE
https://www.linkedin.com/in/prad https://www.linkedin.com/in/pranita-
eepqa/ chikorde-251728101/
PRASAD GOKHALE
PRASHANT HEGDE
https://www.linkedin.com/in/prasa
d-gokhale-291941147/ https://www.linkedin.com/in/prazhegde/
PRAVESH BHATT
PRICILLA B
https://www.linkedin.com/in/prave
sh-bhatt-5b1b2a38/ https://www.linkedin.com/in/pricilla-b/
PRIYANKA K PRIYESH NAIK
https://www.linkedin.com/in/priya https://www.linkedin.com/in/priyesh-naik-
nka-k-2b086b168/ 4a51aa2b/
RACHANA BANERJEE RAHUL PATIDAR
https://www.linkedin.com/in/racha https://www.linkedin.com/in/rahulpatidar0
na-banerjee-7b20741b3/ 505/
RAKSHIT SANGANI RAZA SOHAIL
https://www.linkedin.com/in/raksh https://www.linkedin.com/in/raza-sohail-
itsangani/ a26b44171/
RICHARD FORJOE RIDDHI SHAH
https://www.linkedin.com/in/richar https://www.linkedin.com/in/riddhi-shah-
dforjoe/ 56581723/
RIJOY GEORGE
RISHI KUMAR
https://www.linkedin.com/in/rijoyt
george/ https://www.linkedin.com/in/reishitiwari/

RITIKA GHOSH
SACHIN SHARMA
https://www.linkedin.com/in/ritika-
ghosh-52aa84118/ https://www.linkedin.com/in/sachin-india/
SAGAR AGRAWAL SAHITHYA REDDY KADAPAKONDA
https://www.linkedin.com/in/sagar https://www.linkedin.com/in/sahithya-
-agrawal-a33771104/ reddy-kadapakonda-476031146/
SAMEER POTA SAMEER PURANDARE
https://www.linkedin.com/in/same https://www.linkedin.com/in/sameer-
er-pota-2885976/ purandare-815620103/
SAMREEN ADIL SANDEEP AGGARWAL
https://www.linkedin.com/in/samr https://www.linkedin.com/in/sandeep-
een-adil/ aggarwal-b034b96/
SANJAY Kumar
SHAILESH GOHEL
https://www.linkedin.com/in/chrop
ath-creator/ https://www.linkedin.com/in/shaileshgohel/
SHANTALA GONAKI SHEELA S K
https://www.linkedin.com/in/sgon https://www.linkedin.com/in/sheelasklinked
aki/ inprofile/
SHEFALI JAIN SHIVA PRASAD B M
https://www.linkedin.com/in/shefa https://www.linkedin.com/in/shiva-prasad-
li-jain-16336532/ b-m-211426141/
SHOBHIT KAUL
SK AMIR ULLAH
https://www.linkedin.com/in/shob
hit-kaul-74313a9/ https://www.linkedin.com/in/skamirullah/

SOMIL BAJPAI SONAL GOSAVI
https://www.linkedin.com/in/somil https://www.linkedin.com/in/sonalgosavi16
-bajpai-404225105/ 91/
SONU TITUS SOUVIK CHATTERJEE
https://www.linkedin.com/in/sonu- https://www.linkedin.com/in/souvik-
titus-88341287/ chatterjee-2967ba87/
SUDHAKAR SIVANNAGARI SUNIT BOSE
https://www.linkedin.com/in/sudh https://www.linkedin.com/in/sunit-bose-
akarsivannagari/ a5419028/
SUNNY BHATIA
SURESH DUBEY
https://www.linkedin.com/in/sunn
y-bhatia/ https://www.linkedin.com/in/suresh-dubey/
SWADHA SUNDAR PANDA SWAPNA SAMISHETTY
https://www.linkedin.com/in/swad https://www.linkedin.com/in/swapna-
hasundarpanda/ samishetty-39528913/
TEJAS AMBEKAR
https://www.linkedin.com/in/tejas-
ambekar-94a67b13/ https://www.linkedin.com/in/varadha2k/
VIKRANT DESAI
VINAYAK TITTI
https://www.linkedin.com/in/vikra
nt-desai-495854140/ https://www.linkedin.com/in/vinayak-titti/
VINIT AGRAWAL WAYNE ROSEBERRY
https://www.linkedin.com/in/vinita https://www.linkedin.com/in/wayne-
grawal/ roseberry-4758b0/

YOUSSEF TOUATI DEVIKRISHNA R
https://www.linkedin.com/in/youss https://www.linkedin.com/in/devikrishna-r-
ef-touati-09a93a158/ serving-notice-period-92085678/
PRAVEEN MATHEW ANIMESH MISHRA
https://www.linkedin.com/in/prave https://www.linkedin.com/in/animesh-
endvd/ mishra-044777126/
SAURABH SONI RAJESH KUMAR
https://www.linkedin.com/in/conn https://www.linkedin.com/in/rajesh-kumar-
ectsaurabhsoni/ 57178866/
TRISTAN LOMBARD SRI PRIYA P KULKARNI
https://www.linkedin.com/in/trista https://www.linkedin.com/in/sripriyapkulka
nlombard/ rni/
AVISHEK BEHERA PRABHAKARAN RAJENDRAN
https://www.linkedin.com/in/avish https://www.linkedin.com/in/prabhakaran-
ekbehera/ rajendran-8548109b/
ANKITA JOSHI
MOHANRAJ PANNEERSELVAM
https://www.linkedin.com/in/ankit
a-joshi-zippage/ https://www.linkedin.com/in/mohanrajps/
AHILESH MANICKAVASAGAN SHUBHAM KORI
https://www.linkedin.com/in/ahiles https://www.linkedin.com/in/shubham-
h-manickavasagan-8a82014b/ kori/
SHEETAL GADWAL AKANSHA BANSAL
https://www.linkedin.com/in/sheet https://www.linkedin.com/in/akanshabansa
al-gadwal-38b71860/ l02/

NAGASRUTHI JALIGAMA RAKSHA SHETTY
https://www.linkedin.com/in/naga https://www.linkedin.com/in/raksha-shetty-
sruthi-jaligama-761185192/ 89798081/
THARANI PARAMASIVAM JENCY STELLA
https://www.linkedin.com/in/thara https://www.linkedin.com/in/jency-stella-
ni-paramasivam-77b272188/ 88a41952/
RAM PRASATH ESWARASAMY SHASHANK CHATURVEDI
https://www.linkedin.com/in/ram- https://www.linkedin.com/in/chaturvedisha
prasath-eswarasamy-06152619/ shank/

The team that made this e-book
possible
Sahithya Reddy Kadapakonda Riddhi Shah
Arpita Swer Shailesh Gohel

About The Test Chat
Inspired by Dr. Steven Covey's book "The 8th habit" which is the sequel of the book "7
Habits Of Highly Effective People ", the idea of The Test Chat (TTC) was born. The ethos
behind TTC is Find your voice and help others find theirs
The idea of The Test Chat is based on the fact that testers do not have an opportunity or
platform to talk, discuss our problems, and overcome those challenges, practical situations,
misconceptions about testing, and most importantly have fun. We are all looking forward
to learning together and grow. The group resides on Telegram
We started our own YouTube channel The Test Chat solely with the intention of taking your
voice to the world. As a part of the YouTube channel, we have interviews with testers, video
bytes, AMAs, Panel discussions, meetups, and much more
Remember that even if you are someone who has begun his/her career just yesterday, you
have a story to tell and an experience to share so speak up and speak out.
The Test Chat can be found on the following platforms
This is an original contribution from the members of The Test Chat community for the testing community worldwide

Test Chat

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Test Chat

Uploaded by

Copyright:

Available Formats

THE TEST CHAT

This book is dedicated to all the frontline workers

21Days21Tips The Test Chat 1

21Days21Tips The Test Chat 2

21Days21Tips The Test Chat 3

21Days21Tips The Test Chat 4

In the knowledge industry, it is knowledge that is of utmost importance. What is

21Days21Tips The Test Chat 5

1) Solving logical puzzles

3) Writing daily journals

Go into the informal forums and search for it there.

21Days21Tips The Test Chat 6

1. I set a path and maven done

2. Again I set a new path for node js and it is done

21Days21Tips The Test Chat 7

PRASHANT HEGDE GAURAV MISHRA

21Days21Tips The Test Chat 8

21Days21Tips The Test Chat 9

ABHINAY SARKATE PRASAD GOKHALE

SONAL GOSAVI LUKE LIU

21Days21Tips The Test Chat 10

21Days21Tips The Test Chat 11

Before testing we need to understand the current system behaviours and

Sometimes we use the requirement docs as a user manual which is a not so

We need to think from an end user's perspective and possible approaches

21Days21Tips The Test Chat 12

BADARINATH BHASKARA PETER MOORE

21Days21Tips The Test Chat 13

21Days21Tips The Test Chat 14

21Days21Tips The Test Chat 15

21Days21Tips The Test Chat 16

SAMEER POTA ANIL KUMAR AAVULA

KUMAR CHANDRASHEKAR APPA

21Days21Tips The Test Chat 17

OMKAR CHEREKAR PRASHANT HEGDE

21Days21Tips The Test Chat 18

APOORVA UTHRA SUNIT BOSE

21Days21Tips The Test Chat 19

XMind is one such tool available.

1. You will retain what you learnt

21Days21Tips The Test Chat 20

21Days21Tips The Test Chat 21

21Days21Tips The Test Chat 22

21Days21Tips The Test Chat 23

Use automation to solve your problems such as reducing redundancy and

One must strive to test( I must say use) the product/software as if

GAURAV MISHRA AHILESH

21Days21Tips The Test Chat 24

It's good practice to do exploratory testing and go through each

Try to be self-reliant as much as possible.

21Days21Tips The Test Chat 25

21Days21Tips The Test Chat 26

Its should always be considered as crucial and a primary step to

21Days21Tips The Test Chat 27

Make sure we should have the Manual Test Cases handy

I think of this different - to which I suggest this silly analogy:

Home Owner: Build me an indoor swimming pool

Pool Builder: We cannot. Your house is on swampland and the pool

Pool Builder: I don't think lack of an indoor pool is your most

Like our house on a swamp, if a product cannot support automation,

21Days21Tips The Test Chat 28

Following logs of different forms and types are useful,

1. Test execution logs