Manish Saini
Advocating for Smarter, Scalable, and Automation-Driven Testing | Developer Advocate 🥑 | Speaker | Mentor | Author | AI & Automation Evangelist | YT - @TechUnfilteredWithManish
Noida, India
Actions
As the Senior Lead Developer Advocate at BrowserStack, I bridge the gap between developers and testing solutions, empowering global communities to build higher-quality software with confidence.
With 11+ years of experience in software quality and test automation, I understand the challenges development teams face and how the right testing approach can transform delivery timelines while enhancing product quality.
What I Do:
I advocate for developers by creating educational content, building communities, and demonstrating how testing can be integrated seamlessly into development workflows. My goal is to help teams adopt testing practices that accelerate rather than hinder innovation.
Previously, as a Senior SDET Consultant, I partnered with clients worldwide to establish testing processes and automation solutions that significantly improved team productivity across Cloud, Fintech, E-commerce, HR-Tech, and other domains.
My Technical Foundation:
- Automation Frameworks: Pytest, Behave, Pytest-bdd
- Testing Tools: Appium, Selenium, Playwright, Cypress
- Infrastructure: Docker, Kubernetes
- API Testing: Postman, REST frameworks
- Performance Testing: Locust, K6, Artillery
- CI/CD: Bitbucket Pipelines, GitLab CI, Jenkins, GitHub Actions
- Cloud Platforms: AWS, GCP, DigitalOcean, Linode
Area of Expertise
Topics
AI Can Generate Tests. It Cannot Generate Trust.
AI is accelerating test automation faster than ever. We can generate tests in minutes, heal selectors automatically, and trigger intelligent reruns. Pipelines are greener and faster.
And yet, many teams still execute critical flows manually before release.
Not because automation is missing.
But because confidence is.
In this talk, I reflect on a pattern I’ve repeatedly seen. Test suites grow. AI adoption increases. Execution time decreases. But when pipelines turn red, teams rerun builds instead of analyzing failures. When instability increases, automation engineers are pulled into execution tasks. When release decisions matter, trust shifts back to manual execution instead of automated results.
The real bottleneck is not writing tests. It is understanding them.
In this talk, we will explore:
- Why green pipelines do not automatically translate to release confidence
- How signal decays as test suites scale
- Why AI scales execution but not necessarily understanding
- Where observability and impact awareness fit into modern automation systems
We will examine how failure fingerprinting, environment traceability, build-to-build comparison, and impact analysis change the conversation from “Did it pass?” to “Do we understand what happened?”
This session is not about adding more tests.
It is about designing automation systems that teams can confidently delegate to.
Because automation should remove execution burden.
Not duplicate it.
Shift Left Isn’t a Tooling Problem. It’s a Collaboration Debt Problem.
Shift-left is often framed just as Testing Early. Add API tests. Integrate automation into CI. Run checks earlier. Increase coverage.
But in many teams, the only thing that truly shifts is the timeline.
In one team I worked with, QA was invited into requirement analysis and sprint planning earlier than usual. During that discussion, we noticed the feature being designed already existed in another module and could be reused. That single observation saved four days of development effort. Similarly in one session, we identified edge cases that would likely have caused rework later. If those were discovered during testing, it would have meant additional QA–dev churn, retesting, and delay.
Nothing about that outcome required new tools.
It required shared visibility and shared authority.
Over time, I’ve seen a recurring pattern across teams scaling automation and CI adoption. We introduce more checks to reduce risk. We expand layers to gain confidence. But testers are still often invited after core design decisions are made. Devs optimise for their module. QA is expected to “own quality” without influencing the decisions that define it.
We call QA gatekeepers. Then we place them behind the gate.
As per my experience, We should be on a watchtower view, because testers often see system-wide impact before issues materialise. But without involvement in early conversations, that visibility turns into reactive validation instead of preventive design input.
This talk explores:
- Why many shift-left initiatives fail even when tooling is strong
- How collaboration debt accumulates across sprints and teams
- Why automation sometimes compensates for missing conversations rather than solving root causes
- How to rethink ownership, authority, and involvement when scaling quality
This is not a tooling session. It is a reflection on system design, responsibility, and how experienced testers can move from late validation to early influence.
Intended audience:Testers, SDETs, and QA leads who have implemented shift-left practices and still feel that something fundamental has not changed.
The goal is not to criticise shift-left, but to examine what actually needs to shift if we want shared responsibility instead of earlier isolation.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top