-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use a single source for test sites' content #1271
Comments
I just realized that the reason why we might duplicate content is to avoid conflicts when two different engineers work on the same set of tests. In that case, what if instead of storing the entire content we only store the commit hash? |
We had a short discussion on this. The primary challenge with the proposed approach is the occasional DB sync with production. These syncs will end up destroying the studio DB and these test courses. The current favored approach is to use the |
@HussainTaj-arbisoft I know this is an old discussion now, but I thought I'd update it with some new information. The end to end test pipeline has been released for a little while now and is running in RC and production. You are correct in that a database restore will wipe out the test courses, along with the rest of the database, but I think that's not as big of an issue as it might seem.
Footnotes
|
Description/Context
Our Playwright tests use a set of test sites. These test sites are located on RC as well as inside the
ocw-hugo-themes
repo, as markdown content. From what we see on RC, we were meant to keep these manually synced.I believe that changes to the test sites should always be made on RC first. We should remove the need for a manual step, which I believe is the cause of this inconsistency. I propose that we use the GitHub content, created via Studio RC, as the source for the test sites in
ocw-hugo-themes
.Plan/Design
To achieve this objective, we will need to perform the following tasks.
test:e2e
command to automatically pull the test sites when needed.I don't know why we initially chose to duplicate the content. I might have missed something, so whoever works on this might need to refine the plan accordingly.
The text was updated successfully, but these errors were encountered: