You might a testing rock star in current organization or
team but what happens when you join a new team or organizations which are
disjoint in all means? That’s when challenges begin for a newbie. Here I mean work
style, understanding testing artifacts, test techniques & tool and this
list items will go on .Aligning our self to existing ecosystem will take some
time. But what if your supervisor assigns tasks right away??
Surfing internet helps to an extent but not always. Here are
few tips which you can implement right away to propel your learning series
Bug Repository -
Bug Tracking software is a vital source to detail about pattern of bugs
existed/exist on product. It also hints about areas where developers pay less
attention. In addition, here we can visualize protocols adhered in bug report.
How each component interact with each other and possible user flows can also be
derived from bugs. In short, it provides a flashback about project history and
of-course current status as well.
Pair-Wise Testing
- I would say this is the best technique to learn any testing techniques on
earth, but not sure why it is not encouraged in many firms. Along with
hearing, if you experiment the same with your co-worker anyone can easily
master any platform/stream. Seek a “buddy (mentor)” for you, till you are
familiar with project internals and post all your queries to him (Ensure you
don’t bug him!). For the following newbie make sure you act as “buddy” and contemplate
this as an opportunity to uncover new project landscapes.
Intranet Sources - Search
for Wiki or documents which exist in your organization. It could be any simple source,
yet if you think it will help any subsequent new comers (like you) just make a
note of its location and draft a wiki/document citing all these sources. Share
this document with rest of your team since good learners also contribute.
To learn something we need to be passionate about it,
nothing else. If you have any tips or comments, do share.
