Project studio II — build and test

Inhalt

This week is focused on implementation, debugging, and testing. Getting a workflow to run is only the first step; evaluating and tightening it is what makes it useful. Expect the first working version to fail on realistic inputs. A real test case is one the system wasn't obviously designed for — messy formatting, edge cases, out-of-distribution inputs. If all 5 test cases look like the example in the prompt, you haven't tested anything.

Beispiel: A paper-comparison assistant works on clean abstracts but fails on preprints with unusual formatting — forcing a preprocessing node and a stricter prompt.

Hast du das verstanden?

• [ ] 5 test cases include at least 2 adversarial/edge inputs
• [ ] Every failure has root cause + fix logged
• [ ] End-to-end runs (not just the Dify piece or the n8n piece)
• [ ] You can point to one change you made *because* of a test failure
• [ ] You can explain in one sentence what you learned that you would tell a labmate tomorrow

Direkt ausprobieren

Diese Links öffnen die laufenden Demos auf n8n.32dots.de + dify.32dots.de.