Rethink the folder structure created by wdi5 about create-wdi5 HOT 5 OPEN

I can imagine that it might be be confusing for all who just use wdi5, not knowing about the Browser and Node part, and/ or have experience with the

test/e2e/**

structure.

from create-wdi5.

Yea, that is tricky.

From an ui5 standpoint, I would expect all the tests to be in the webapp/test folder.

How about adding a ".gitignore" like feature in the ui5 tooling that will automatically add all folders/files with such a file to the excludes. This would make it possible to add it to the WDI5 template code and therefor need no further config by the Developer.

@RandomByte do you think such a feature is possible without too much work ?

from create-wdi5.

Hi, rationale behind picking webapp/test/e2e/**/* as the default location for wdi5 tests was to adhere to the standard where UI5 puts its Unit- (webapp/test/unit/**/*) and Integration-tests (webapp/test/integration/**/*) in docs and tutorials.
So my first notion wrt TypeScript would be to have an exclude maintained for webapp/test/e2e/**/*. While moving wdi5 TS resources to sth like /test/e2e/**/* might adhere to the TypeScript standards, it would fragment the test file/folder location into /webapp/test/ and /test, eventually confusing users. But this is just my first notion, nothing set in stone here as long as it helps the UI5 developer.
Thoughts @RandomByte @tobiasqueck @Siolto @dominikfeininger @sebbi08?

from create-wdi5.

You can already exclude resources from the build: https://sap.github.io/ui5-tooling/stable/pages/Configuration/#exclude-resources

Excluded resources won't be available to the ui5-tooling-modules task. However, they are still available in the server. The idea is to exclude runtime resources that are needed during development but unwanted in production. Our general expectation is that webapp only contains runtime resources.

from create-wdi5.