Validating Entire User Journeys by Isolating Front Ends using OpenAPI
summary
Shows how OpenAPI-driven HTTP stubbing + Specmatic lets a front end run full user journeys locally and in CI: recorded proxy traffic generates specs, stubs validate canned responses against the spec, and contract tests keep mocks and services in lockstep. Demonstrates OTP login (invalid code, timeouts), parallel Android/iOS/Web runs via Teswiz and BrowserStack tunneling, visual checks with Applitools and reports to ReportPortal, and the ability to shift testing left without real third‑party sandboxes.
AI-written summary · about
chapters (10)
- 0:00Component workflow testing intro
- 3:43Complex user journey challenges
- 7:04Isolation with OpenAPI mocks
- 10:44Super app UI components
- 13:38Component workflow in test pyramid
- 15:49Full-stack testing challenges
- 20:39Demo: UI component workflow testing
- 24:20Fault simulation & parallel testing
- 27:40E2E test architecture with Specmatic
- 32:05Summary & Q&A
related talks
30mBreak the API Test Data Bottleneck: Real Scenarios on Real Systems
37mStop Doing E2E Tests! Write Better Tests with Contract
51mThe Swag of Performance Testing
43mImprove your API and OpenAPI
38mLive Exploratory Testing
40mStrategic Business Functionality Testing: Accelerating Development Through Mocking
26mTips and tricks for writing API Tests
43mAutomating the real-user scenarios across multi-apps, & multi-devices