Let's say you want to update and test your web app with a CMS regularly and you want to automate this:
Do you prefer n8n like workflows or AI workflows where you describe your issue in detail with specific steps?
Commit
9d385aa
playwrite E2E tests running every other day for essentials/critical paths. Full test battery before release. update tests weekly
Would you want to define an example update progress like that:
- Update to minor version
- Test critical paths with test suite
- if test fails -> AI Fix -^
- Create Branch
- Commit Change
- Open a PR…
I only use AI on things that are really necessary. You can push test output to an n8n workflow if there are any errors. Or, every 3 tests, send it to have a second opinion. But E2E tests should be deterministic. No need to put AI in that mix.
I agree! So you would want to build deterministic workflows with AI only if needed?
Anything I don't need to burn tokens for, I don't. I believe in AI as a tool. A fantastic tool. But it's not a universal tool.
commit 9d385aa