Skip to content

Loading…

Write acceptance tests #38

Closed
jankotek opened this Issue · 1 comment

1 participant

@jankotek
Owner

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.

@jankotek
Owner

Closing, not going to fix right now

@jankotek jankotek closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.