test suite

[alexanderadam]

Either I'm missing something or there's no test suite.
If there's indeed none, be aware that it would increase trust if tests would be added.

[stefan-ernst]

Hey @alexanderadam - hello from across the pond (Rotkreuz) 👋

Yes, there is a full e2e testsuite which we have not yet made available yet since it still needs a bit of work. If you are interested I can add you to the repo

[alexanderadam]

Feel free to add me. I'm not sure whether I can contribute much though.

Also feel free to ping me in case you'd like to meet in the Freiruum for a chat or so.

[Optic00]

While working on action AI input resolution, I found a focused case worth covering: the editor offers item.* fields, but ai_extract and ai_agent currently look up configured inputs directly in ctx.Variables, so dotted item paths and nested output values are not resolved.

I am preparing unit coverage for dotted item fields, nested output values, and missing-input failures. Would you prefer those focused tests in this repository, or should the implementation PR omit them because the canonical suite lives in core-tests? A small public unit test would let external contributors verify this behavior without duplicating the private E2E suite. I am happy to follow either convention.

[stefan-ernst]

@Optic00 you are free to add these to the core repo. I am currently getting the core-tests repo ready and will move them over once done

[stefan-ernst]

core-tests is available meanwhile