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
The edx-platform frontend is very complex and so not all the issues with it can be caught with the existing frontend unit tests.
Goal
To ensure that we don't break the most basic capabilities of the edx-platform, we should have a set of tests that run on a production-like runtime of edx-platform.
Acceptance Criteria
The end-to-end tests should spin up a production like run of edx-platform with assets fully built and test the following scenarios:
User creation
User Login
User enrollment in a course
User can load a problem
User can submit a response
Some of these capabilities have moved to MFEs in which case we should use the relevant APIs but where possible we should load the page/iframe in a browser and do UI level testing.
The text was updated successfully, but these errors were encountered:
@feanil what playwirght seems good candidate for this.
Could you please share some ideas on how to initiate the server or use an existing sandbox with code changes?
I think the simplest version of this testing would bring up the server similar to how we do it for the migration testing where we just use the minimal config and then we hit that running server with whatever UI testing we have written. I think it's fine to try this with playwright or any other technology that you're familiar with as long as the end tests are in python or javascript in a way that's easy for developers to add/update.
Context
The edx-platform frontend is very complex and so not all the issues with it can be caught with the existing frontend unit tests.
Goal
To ensure that we don't break the most basic capabilities of the edx-platform, we should have a set of tests that run on a production-like runtime of edx-platform.
Acceptance Criteria
The end-to-end tests should spin up a production like run of edx-platform with assets fully built and test the following scenarios:
Some of these capabilities have moved to MFEs in which case we should use the relevant APIs but where possible we should load the page/iframe in a browser and do UI level testing.
The text was updated successfully, but these errors were encountered: