Our build testing is automated, so if it’s a matter of pulling in a maven artifact and kicking off a build, i’m willing. Otherwise, I’m happy to share a bit of what we do on the testing front to integrate into the automated testing that’s part of struts.
-- _________________________________________________________ Adam Brin Director of Technology, Digital Antiquity 480.965.1278 > On Jul 17, 2017, at 6:16 AM, Lukasz Lenart <lukaszlen...@apache.org> wrote: > > 2017-07-17 14:35 GMT+02:00 Adam Brin <ab...@digitalantiquity.org>: >> In the automated testing we run on our application there was not one test >> that passed that used a browser backend be it Chrome or HtmlUnit without >> adjusting the regular expression. > > Is there a way to involve you and your testing in a new release > process? I'm always publishing a test build to allow everybody test it > before we will vote on it. This gives users an opportunity to stop the > release process and point out what have to be fixed before we can > start over the release process. > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
