Skip to content
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

Refactor MTE-1885 [v122] Move scripts and other files to firefox folder #17310

Conversation

isabelrios
Copy link
Contributor

📜 Tickets

Jira ticket

Let's move more files into firefox-ios folder.

  • L10n tests and import scripts
  • Docs

Also let's rename the github actions mobile test eng own.

📝 Checklist

You have to check all boxes before merging

  • Filled in the above information (tickets numbers and description of your work)
  • Updated the PR name to follow our PR naming guidelines
  • Wrote unit tests and/or ensured the tests suite is passing
  • When working on UI, I checked and implemented accessibility (minimum Dynamic Text and VoiceOver)
  • If needed I updated documentation / comments for complex code and public methods

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if we can even remove this file... it has not been updated in two years

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Delphine do you know what this is used for?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No idea. @boek Do you remember this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It shouldn't be removed, it's used for the WidgetIntent.strings we have. Example here. The name definitely could be better than l10n_comments thought haha. But if the filename is changed then we should change it too in the script

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh I see, thanks @lmarceau ... should I move it then or wait for another round of changes? Not sure I can create a PR in LocalizationTools repo or to handle that change there

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I can create a PR in there. The strings for v120 are currently being exported, so if we merge the current PR (17310) after that's done to avoid breaking l10n flow would be ok I think (should be done by end of week for sure) 👍 I just created a task for myself to adjust the script in LocalizationTools once this PR is merged.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that sounds great :) thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@flodolo as commented on focus-ios PR, I'm also moving this script here. I have changed the path in the bootstrap file where it is executed. Locally I get the import working, but please let me know if I'm missing any other changes that could break the automation around this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@flodolo I also changed the name for the focus github action and seems that this change is not affecting anything, but doublechecking

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No risk, we have our own workflow, we only use scripts from this repo.

Copy link
Contributor

@flodolo flodolo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be good, since we use LocalizationTools to do the actual extraction

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No risk, we have our own workflow, we only use scripts from this repo.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Delphine do you know what this is used for?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@relud is it fine if we rename this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lmarceau checking with you if we can rename as author of the github action

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes should be safe to rename 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lmarceau checking with you if we can rename as author of the github action

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes should be safe to rename 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeddai checking with you if we can rename without breaking anything as author of the github action

@isabelrios isabelrios marked this pull request as ready for review November 15, 2023 09:33
@isabelrios isabelrios requested review from a team as code owners November 15, 2023 09:33
@isabelrios isabelrios requested a review from jjSDET November 15, 2023 09:33
@flodolo
Copy link
Contributor

flodolo commented Nov 15, 2023

I double-checked one of these comments, and we still have it in the XLIFF file. So, something is using this file, but I have no clue how based on #8050

@flodolo
Copy link
Contributor

flodolo commented Nov 15, 2023

And that's because the file is used from code that lives elsewhere, and needs to be updated as well
https://github.com/mozilla-mobile/LocalizationTools/blob/main/Sources/LocalizationTools/tasks/ExportTask.swift#L91-L98

@mobiletest-ci-bot
Copy link

mobiletest-ci-bot commented Nov 15, 2023

Messages
📖 Project coverage: 35.02%
📖 Edited 478 files
📖 Created 0 files

Client.app: Coverage: 32.51

File Coverage
NimbusOnboardingTestingConfigUtility.swift 100.0%

Generated by 🚫 Danger Swift against 71cf099

@isabelrios
Copy link
Contributor Author

And that's because the file is used from code that lives elsewhere, and needs to be updated as well https://github.com/mozilla-mobile/LocalizationTools/blob/main/Sources/LocalizationTools/tasks/ExportTask.swift#L91-L98

Thanks for checking, I will not remove the l10n_comments.txt file then

Copy link
Contributor

mergify bot commented Nov 16, 2023

This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏

@isabelrios isabelrios force-pushed the irios-mte1885-move-test-scripts-files-into-firefoxios branch from 743d77b to 4f9b3d7 Compare November 16, 2023 18:12
@isabelrios
Copy link
Contributor Author

I had to create a firefox-ios-tests folder inside firefox-ios and move the tests there. The way I created firefox-ios folder before would not allow me to move app folders in it in the future.

This PR is ready for review. Thanks for your comments so far.

@isabelrios
Copy link
Contributor Author

@flodolo I'm moving the import-strings.sh script into firefor-ios folder. I have changed the bootstrap script to run it using the new location. Are there more changes needed so that the import/export keeps working? The import is working for me locally, but double checking as I don't want to break things

@flodolo
Copy link
Contributor

flodolo commented Nov 17, 2023

@flodolo I'm moving the import-strings.sh script into firefor-ios folder. I have changed the bootstrap script to run it using the new location. Are there more changes needed so that the import/export keeps working? The import is working for me locally, but double checking as I don't want to break things

We only use the bootstrap from this repo and LocalizationTools on our side. Once this is merged, you should verify that the import action works correctly in this repo.

@isabelrios
Copy link
Contributor Author

@flodolo I'm moving the import-strings.sh script into firefor-ios folder. I have changed the bootstrap script to run it using the new location. Are there more changes needed so that the import/export keeps working? The import is working for me locally, but double checking as I don't want to break things

