I’m currently testing GeoServer 2.8 version with the integrated GeoFence.
To automate this testing, e.g. ensuring every pages of the GS UI is working correctly after setup, I developed a Capybara scenario, testing that no page titles are matching “Oops something went wrong” pattern, when browsing every UI pages.
Source code: [1]
This produces the following result for now (YouTube video[2]). Please note that this is an early preview of this work, but it can already give an idea of the testing potential of the tool.
I was wondering if the GeoServer community was interested in this, and if this work could be relevant for the project.
That may be amazing, we are thinking of doing a code-sprint to upgrade to a newer version of wicket, this kind of automated abuse may be able to quickly support the team doing the upgrade.
If others are interested perhaps you can join the next project Skype call?
Looking at your video a stack trace passed your “Oops something went wrong” test? I was also amused to see the product renamed as geOrchestra
I’m currently testing GeoServer 2.8 version with the integrated GeoFence.
To automate this testing, e.g. ensuring every pages of the GS UI is working correctly after setup, I developed a Capybara scenario, testing that no page titles are matching “Oops something went wrong” pattern, when browsing every UI pages.
Source code: [1]
This produces the following result for now (YouTube video[2]). Please note that this is an early preview of this work, but it can already give an idea of the testing potential of the tool.
I was wondering if the GeoServer community was interested in this, and if this work could be relevant for the project.
