What browser-level QA found that green tests missed
A passing build is not a passing check.
RUNNING INTERNALLYA real Lehvel operating system in use internally. Not a customer product claim.
01 · Question
Why did Sales Desk pass its unit tests and its build, and still fail in a rep's hand?
02 · Why it matters
Because the tests measured the code and the rep measured the product. Layout, tap targets and viewport behavior on a phone are not in a unit test.
03 · State
RUNNING INTERNALLY A real Lehvel operating system in use internally. Not a customer product claim.
04 · What we built or tested
- A rendered, mobile-viewport QA script run against real device profiles (360 to 430 px wide), as a release gate alongside the tests.
05 · Evidence
FindingDefects surfaced only in rendered mobile QA, after green unit tests and a green build
06 · What we learned
- Name the instrument that would catch the failure you care about, then run that one.
- The founder judges on an iPhone. So does the customer.
07 · Limitations
- A QA script proves what it looked at. It does not prove the pages it did not open.
08 · What changes next
The same viewport gate on every public page in this redesign.
Negative results are published as results. A state on this page is a claim about what is true today, not about what is planned; a limitation is a limitation.
Tell us what is true about your business.
A few questions, in your own words — type them or talk. A person reads what you send and follows up. Nothing is published and nothing is sent on your behalf.