Mid to late 2015, we had some experiments with SauceLabs to see if thteir infrastructure could help, but nothing came immediately from it.
Instead of fixing the reported problems in the same ad-hoc manner we have been for years, I decided to bite the bullet and start developing browser based tests. Taking advantage of our lagging adoption of these, we're able to do it first-time-right: I'm using BDD (Test::BDD::Cucumber) to specify the application behaviours, abstracting away page accesses behind a PageObject model. One of the reasons to go for BDD is to open up contribution of test-scripts to a wider audience than just the core LedgerSMB developers.
With these efforts, I've been able to nearly-double the test coverage in 5 days: 11.7% on Tuesday to 22.3% today!
As you can see, we've been very busy developing infrastructure supportive of releasing higher quality software -- at the expense of visible progress in terms of release size and timing. When we release 1.5.0, we want it to be better than any of the .0 versions we released so far and we're working hard to make it so.
All in all: we're delayed, but we're using that time to improve application quality. Not by doing major (destabilizing) code rewrites, but by implementing rigorous automated quality validations.
If you feel like helping out improving our quality checks: with our choice for BDD, we have lowered the barrier of entry to contribution. To contribute a BDD script, have a look at the scripts we already have in place at https://github.com/ledgersmb/LedgerSMB/tree/master/t/66-cucumber/01-basic
; we don't ask contributors to write the step implementations: just the BDD script. We'll implement the missing steps.
Robust and Flexible. No vendor lock-in.