On Thu, 6 Sep 2018 at 23:06, Cyril Ferlicot D. <[email protected]> wrote: > > > Maybe we could have a package with release tests that are not executed > by the CI but that are executed at the moment of the feature freeze and > some time before the Pharo release to ensure the quality of the code > base for tests that are too long?
The drawback of this approach is that it relies on the original author going back and submitting a fix in a timely manner (quite possibly after they've moved on to other things). If the tests could be run on a specified set of classes / methods, perhaps we could run them as part of Iceberg, i.e. when going to commit code, these tests are run on the classes in the commit and a warning opened prompting the user to fix them before actually committing. Cheers, Alistair
