right now tests are only run against known target stores using their zip or city
Why Test?
irl there could be instances where cities are queried that dont pass the place input validation.
having more comprehensive test data could find more unknown defects that would otherwise be found by end users
Proposed Solution
include the whole target store locations database
use a goelocation algorithm to return expected target store locations and randomly derive zip codes and city and zip code test data
Why Proposed Solution
people aren't going to query nearby stores to a known store location, irl it will be relative to things like their current position, or a landmark or something.
Alternative
just feed in the whole target store location db w/o changing the zip code / city feed.
Test Requirements
[ ] tests include data from not just utah
[ ] tests include random zip codes and cities, not just spoon fed data from store locations.
Additional Context
I think robots.txt would have sitemap info on this information
Summary
right now tests are only run against known target stores using their zip or city
Why Test?
Proposed Solution
Why Proposed Solution
people aren't going to query nearby stores to a known store location, irl it will be relative to things like their current position, or a landmark or something.
Alternative
just feed in the whole target store location db w/o changing the zip code / city feed.
Test Requirements
Additional Context
I think robots.txt would have sitemap info on this information
Code of Conduct