Does Low-Code mean Low Testing?
summary
Argues that low-code still needs focused testing and gives concrete outcomes: a booking app goes from brainstorm to production in two days from brainstorm to live, an ERP attempt collapses when customization adds high-code and complexity, a load test shows the platform fails at 100 users out of 10,000 expected, and UX bugs like a checkbox needing three actions and SSO logout mismatches persist. Recommends low-code testing tools (curiosity mabel or test tim, TestProject or LeapWork) plus a quality consultant role.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:29Marilyn’s introduction
- 2:33Who is Marilyn
- 3:14Disney’s low-code inspiration
- 4:41Low-code promises
- 6:06Two companies’ low-code approaches
- 7:51Risks of citizen development
- 9:57Performance and scalability challenges
- 11:43Deployment and version control risks
- 12:48Usability and UX gaps
- 13:08Testing low-code applications
- 14:51Why unique testing matters
- 15:34Layers to test in low-code
- 16:37Functional risks in low-code
- 17:40Role of quality consultant
- 18:47ERP implementation struggles
- 20:11Bridging gaps in low-code
- 21:13Testing vs. low-code testing tools
- 22:37Preparing for test automation
- 23:20Benefits of test automation
- 24:27Risks in citizen testing
- 25:32Low-code and companies
- 26:15Q&A: When not to use low-code
- 28:03Q&A: Testing awareness
- 29:29Q&A: Executive misconceptions
- 32:12Q&A: Bias and edge cases
- 34:40Q&A: Good low-code tester
- 37:09Q&A: Simple, fast, cheap, good testing
- 38:14Q&A: Future of low-code and AI
related talks
46mDoes Low Code Mean Low Testing?
22mHow Low-Code Enables Continuous Testing in DevOps
45mLow Code Visual Testing of an Enterprise Scenario
08m"There’s no such thing as ‘no code’ "
01h 05mMicrotesting
24mTesting Less, Achieving More: How we mastered The Art of Strategic Testing
21mLowering End to End Testing Barriers
38mThere Are No Tests