[geomoose-psc] Release this week?

[Dan Little]

I'm not sure as to the complete reliability of these first rounds of tests.
I configured and setup the playwright tests but then worked with some
models to create some additional tests. The branch is here:

- https://github.com/geomoose/gm3/pull/1046

For folks who have some favorite workflows for testing, maybe we can
automate it a little bit more so we have some higher confidence in the
releases?

The list of tests current covered are (this list is LLM summarized):

  Core desktop tasks (desktop.spec.js)
  1. Layers and backgrounds: turn the Parcels layer off and back on, then
switch backgrounds and confirm only one is on at a time.
  2. Identify: turn on Vector Parcels and confirm the outlines draw on the
map. Click a parcel and check that its PIN and owner appear.
  3. Select, zoom, export, remove: draw a box to select parcels and zoom to
one. Download the CSV and check it holds that parcel, then remove the
     parcel from the results.
  4. Buffer and feature report: buffer a selected parcel by 100 ft and run
the new selection. Open the parcel's report and download it as a PDF.
  5. Print a map: set a title and portrait layout, then Cancel. Reopen
Print and download the PDF.
  6. Empty selection (offline only): a query with no results shows a clear
message.

  Follow-up desktop tasks (desktop-workflows.spec.js)
  1. Selection needs a shape: pressing Go with nothing drawn shows a
warning and sends no query. Drawing a polygon then works.
  2. Sorting: clicking a column header sorts the rows up, then down, then
back to the original order.
  3. PIN filter: filter to one PIN and check the CSV holds only that
parcel. Cancel leaves the filter in place, and Clear brings back every
result.
  4. Value range filter: set a range that hides every row, then clear it.
All rows come back without a new server query.
  5. Hide grid and cancel removal: minimizing and restoring the grid loses
nothing, and cancelling a removal keeps the parcel.
  6. Buffer all results: buffer every result, clear the results, then
select again.
  7. Results report: filter the results, then print a results report as a
PDF.
  8. Parcel search: an empty search asks for input. Searching an owner's
name finds their parcel.
  9. Favorites, Visible and Catalog: add a favorite and hide a layer from
the Visible tab. The other two tabs show the same state.
  10. Bookmark: zoom to a parcel and copy the bookmark link. Opening the
link restores the layers and map location, even with local storage cleared.
  11. Identify after turning a layer off: after the layer is turned off,
clicking the map shows no stale results and sends no new query.

  Mobile (mobile.spec.js, Pixel 7 with touch)
  1. Catalog and tools: open the catalog, turn a layer off and on, then
switch to Identify and confirm the map is still usable.
  2. Identify (live only): tap a parcel and get real details from the
server. Switch to the map and back, and the results are still there.

We can add some more tests based on what folks find valuable and/or what
folks have found they do repeatedly.

On Mon, Oct 12, 2026 at 8:40 PM James Klassen via geomoose-psc <
geomoose-psc at lists.osgeo.org> wrote:

> I have a couple main job projects due at the end of the month.  I can make
> a release, but testing it given the amount of change will likely take more
> time than I have until November.  If we want a release before then (and
> roughly equivalently before FOSS4G-NA), my testing will be limited.
>
> On Mon, Oct 12, 2026 at 19:34 Eli Adam <eadam at co.lincoln.or.us> wrote:
>
>> I'm not in a rush if Jim will have a chance to look at it.  He has a
>> different perspective on things that I often appreciate.
>>
>> Our internal testing with beta testers will probably take more than a
>> week.  Chris does have it up and running for those testers.
>>
>> Eli
>> ------------------------------
>> *From:* geomoose-psc <geomoose-psc-bounces at lists.osgeo.org> on behalf of
>> TC Haddad via geomoose-psc <geomoose-psc at lists.osgeo.org>
>> *Sent:* Monday, October 12, 2026 9:03 AM
>> *To:* Jim Klassen <klassen.js at gmail.com>
>> *Cc:* geomoose-psc at lists.osgeo.org <geomoose-psc at lists.osgeo.org>
>> *Subject:* Re: [geomoose-psc] Release this week?
>>
>>
>> I was going to remind everyone to do some testing this week ahead of the
>> PSC meeting, now that all the major PRs have been merged.
>>
>> Seems reasonable to give folks the week, discuss any issues that crop up
>> on Friday, and then release at that point.
>>
>> Tanya
>>
>>
>>
>> On Mon, Oct 12, 2026 at 8:43 AM Jim Klassen via geomoose-psc <
>> geomoose-psc at lists.osgeo.org> wrote:
>>
>> Has it been tested well enough for a release?  I haven't had a chance to
>> give it a thorough run through yet, but if others have, I'm happy to
>> mindlessly push the buttons to make a release.
>>
>> On 10/12/26 10:19 AM, Dan Little via geomoose-psc wrote:
>> > Anyone have any objections to stamping a release from the current main
>> > branch?
>> >
>> > _______________________________________________
>> > geomoose-psc mailing list
>> > geomoose-psc at lists.osgeo.org
>> > https://lists.osgeo.org/mailman/listinfo/geomoose-psc
>>
>> _______________________________________________
>> geomoose-psc mailing list
>> geomoose-psc at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/geomoose-psc
>>
>> _______________________________________________
> geomoose-psc mailing list
> geomoose-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-psc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20261013/7918eb10/attachment.htm>