Use features instead of ApplyFlags:

tapENABLE_TESTING is removed from checks, and feature enablement
is the sole method for activating features. Unit tests are updated
to enable required features in the construction of the Env.

Tickets are put on a feature switch instead of a build macro.
This commit is contained in:
Vinnie Falco
2015-12-17 15:35:56 -05:00
parent 48e0466a2b
commit a5583de6e6
17 changed files with 64 additions and 81 deletions

View File

@@ -66,8 +66,7 @@ struct Regression_test : public beast::unit_test::suite
OpenView accum(&*next);
auto const result = ripple::apply(env.app(),
accum, *jt.stx, tapENABLE_TESTING,
env.journal);
accum, *jt.stx, tapNONE, env.journal);
expect(result.first == tesSUCCESS);
expect(result.second);
@@ -93,8 +92,7 @@ struct Regression_test : public beast::unit_test::suite
OpenView accum(&*next);
auto const result = ripple::apply(env.app(),
accum, *jt.stx, tapENABLE_TESTING,
env.journal);
accum, *jt.stx, tapNONE, env.journal);
expect(result.first == tecINSUFF_FEE);
expect(result.second);