We only use the bootstrap from this repo and LocalizationTools on our side. Once this is merged, you should verify that the import action works correctly in this repo.

I will verify that for sure, thank you

@isabelrios
Copy link
Contributor Author

FYi, This PR will not land until the v121 branch is cut from main on Monday to disrupt the less possible

Copy link
Contributor

mergify bot commented Nov 17, 2023

This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏

@clarmso
Copy link
Collaborator

clarmso commented Nov 17, 2023

😬 Would Sync Integration Tests run? I can give it a try.

@isabelrios
Copy link
Contributor Author

😬 Would Sync Integration Tests run? I can give it a try.

In theory yes, on MacStadium I will fix the path to the test results once this lands

@clarmso
Copy link
Collaborator

clarmso commented Nov 17, 2023

😬 Would Sync Integration Tests run? I can give it a try.

In theory yes, on MacStadium I will fix the path to the test results once this lands

🎉 I just confirmed that the SyncIntegrationTests could be run.

@clarmso
Copy link
Collaborator

clarmso commented Nov 17, 2023

😬 Would Sync Integration Tests run? I can give it a try.

In theory yes, on MacStadium I will fix the path to the test results once this lands

🎉 I just confirmed that the SyncIntegrationTests could be run.

I take it back. The TPS logs shows the following errors. @isabelrios Could you please update the paths to files needed by TPS?

2023-11-17 10:24:40.966 CROSSWEAVE ERROR: [phase -1] _executeTestPhase failed - Error opening input stream (invalid filename?): file:///Users/cso/workspace/firefox-ios/test_bookmark_desktop.js No traceback available

Copy link
Collaborator

@clarmso clarmso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check paths for sync integration tests. 🙇🏼

@isabelrios
Copy link
Contributor Author

isabelrios commented Nov 17, 2023

😬 Would Sync Integration Tests run? I can give it a try.

In theory yes, on MacStadium I will fix the path to the test results once this lands

🎉 I just confirmed that the SyncIntegrationTests could be run.

I take it back. The TPS logs shows the following errors. @isabelrios Could you please update the paths to files needed by TPS?

2023-11-17 10:24:40.966 CROSSWEAVE ERROR: [phase -1] _executeTestPhase failed - Error opening input stream (invalid filename?): file:///Users/cso/workspace/firefox-ios/test_bookmark_desktop.js No traceback available

@clarmso I have a copy of my branch on MacStadium and the tests passed there. It may be something on your virtual env that is chached?
You can check on MacStadium: /Users/administrator/irios-tmp-test/irios-fork/firefox-ios/firefox-ios/firefox-ios-tests/Tests/SyncIntegrationTests
I have left the terminal open with my repo and branch. I commented the test_integration file to just run one test to try

@isabelrios isabelrios requested a review from clarmso November 17, 2023 16:51
@clarmso
Copy link
Collaborator

clarmso commented Nov 17, 2023

😬 Would Sync Integration Tests run? I can give it a try.

In theory yes, on MacStadium I will fix the path to the test results once this lands

🎉 I just confirmed that the SyncIntegrationTests could be run.

I take it back. The TPS logs shows the following errors. @isabelrios Could you please update the paths to files needed by TPS?

2023-11-17 10:24:40.966 CROSSWEAVE ERROR: [phase -1] _executeTestPhase failed - Error opening input stream (invalid filename?): file:///Users/cso/workspace/firefox-ios/test_bookmark_desktop.js No traceback available

@clarmso I have a copy of my branch on MacStadium and the tests passed there. It may be something on your virtual env that is chached? You can check on MacStadium: /Users/administrator/irios-tmp-test/irios-fork/firefox-ios/firefox-ios/firefox-ios-tests/Tests/SyncIntegrationTests I have left the terminal open with my repo and branch. I commented the test_integration file to just run one test to try

😓 pipenv clean is needed in the directory after checking out the branch.

@isabelrios isabelrios force-pushed the irios-mte1885-move-test-scripts-files-into-firefoxios branch from 6125091 to 55afc47 Compare November 20, 2023 09:37
Copy link
Contributor

mergify bot commented Nov 20, 2023

This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏

@isabelrios isabelrios force-pushed the irios-mte1885-move-test-scripts-files-into-firefoxios branch from 55afc47 to c5ebd8e Compare November 20, 2023 10:52
Copy link
Contributor

mergify bot commented Nov 20, 2023

This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏

@isabelrios isabelrios force-pushed the irios-mte1885-move-test-scripts-files-into-firefoxios branch from c5ebd8e to 65abf87 Compare November 20, 2023 16:04
Copy link
Contributor

mergify bot commented Nov 20, 2023

This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏

@isabelrios isabelrios force-pushed the irios-mte1885-move-test-scripts-files-into-firefoxios branch from 65abf87 to 023fafa Compare November 21, 2023 08:32
@isabelrios isabelrios merged commit 48a02a1 into mozilla-mobile:main Nov 21, 2023
10 checks passed
@isabelrios isabelrios changed the title Refactor MTE-1885 Move scripts and other files to firefox folder Refactor MTE-1885 [v122] Move scripts and other files to firefox folder Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants