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

Prelease QA Pass #734

Closed
21 tasks
danrademacher opened this issue Apr 3, 2024 · 8 comments
Closed
21 tasks

Prelease QA Pass #734

danrademacher opened this issue Apr 3, 2024 · 8 comments
Assignees
Labels
infrastructure Deploy / Infrastructure issues

Comments

@danrademacher
Copy link
Member

@Rub21 once this ohm-deploy is ready but BEFORE we dpeloy to prod, let's have your team do a QA pass. Can you reassign when ready?

Website

  • User creation
  • User Login in website
  • Check all the important URLs route on the site, navigating between them and confirming that login is respected
    • Verify that all tabs in the main page load correctly: GPS Traces, User Diaries, Copyright, Help, About
    • Verify that all URLs in the breakdown of user name work correctly: My Dashboard, My Messages, My Profile, My Settings, My Preferences
  • Verify that enhanced inspector is loading. For example, this Way should load a slideshow with photos. If it does not, that usually means we need to adjust our injection code to target changed HTML in the upstream code.
  • Search for a location using the search bar
  • User logout

iD

  • Make edition for each object (Edit, Update and Remove): node, way, relations in dates start_date=1800 and end_date=2023 and make sure to add a name name=<uniq> , because name is gong to be used to test in nominatim
    • Make an edit with something we know is symbolized clearly on the map
    • Examples: Landuse, Buildings, highways, POI
      - [ ] Upload changesets
      - [ ] View the changeset and note if session persists

JOSM

Minute replication reflects the changesets

Tiler

  • Confirm that the edit is appearing in the vector tiles in a timely manner (10 min)
  • Play with the range dates in the website, according the start_date and end_date tags of the features.

Nominatim

Overpass

Taginfo

Note: taginfo is been updating every week, so it may not be necessary to test.

cc @erictheise

@danrademacher danrademacher added the infrastructure Deploy / Infrastructure issues label Apr 3, 2024
@erictheise
Copy link
Member

@Rub21, I would like to add one subtask to "User creation" and that is to verify in the database that the user's consider_pd field is set to true. The field has been removed from the interface and the migration in this release should default to that. Thanks.

@Rub21
Copy link

Rub21 commented Apr 3, 2024

@danrademacher sounds good,

I will Let karito know about this.

@Rub21
Copy link

Rub21 commented Apr 4, 2024

@karitotp 👇

Confirm TagInfo is consuming and updating diffs

the right url will be: https://taginfo.staging.openhistoricalmap.org/keys

@karitotp
Copy link

karitotp commented Apr 5, 2024

@Rub21, I did tests according our checklist and most of them has passed

Website

🟢 All tests in staging and production has passed

ID

ID Production:
🟢 All tests has passed

ID staging:
🔴 The Start Date and End Date do not allow adding month and day, the entered values are cleaned when clicking out the field

Screencast.2024-04-04.15.58.45.mp4

JOSM

🟢 All editions tests in staging and production has passed

Minute replication reflects the changesets

🟢 Edits made in Production are only updated in Planet Production - https://planet.openhistoricalmap.org/

Tiler

🟢 Edits made in Production appear in Staging and Production website

Nominatim

🟢 The editions of places in Production are found in Staging and Production Nominatim

Overpass

🟢 Edits made in Production appear in Staging and Production Overpass

OSMCha

🟢 Edits made in Production are updating correctly in Staging and Production OSMCha

@danrademacher
Copy link
Member Author

@erictheise can you look at this?

ID staging:
🔴 The Start Date and End Date do not allow adding month and day, the entered values are cleaned when clicking out the field

@erictheise
Copy link
Member

Saw the results, @danrademacher, will get to it mid day.

@1ec5
Copy link
Member

1ec5 commented Apr 5, 2024

We should probably track individual regressions in separate tickets when possible, in case they need deeper investigation.

I wonder if this is related to openstreetmap/iD#10145. Have we pulled in the fix in openstreetmap/iD#10151?

@danrademacher
Copy link
Member Author

Yeah, separate tickets is the best Here's this one #737

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Deploy / Infrastructure issues
Projects
Development

No branches or pull requests

5 participants