Closed
Bug 1585252
Opened 5 years ago
Closed 4 years ago
[python3] Manually test Pontoon app and sync for regressions
Categories
(Webtools Graveyard :: Pontoon, task, P2)
Webtools Graveyard
Pontoon
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mathjazz, Assigned: adrian)
References
Details
Attachments
(4 files)
Once all the tests will pass in the python3 env, we should perform extensive manual test of the app, with special focus on sync.
Comment hidden (offtopic) |
Comment hidden (offtopic) |
Comment hidden (offtopic) |
Reporter | ||
Updated•5 years ago
|
Summary: [python3] Test Pontoon app and sync for regressions → [python3] Manually test Pontoon app and sync for regressions
Assignee | ||
Comment 4•5 years ago
|
||
To be clear, this work will happen on our stage instance.
This work includes the following steps:
- Deploy a patch that updates the runtime to Python 3.7 to our stage Heroku environment.
- Trigger a sync job without commit for all jobs, verify that no errors happen and data is correctly modified or created in Pontoon.
- Trigger a sync job with commit for a single, test repo, verify that changes are correctly synchronized to that repo.
- Browse the web app and verify that no functionalities are broken (login, dashboards, translate, review… ).
The command to trigger a sync job is: ./manage.py sync_projects --projects=$SLUG --no-commit
Assignee: nobody → adrian
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•5 years ago
|
||
With help form Matjaz, I was able to deploy Python 3 to stage and run a sync job. I found a few problems along the way, that I transformed into bugs:
- mercurial needs to be updated: bug 1597732
- celery needs to be updated (with its dependencies): bug 1597733
- There's a TypeError while running sync: bug 1597731
The command I used to run sync is: heroku run -a mozilla-pontoon-staging ./manage.py sync_projects --no-commit
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•4 years ago
|
||
Comment 8•4 years ago
|
||
Assignee | ||
Comment 9•4 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Comment 10•4 years ago
|
||
Assignee | ||
Comment 11•4 years ago
|
||
Updated•3 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•