<div dir="ltr"><div>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:</div><div><br></div><div>- <a href="https://github.com/geomoose/gm3/pull/1046">https://github.com/geomoose/gm3/pull/1046</a></div><div><br></div><div>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?</div><div><br></div><div>The list of tests current covered are (this list is LLM summarized):</div><div><br></div><div> Core desktop tasks (desktop.spec.js)<br> 1. Layers and backgrounds: turn the Parcels layer off and back on, then switch backgrounds and confirm only one is on at a time.<br> 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.<br> 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<br> parcel from the results.<br> 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.<br> 5. Print a map: set a title and portrait layout, then Cancel. Reopen Print and download the PDF.<br> 6. Empty selection (offline only): a query with no results shows a clear message.<br><br> Follow-up desktop tasks (desktop-workflows.spec.js)<br> 1. Selection needs a shape: pressing Go with nothing drawn shows a warning and sends no query. Drawing a polygon then works.<br> 2. Sorting: clicking a column header sorts the rows up, then down, then back to the original order.<br> 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.<br> 4. Value range filter: set a range that hides every row, then clear it. All rows come back without a new server query.<br> 5. Hide grid and cancel removal: minimizing and restoring the grid loses nothing, and cancelling a removal keeps the parcel.<br> 6. Buffer all results: buffer every result, clear the results, then select again.<br> 7. Results report: filter the results, then print a results report as a PDF.<br> 8. Parcel search: an empty search asks for input. Searching an owner's name finds their parcel.<br> 9. Favorites, Visible and Catalog: add a favorite and hide a layer from the Visible tab. The other two tabs show the same state.<br> 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.<br> 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.<br><br> Mobile (mobile.spec.js, Pixel 7 with touch)<br> 1. Catalog and tools: open the catalog, turn a layer off and on, then switch to Identify and confirm the map is still usable.<br> 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.</div><div><br></div><div>We can add some more tests based on what folks find valuable and/or what folks have found they do repeatedly. </div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Oct 12, 2026 at 8:40 PM James Klassen via geomoose-psc <<a href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">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.</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 12, 2026 at 19:34 Eli Adam <<a href="mailto:eadam@co.lincoln.or.us" target="_blank">eadam@co.lincoln.or.us</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
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. </div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Our internal testing with beta testers will probably take more than a week. Chris does have it up and running for those testers. </div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Eli</div>
<div id="m_-8180866220183541330m_-3282834851020803021appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="m_-8180866220183541330m_-3282834851020803021divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(0,0,0)"><b style="font-family:Calibri,sans-serif">From:</b> geomoose-psc <<a href="mailto:geomoose-psc-bounces@lists.osgeo.org" style="font-family:Calibri,sans-serif" target="_blank">geomoose-psc-bounces@lists.osgeo.org</a>> on behalf of TC Haddad via geomoose-psc <<a href="mailto:geomoose-psc@lists.osgeo.org" style="font-family:Calibri,sans-serif" target="_blank">geomoose-psc@lists.osgeo.org</a>><br>
<b style="font-family:Calibri,sans-serif">Sent:</b> Monday, October 12, 2026 9:03 AM<br>
<b style="font-family:Calibri,sans-serif">To:</b> Jim Klassen <<a href="mailto:klassen.js@gmail.com" style="font-family:Calibri,sans-serif" target="_blank">klassen.js@gmail.com</a>><br>
<b style="font-family:Calibri,sans-serif">Cc:</b> <a href="mailto:geomoose-psc@lists.osgeo.org" style="font-family:Calibri,sans-serif" target="_blank">geomoose-psc@lists.osgeo.org</a> <<a href="mailto:geomoose-psc@lists.osgeo.org" style="font-family:Calibri,sans-serif" target="_blank">geomoose-psc@lists.osgeo.org</a>><br>
<b style="font-family:Calibri,sans-serif">Subject:</b> Re: [geomoose-psc] Release this week?</font>
<div> </div>
</div>
<div>
<div><br>
</div>
<div dir="auto">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. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Seems reasonable to give folks the week, discuss any issues that crop up on Friday, and then release at that point.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Tanya </div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div><br>
<div>
<div dir="ltr">On Mon, Oct 12, 2026 at 8:43 AM Jim Klassen via geomoose-psc <<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Has it been tested well enough for a release? I haven't had a chance to <br>
give it a thorough run through yet, but if others have, I'm happy to <br>
mindlessly push the buttons to make a release.<br>
<br>
On 10/12/26 10:19 AM, Dan Little via geomoose-psc wrote:<br>
> Anyone have any objections to stamping a release from the current main <br>
> branch?<br>
><br>
> _______________________________________________<br>
> geomoose-psc mailing list<br>
> <a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">
https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
<br>
_______________________________________________<br>
geomoose-psc mailing list<br>
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote></div></div>
_______________________________________________<br>
geomoose-psc mailing list<br>
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</blockquote></div>