Does Low Code Mean Low Testing?
summary
Low code platforms ship with CI/CD in platform and vendor-tested building blocks but still require tester attention for integrations, custom code and nonfunctional risks; real projects include replacing eight company ERPs supporting 15 million tires a year so downtime is unacceptable. Expect vendors to catch technical wiring while functional errors and architecture drift remain; empiric speedup is about 2–3x faster for simple apps, and the citizen tester pattern increases risk on complex systems so prioritize business‑rule and integration testing.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:10What is low code
- 10:50Core components
- 24:24Why test low code
- 32:40Risk factors
- 41:13What to test
- 44:45Closing remarks
related talks
40mDoes Low-Code mean Low Testing?
22mHow Low-Code Enables Continuous Testing in DevOps
45mLow Code Visual Testing of an Enterprise Scenario
24mDemystifying Code Through Testing
38mThere Are No Tests
51mLess about tests more about testability - a tester in the platform engineering world
19mBusiness Impact Delivery Using Test Automation
24mTesting Less, Achieving More: How we mastered The Art of Strategic Testing