Repository navigation
Add regression suite and source-aware legends - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
static,browser,full, andrecoveryprofilesmain台湾省naming across package prompts, resource names, feature details, and world-overview labelsWhy
The repository had strong individual smoke scripts, but no single development workflow or durable catalog connecting past regressions to the checks that prevent them. The documented performance command also could not run from the UI-test image because the script and baseline were not copied into it.
Running the new full suite additionally exposed repeated weather synchronization failures for newly installed country packages. The Windows checkout supplied a CRLF JQ program to a Debian container, where JQ rejected the carriage return before processing the first uncached country.
The previous fixed legend also did not explain the symbols of the map source currently on screen. It now follows source and layer state, with compact defaults and expandable details.
Impact
Developers can now choose a test cost appropriate to each change, while GitHub catches repository and documentation regressions without requiring the private local GIS payload. Runtime and recovery profiles remain local because they depend on the prepared eight-service stack and offline products.
Map users now get an accurate legend when switching between detailed offline/online sources and the low-zoom world overview, including currently enabled overlays.
Validation
static: 6 JSON files, 47 PowerShell scripts, 21 bilingual pairs, 194 local Markdown links, 16 test cases, 3 performance samples, and 4 browser testsfullprofile: passed in 423.8 seconds before the legend-only follow-upgit diff --cached --check: passedThe isolated
recoveryprofile was added but not run for this change because no recovery payload or recovery implementation changed.