You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"As a developer, I have two blades A and B where I want to test complex interactions between them.
Workbenches allow unit testing of blade A and B in isolation, but does not facilitate integration testing, with a visual representation of two components interacting.
BRJS' workbench handling code is not implemented in a very generic way:
case WORKBENCH_INDEX_PAGE_REQUEST:
return getIndexPageContent(app.bladeset(pathProperties.get("bladeset")).blade(pathProperties.get("blade")).workbench(), new Locale(pathProperties.get("locale")), devVersion, contentAccessor, RequestMode.Dev);
This code presumes the workbench lives in a blade, and effectively rules out library level or bladeset level workbenches.
A workaround would be to use another HTML page (index.html) at the bladeset level, to instantiate both components. However further BRJS restrictions impose a 'single-entry' point, default-aspect/index.html, preventing us creating test web pages, or in fact using any sort of multi-page model.
As a feature request, could BRJS add support for integration testing of UI components?
And as a follow up request, could the restriction on 'one workbench per blade', 'one HTML page per app' be lifted to support multiple pages for different testing scenarios?"
The text was updated successfully, but these errors were encountered:
Hey @tobycatlin we have 2 other issues that cover this - #945: Allow workbenches on the bladeset level & #950: allow workbenches in BRJS libraries. I'm going to close this as a duplicate in favour of #945 and #950.
Raised as Caplin support issue: http://yourls.caplin.com/3
"As a developer, I have two blades A and B where I want to test complex interactions between them.
Workbenches allow unit testing of blade A and B in isolation, but does not facilitate integration testing, with a visual representation of two components interacting.
BRJS' workbench handling code is not implemented in a very generic way:
case WORKBENCH_INDEX_PAGE_REQUEST:
return getIndexPageContent(app.bladeset(pathProperties.get("bladeset")).blade(pathProperties.get("blade")).workbench(), new Locale(pathProperties.get("locale")), devVersion, contentAccessor, RequestMode.Dev);
This code presumes the workbench lives in a blade, and effectively rules out library level or bladeset level workbenches.
A workaround would be to use another HTML page (index.html) at the bladeset level, to instantiate both components. However further BRJS restrictions impose a 'single-entry' point, default-aspect/index.html, preventing us creating test web pages, or in fact using any sort of multi-page model.
As a feature request, could BRJS add support for integration testing of UI components?
And as a follow up request, could the restriction on 'one workbench per blade', 'one HTML page per app' be lifted to support multiple pages for different testing scenarios?"
The text was updated successfully, but these errors were encountered: