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
To be done after Container Cypress Integration tests are restructured properly in #3562
Possible solution:
This can work as a Cypress Integration test.
Have two apps that use WC microfrontend with the same exact UI, but one of them is built as a Core based App, the other as a Container based only WC microfrontend. Maybe just put these under two different routes if possible.
At the end have one singular Cypress test file/s for both apps.
The same tests should be ran twice but on different app routes. If test passes twice it means both Core and Client have the same clientAPI functionality.
(Keep in mind that there might be exceptions where some Core WC clientAPI functionality might not make sense in Container scenario)
The text was updated successfully, but these errors were encountered:
ndricimrr
changed the title
Add test that checks that Core and Container WC LuigiClient API are the same
Add test that checks that Core and Container WC clientAPI are the same
Feb 29, 2024
Follow up from #3643
To be done after Container Cypress Integration tests are restructured properly in #3562
Possible solution:
This can work as a Cypress Integration test.
Have two apps that use WC microfrontend with the same exact UI, but one of them is built as a Core based App, the other as a Container based only WC microfrontend. Maybe just put these under two different routes if possible.
At the end have one singular Cypress test file/s for both apps.
The same tests should be ran twice but on different app routes. If test passes twice it means both Core and Client have the same clientAPI functionality.
(Keep in mind that there might be exceptions where some Core WC clientAPI functionality might not make sense in Container scenario)
The text was updated successfully, but these errors were encountered: