Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write acceptance tests #38

Closed
jankotek opened this issue Mar 19, 2012 · 1 comment
Closed

Write acceptance tests #38

jankotek opened this issue Mar 19, 2012 · 1 comment

Comments

@jankotek
Copy link
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
Copy link
Owner Author

jankotek commented May 9, 2012

Closing, not going to fix right now

@jankotek jankotek closed this as completed May 9, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant