[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] wx_test_default_input.cpp
From: |
Greg Chicares |
Subject: |
Re: [lmi] wx_test_default_input.cpp |
Date: |
Fri, 12 Dec 2014 21:07:38 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 |
On 2014-12-12 18:28, Greg Chicares wrote:
[...]
> [Vadim--this specification is being re-reviewed and may change, so
> please don't work on it before December thirteenth.]
Okay, it's all set now--I've committed a change to make it read:
// ERASE THIS BLOCK COMMENT WHEN IMPLEMENTATION COMPLETE. The block
// comment below changes the original specification, and does not
// yet describe the present code. Desired changes:
// - Run this test only when the '--distribution' option is given.
// - Write selected parameters to stdout as prescribed.
// - "EffectiveDate" is now compared to the first day of the current
// month, but should instead equal the first day of the next month.
/// Test selected parameters in the user-customizable default cell.
///
/// Run this test only when the '--distribution' option is given.
///
/// Write "ProductName" and "GeneralAccountRate" to stdout in that
/// order on a single line. We maintain several different binary
/// distributions, each with a specific default product, and that
/// product's general-account rate is a crucial parameter that often
/// varies from one month to the next, so a spot check seems wise.
///
/// The expected value of "EffectiveDate" is normally the first day
/// of the next month. (For example, to prepare a distribution that
/// is to be used beginning January first, we must run this test in
/// December, as validation should precede dissemination.)
///
/// Write both "EffectiveDate" and its expected value to stdout, both
/// as JDN and as YYYYMMDD, all on a single line, e.g.:
/// EffectiveDate: 2457024 2015-01-01 expected: 2457024 2015-01-01
/// Then print a warning on a separate line iff these two dates do not
/// match; do this after writing parameters to stdout, so that they're
/// still written even if this test abends. Inequality is an unusual
/// condition requiring attention, but not necessarily an error, so a
/// mere warning suffices; program flow should not be interrupted as
/// for an assertion failure.