You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JDBM tests currently runs for couple of minutes. But we need better test suite to test JDBM before each release. It should run approximately week and should require 4 GB RAM and 100 GB HDD space.
I would like to keep tests fast, but this test should be also part of JDBM. So JDBM will have two modes:
There will be static final boolean field in CompileConfig.TESTED_RELEASE.
When set to false, only basic unit tests will be run for couple of minutes. At initialization JDBM will also log an warning that this release is dev version and did not passed acceptance tests.
When set to true, full battery of acceptance tests will be run. This will require significant resources and will for several days, before all tests pass. At startup JDBM will not display any warnings as this release probably passed all tests.
In git sources and during development time this flag will be off. Before release I flip it on locally and build release jar.
The text was updated successfully, but these errors were encountered:
JDBM tests currently runs for couple of minutes. But we need better test suite to test JDBM before each release. It should run approximately week and should require 4 GB RAM and 100 GB HDD space.
I would like to keep tests fast, but this test should be also part of JDBM. So JDBM will have two modes:
There will be static final boolean field in CompileConfig.TESTED_RELEASE.
When set to false, only basic unit tests will be run for couple of minutes. At initialization JDBM will also log an warning that this release is dev version and did not passed acceptance tests.
When set to true, full battery of acceptance tests will be run. This will require significant resources and will for several days, before all tests pass. At startup JDBM will not display any warnings as this release probably passed all tests.
In git sources and during development time this flag will be off. Before release I flip it on locally and build release jar.
The text was updated successfully, but these errors were encountered: