Hi @aabidsofi19 @leecalcote . I would like to work on this issue. It would be my first time contributing here, so I appreciate some guidance.

I found the existing workflow at

So, I'm thinking of replacing the cypress test steps with a step that runs make test-setup-ui and make test-ui, which run the playwright tests. Is this the correct approach?

@DevRish yeah thats the right approach .

@DevRish, looks like we've had a misfire on the first PR. Try again and come back quickly or let us know if you're in need of being reassigned, so that another contributor can carry this forward.

@DevRish you're encouraged to try again. In the meantime, as you work on it, I'll open this up for other contributors to undertake the crux of this issue, which is the conversion from one tool to the next.

Here is my second try at this issue. Summary of changes:

• Migrated all cypress tests except commented out ones (service_mesh_configuration_management_spec.js and configuration_filters_spec.js) to playwright. Verified passing on my system.
• Used provider None for running the tests, because the Meshery provider was giving some errors in my local instance, which I haven't been able to fix yet. However, I think the flow of the existing tests are same irrespective of provider chosen.
• The test for visibility of Service Mesh section in indexui.spec.js is commented out because it was failing on my end, as no such section was indeed visible in the left navigation panel on the local instance.
• The checks to compare response bodies of requests to /api/system/adapters and /api/system/adapter/manage in settings.spec.js was done in the cypress tests, but I have excluded them because I think the request body will differ depending on which adapters the user has active and running, based on the responses I observed.

Please review @leecalcote @jameshorton2337