Last sprint: 100% pass rate.
Green build. Confident deploy.
Monday: 47 support tickets.
"Button hidden on mobile."
"Form overlaps footer."
"Can't click submit on iPad."
Selenium automation testing passed. UI broken.
This TestLeaf breakdown explained what I missed.
The Problem
Selenium confirmed workflow worked.
Login, checkout, dashboard: ✅
None proved UI was usable.
What I Missed
Software testing with Selenium verifies:
Element exists
Workflow completes
Assertions pass
Doesn't verify:
Element visible
No overlaps
Mobile layout works
Text readable
False Confidence
Tests:
element.isDisplayed() // true
element.click() // success
Users saw:
Submit behind sticky header
Fields overlapping on mobile
Cards misaligned
Text unreadable
Why Matters
Mobile accounts for 51% of global web traffic.
India? 68% mobile dominance.
My tests ran on desktop viewports. Most actual users accessed on mobile devices.
I tested functionality. They experienced layout and visual presentation.
Gap between testing and reality.
Changed
Selenium training in Chennai taught visual quality.
Learned:
Visual regression
Responsive validation
Viewport coverage
Layout stability
New Approach
Functional (Selenium): Workflow? Logic? Data?
Visual (Added): Layout stable? Elements visible? Responsive? No overlaps?
Example
Before:
javadriver.findElement(By.id("submit")).click();
// Passes if exists
After:
javadriver.findElement(By.id("submit")).click();
driver.manage().window().setSize(new Dimension(375, 667));
takeScreenshot();
compareBaseline();
// Catches mobile issues
Insight
Green build ≠ usable UI.
Functional = it works.
Visual = users can use it.
Questions
Not "Did it complete?"
But:
Button visible?
Layout stable across viewports?
Touch-accessible?
Responsive works?
Pattern
Strong QA = functional + visual.
Selenium → workflows
Visual regression → experience
Responsive checks → real devices
Combined = release confidence.
Top comments (0)