feature request: preview-middleware

[heimwege]

Hi guys,

how about using the preview middleware to get rid of the test glue code?

Using this config in the ui5*.yaml (further configuration w.r.t paths, testfile name patterns, etc. is possible)

  - name: preview-middleware
    afterMiddleware: compression
    configuration:
      test:
        - framework: QUnit
        - framework: OPA5
        - framework: Testsuite

makes the following files superfluous:

• /test/testsuite.qunit.html
• /test/testsuite.qunit.js
• /integration/opaTests.qunit.html
• /integration/opaTests.qunit.js
• /unit/unitTests.qunit.html
• /unit/unitTests.qunit.js

Having this glue code centrally managed could be quite helpful in case the test recommended setup changes (e.g. because resources/sap/ui/test/starter/createSuite.js should be used).

Using this middleware might not only be relevant for the ts app generator but for other generators as well.

[petermuessig]

We are currently reworking the test started code. Till then, I would prefer not to integrate the preview-middleware into the "basic" templates of UI5 applications.

Let's keep this issue open for the future evolution of the templates.

[tobiasqueck]

We are currently reworking the test started code. Till then, I would prefer not to integrate the preview-middleware into the "basic" templates of UI5 applications.

Let's keep this issue open for the future evolution of the templates.

The middleware removes that from the project, so wouldn't it be good then to integrate it now? And, once, you have new guidance for the test starter code, then we would implement it in the middleware and all projects "magically" use it once upgrading.