PacoVK

Hey @rdmueller i think the issue is the usage of the doctoolchain image rather than a bug. I can reproduce the behaviour using the steps you described, but i can...

Since this PR introduces a new file structure for tests to put them under `src/test/groovy/scripts` i would like to open a discussion here. 1. Although putting tests under `src/test/groovy/scripts` folder...

One small remark on your current proposal: > src/petstore-*.yaml: the OpenApi specifications used by the test I'd like to have them under > resources/petstore-*.yaml: the OpenApi specifications used by the...

> The main point of a test should be to reflect the structure of the documentation project structure. This means, following our standard project structure, if an OpenAPI specification is...

> But I would not refactor the existing code without good test coverage This would just kill the scope of this PR i guess :D But if we align on...

Output on Mac with ARM chip, with `arch -x86_64 bash` ``` uname -m --> x86_64 uname -s --> Darwin arch --> i386 ``` Bear in mind that running `arch -x86_64...

@mh182 what is still open here?

is this about creating a release process for `dtcw`? i am a bit lost tbh of the tickets scope, thats why i am asking :)

Thanks for the good work! I will take a look and then merge it. Apparently I waited because of the draft mode so far 😊🖖

Hey @MichaelRossner thanks for raising this issue. I think it clearly states that me miss some documentation here. Starting with `3.x` we introduced [`failOnMissingImages`](https://doctoolchain.org/docToolchain/v2.0.x/030_news/2023/3.0.0-rc1.html#_added) configuration. If you set this property...