Suggestions
Nilesh Jain
Experienced Software Tester - Accessibility Testing - Selenium Automation - UI/UX - Founder - Regression Testing
Nilesh Jain is the Founder and Chief Testing Officer of Vervali Systems Pvt Ltd, a software testing company he established in January 2010.2 With over 12 years of experience in software testing services, Nilesh has grown Vervali from a freelance operation to a global software engineering and testing firm.12
Vervali Systems, headquartered in Mumbai, India, employs more than 250 professionals and has worked with clients across 12+ countries.1 The company specializes in various types of testing, including web, mobile, API, accessibility, security, automation, and performance testing.2
Nilesh's expertise includes:
- Functional, sanity/smoke, system, integration, regression, usability, and other forms of testing
- Test planning and strategy
- Requirements review and estimation
- Test case documentation
- Bug triage and prioritization
- Test-driven development
- Test automation frameworks
- Performance testing
He has experience managing and collaborating with teams in the US, Australia, Croatia, Vietnam, and India.2 Nilesh is passionate about delivering high-quality, bug-free products and enhancing user experience for his clients.2
Before founding Vervali, Nilesh worked as a Senior Software Engineer at Accenture Services from July 2006 to December 2009, and as a Software Engineer at Infosys from October 2004 to June 2006.2
Nilesh holds a Bachelor's degree in Information Technology from the University of Mumbai.2
Highlights
Sometimes, the biggest journeys start with a simple suggestion from a friend.
Around 2010, I was happy with my job but looking for new ways to learn and challenge myself.
I was curious about freelancing, seeing it as a path to diverse experiences and rapid growth. But I had no idea where to start.
There were no “How to start freelancing in 10 easy steps” kind of youtube videos back then to learn 😀
That's when a casual conversation with my school friend, Sugam Khokhani, changed everything.
"Why don't you try Odesk?" Sugam suggested one day. (For those who don't know, Odesk is now Upwork)
I had no idea what Odesk was, but Sugam didn't just throw me a suggestion and walk away. He sat with me, helping build my profile, explaining the ins and outs of the platform.
"Here's how you bid for projects," he said, patiently guiding me through the process.
That first bid was terrifying. But then, it happened - my first project.
And then another. And another.
Soon, I was swimming in opportunities. So many, in fact, that I couldn't handle them alone. I started hiring help, building a team to manage the influx of projects.
Before I knew it, this accidental journey had transformed into something bigger than I ever imagined - a full-fledged software testing and QA agency.
Today, a decade later, as I look at our thriving business, I can trace it all back to that one conversation with Sugam.
It's amazing how a single act of kindness can set off a chain reaction of success.
To Sugam Khokhani - thank you. Your willingness to help didn't just change my career; it created opportunities for every team member who's been part of this agency over the past decade. Keep helping people like you do - you never know whose life you might change next :)
. . . . . .
Have you had a 'Sugam' in your life? Someone whose small act of kindness led to big changes? I'd love to hear your stories.
#Gratitude #Entrepreneurship #PayItForward
Does your end-to-end automated test break after a big new update?
Well, there are 3 solutions to this…
𝗔/. 𝗖𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗲 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀
Your developers need to think about testability in all projects.
Mostly broken selectors are often the culprit in UI test failures.
Solution: Get devs to add custom attributes to ALL UI elements..
This includes buttons, inputs, tables, selects - everything you interact with.
This can dramatically reduce time fixing broken tests.
𝗕/. 𝗦𝗵𝗶𝗳𝘁 𝗹𝗲𝗳𝘁, 𝗶𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗲 𝗿𝗶𝗴𝗵𝘁
Embed automated tests directly in your CI/CD workflow. Ideally, run the full test suite on every code push.
Implement a "you break it, you fix it" policy.
This means the developer who introduced a failing test is responsible for fixing it.
Result: Faster issue detection and a shared sense of quality ownership
𝗖/. 𝗗𝗶𝘃𝗲𝗿𝘀𝗶𝗳𝘆 𝘆𝗼𝘂𝗿 𝘁𝗲𝘀𝘁𝗶𝗻𝗴 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆
Try to reduce reliance on brittle UI checks - they're often the first to break.
Boost API automation for greater stability and speed. Focus UI tests only on critical, stable user journeys.
Consider pausing UI automation during periods of rapid UI changes.
Integrate QA and dev teams to align goals and improve communication.
Remember: Sometimes less is more in UI automation
The most resilient test strategy often involves a mix of approaches.
Keep Adapting!
. . . . . .
P.S. If you need expert insights on automation testing in your project. Let’s chat!
#testautomation #automationtesting #softwaretesting #QA
