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

[Dependency Updates] Test Instructions Documentations per Dependency Update #19552

Merged
merged 37 commits into from
Nov 10, 2023

Conversation

ParaskP7
Copy link
Contributor

@ParaskP7 ParaskP7 commented Nov 7, 2023

Parent #17551
Internal Discussion pcdRpT-2Hp-p2

This PR adds a new documentations page with test instructions per dependency update.

FYI: The goal is to further automate the dependency update process by documenting all the specific dependency updates that require explicit testing instructions. The hypothesis here is that this approach would not only save time and effort for each update, but also elevate the quality of dependency update work by ensuring that the testing aspect is not left to chance.

PS: This PR is also slightly updating the pull request template by:

  1. Splitting each section using a horizontal line, for grouping purposes (38a4d69),
  2. Starting each section with a second-level heading, for consistency purposes (6b80fa7), and
  3. Applying other minor changes, for consistency purposes (273a96f).

@irfano I added you as the main reviewer, not so randomly (you shared lots of good ideas), since I just wanted someone from the Jetpack/WordPress mobile team to be aware and sign-off on that change. Feel free to merge this PR directly yourself if you deem so.


To Test:

  1. Proofread the new test instructions per dependency update documentation page.
  2. Verify that each section is well written, can be easily understood and provide enough value while devs are working on a specific dependency update.

FYI: Note that the Smoke Test and Special sections can be further improved. However, I didn't want make this improvement now and instead added TODO for devs to keep improving the documentation themselves when and if needed.


Regression Notes

  1. Potential unintended areas of impact

    • N/A
  2. What I did to test those areas of impact (or what existing automated tests I relied on)

    • See To Test section above.
  3. What automated tests I added (or what prevented me from doing so)

    • N/A

PR submission checklist:

  • I have completed the Regression Notes.
  • I have considered adding accessibility improvements for my changes.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

UI Changes testing checklist:

  • Portrait and landscape orientations.
  • Light and dark modes.
  • Fonts: Larger, smaller and bold text.
  • High contrast.
  • Talkback.
  • Languages with large words or with letters/accents not frequently used in English.
  • Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
  • Large and small screen sizes. (Tablet and smaller phones)
  • Multi-tasking: Split screen and Pop-up view. (Android 10 or higher)

TODOs got added on both those test scenarios as I am not sure how
to test this functionality and can't easily find the entry point to it.
All I could do to test this was to manually comment out some code and
verify that the functions were called after setting the device's date to
days/weeks after today.

Still, I think it is better to have that there and inform future
dependency update testers about this functionality and the fact that
this needs to be (somehow) tested, rather than ignore both completely.

For more info see: https://github.com/wordpress-mobile/
WordPress-Android/pull/17892
TODOs got added on all those test scenarios. I think it is better to
have that there and inform future dependency update testers about this
functionality and the fact that this needs to be (somehow) tested,
rather than ignore both completely.

For more info see: https://github.com/wordpress-mobile/
WordPress-Android/pull/17571
TODOs got added on all those test scenarios. I think it is better to
have that there and inform future dependency update testers about this
functionality and the fact that this needs to be (somehow) tested,
rather than ignore both completely.
FYI: Some smoke test instructions might have an 'Extra' section with
addition instructions.
FYI: Every special test instructions have a 'Why & Extra' section to
further explain why that dependency update is so special and how to
deal with it.
@ParaskP7 ParaskP7 added this to the Future milestone Nov 7, 2023
@ParaskP7 ParaskP7 requested a review from irfano November 7, 2023 12:23
@peril-wordpress-mobile
Copy link

Warnings
⚠️ PR has more than 300 lines of code changing. Consider splitting into smaller PRs if possible.

Generated by 🚫 dangerJS

@wpmobilebot
Copy link
Contributor

wpmobilebot commented Nov 7, 2023

WordPress📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
App NameWordPress WordPress
FlavorJalapeno
Build TypeDebug
Versionpr19552-2f1403d
Commit2f1403d
Direct Downloadwordpress-prototype-build-pr19552-2f1403d.apk
Note: Google Login is not supported on these builds.

@wpmobilebot
Copy link
Contributor

wpmobilebot commented Nov 7, 2023

Jetpack📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
App NameJetpack Jetpack
FlavorJalapeno
Build TypeDebug
Versionpr19552-2f1403d
Commit2f1403d
Direct Downloadjetpack-prototype-build-pr19552-2f1403d.apk
Note: Google Login is not supported on these builds.

@ParaskP7 ParaskP7 mentioned this pull request Nov 7, 2023
50 tasks
Copy link
Member

@irfano irfano left a comment

Choose a reason for hiding this comment

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

Thank you for your efforts on this. I've added some comments for your review.

docs/test_instructions_per_dependency_update.md Outdated Show resolved Hide resolved
docs/test_instructions_per_dependency_update.md Outdated Show resolved Hide resolved
docs/test_instructions_per_dependency_update.md Outdated Show resolved Hide resolved
docs/test_instructions_per_dependency_update.md Outdated Show resolved Hide resolved
docs/test_instructions_per_dependency_update.md Outdated Show resolved Hide resolved
docs/test_instructions_per_dependency_update.md Outdated Show resolved Hide resolved
docs/test_instructions_per_dependency_update.md Outdated Show resolved Hide resolved
This is done for 'WorkManager' and 'Preference', which were both
incorrectly pointing to a specific line number, instead of the default
line one.

Related PR Comment: https://github.com/wordpress-mobile/
WordPress-Android/pull/19552#discussion_r1388166635
Related PR Comment: https://github.com/wordpress-mobile/
WordPress-Android/pull/19552#discussion_r1388166635
Related PR Comment: https://github.com/wordpress-mobile/
WordPress-Android/pull/19552#discussion_r1388214910
Related PR Comment: https://github.com/wordpress-mobile/
WordPress-Android/pull/19552#discussion_r1388217235
Related PR Comment: https://github.com/wordpress-mobile/
WordPress-Android/pull/19552#discussion_r1388224370
Related PR Comment: https://github.com/wordpress-mobile/
WordPress-Android/pull/19552#discussion_r1388231514
Related PR Comment: https://github.com/wordpress-mobile/
WordPress-Android/pull/19552#discussion_r1388239341
Related PR Comment: https://github.com/wordpress-mobile/
WordPress-Android/pull/19552#discussion_r1389360965
Related PR Comment: https://github.com/wordpress-mobile/
WordPress-Android/pull/19552#discussion_r1389373449
@wpmobilebot
Copy link
Contributor

1 Warning
⚠️ This PR is larger than 300 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.

Generated by 🚫 Danger

Copy link
Member

@irfano irfano left a comment

Choose a reason for hiding this comment

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

Thank you for submitting this PR and addressing my comments.
LGTM. 👍🏻

@irfano irfano merged commit 9fc79ce into trunk Nov 10, 2023
20 checks passed
@irfano irfano deleted the docs/test_instructions_per_dependency_update branch November 10, 2023 15:35
@ParaskP7
Copy link
Contributor Author

Awesome, thank you so much reviewing and merging this, more so for being as thorough as you were, you rock! 🙇 ❤️ 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants