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.

Sign up for GitHub

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

Jump to bottom

Android: QA for release v3.8.8 #2738

Closed
79 tasks done
aanorbel opened this issue May 30, 2024 · 1 comment
Closed
79 tasks done

Android: QA for release v3.8.8 #2738

aanorbel opened this issue May 30, 2024 · 1 comment
Assignees
@aanorbel
Labels
priority/medium

Comments

@aanorbel
Copy link
Member

aanorbel commented May 30, 2024 •
edited
Loading

Preparing the master branch for release

  • (android) app/build.gradle: use the latest probe-cli
  • (android) engine/build.gradle: use the latest probe-cli
  • (android) app/build.gradle: bump version number and code
  • (android) app/build.gradle: possibly upgrade the SDKs
  • update the translation strings
  • merge any other feature PR we may need

(android) Preparing a stable full release

Tests and results

  • while a nettest is running
    • put the app in the background and ensure you can come back with an decreased ETA
    • check that the title changes as we change the nettests we're running
  • after the test has run
    • ensure the number of run tests has been updated
    • check that the data usage numbers have increased
    • try to adjust the filter and validate that only the filtered results appear
    • tap the result row
      • check that the last run test is highlighted
      • check that the date & time of the test are correct and displayed in the timezone of the phone
      • check that the country & network are resolved properly
    • tap the measurement row
      • check that the country & network are resolved properly
      • check that it’s possible to view the log
      • check that it’s possible to view data
        • check that the report_id is not "", unless publish result is disabled (see settings test section)
        • check that the test_start_time in the measurement is using GMT
    • disable automatic measurement upload
      • check that the upload all (or individual upload) toast is shown
      • tap on upload on an individual test and check it works
      • tap on upload all and check it works
  • run the websites tests
    • tap on Choose Websites
    • tap on settings and re-run the test changing
      • the test duration to a very short runtime
      • enabling only one category to test and checking on that is tested
      • enabling zero categories should not crash the app
    • tap the result row
      • check that the summary shows some number blocked some accessible
      • check that the blocked sites are displayed first
      • check that the icons are displayed next to each test
      • check that the data usage shows a sane number, ex 6.3MB up, 5.8MB down
      • check that the total runtime shows a sane number, ex. 257s
    • tap the measurement row
      • check that everything is displayed properly in this screen
      • check that the runtime is sane ex 2.71s
      • repeat this for on measurement which is OK and one which is blocked (if present)
  • run the IM tests
    • tap on settings and re-run the test changing
      • disable telegram, signal and facebook messenger; check that only whatsapp is run
    • tap on the result row
      • check that the total counts on top match
      • check that the data usage shows a sane number, ex 36KB up, 18KB down
      • check that the total runtime shows a sane number, ex. 2.16s
  • run the performance test
    • tap on settings and re-run the test changing
      • disable all tests but dash; check that only dash is run
    • check that you see upload, download and video speed in the summary
    • tap the result row
      • check that the summary view has video, upload, download and ping
      • check that the data usage shows a sane number, ex 22MB up, 104MB down
      • check that the total runtime shows a sane number, ex. 54s
    • tap the measurement row
      • check that everything is OK

Settings

  • notifications
    • (ios) disable notifications in the system settings and then tab to re-enable them and make sure it asks you to enable notifications from the system settings
    • (android) disable notifications for OONI Probe from android settings and make sure that installing the app asks for the dynamic permission of enabling notifications
  • advanced
    • enable debug logs and run a test; check that the logs are at debug level verbosity

About

  • make sure all links are working as intended

OONI Run v1

We should also test the following links using OONI Run v1. The original document did not spell out which was the source from which we should be trying to load the links, so for now I'd say it's fine to try and use GitHub.
@aanorbel aanorbel assigned bassosimone and unassigned bassosimone May 30, 2024
@aanorbel aanorbel mentioned this issue May 30, 2024
Merged
@aanorbel aanorbel self-assigned this May 31, 2024
@jbonisteel
Copy link
Contributor

Approved to proceed with shipping

aanorbel added a commit to ooni/probe-android that referenced this issue Jun 4, 2024
@aanorbel
chore(release): prepare app for v3.8.8 release (#748)
103926d 
Part of ooni/probe#2738

## Proposed Changes

  - Update translations.
  - Update version code and name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aanorbel aanorbel

Labels
priority/medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bassosimone @jbonisteel @aanorbel