Closed Bug 1585252 Opened 5 months ago Closed 1 month ago

[python3] Manually test Pontoon app and sync for regressions

Categories

(Webtools :: Pontoon, task, P2)

task

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.

Blocks: 1362323
Summary: [python3] Test Pontoon app and sync for regressions → [python3] Manually test Pontoon app and sync for regressions

To be clear, this work will happen on our stage instance.

This work includes the following steps:

  1. Deploy a patch that updates the runtime to Python 3.7 to our stage Heroku environment.
  2. Trigger a sync job without commit for all jobs, verify that no errors happen and data is correctly modified or created in Pontoon.
  3. Trigger a sync job with commit for a single, test repo, verify that changes are correctly synchronized to that repo.
  4. 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

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:

  1. mercurial needs to be updated: bug 1597732
  2. celery needs to be updated (with its dependencies): bug 1597733
  3. 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

Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.