It's four new source files. What's the best way to submit?
On Oct 20, 2009, at 12:42 PM, Sean Farrell wrote:
> Do you have a patch or such?
>
>
> On Fri, Oct 16, 2009 at 11:52 PM, Demon Insight
> <v...@demoninsight.com> wrote:
>> Hi,
>> I have some working code that I would to like to add to the
>> UnitTest+
>> + codebase. It is 4 files providing the following functionality:
>>
>> 1. a predicate that can be used with RunTestIf<> and allows test
>> selection based on regex matching of "full" testcase names, those
>> being of the form <suite name>:<test name>
>> 2. a custom TestReporter implementation that does the following:
>>
>> (a) prints "pretty" START/FINISH markers for testcases. This is
>> useful for users who'd like to see some visual progress and also for
>> testcases that lock up in endless loops (and the max time limit has
>> not been enabled).
>> (b) tracks test failures and displays compact per-suite summary of
>> what failed at the end of the entire run. This is useful for users
>> who
>> tend to test from a shell and prefer to see an "all passed/something
>> failed" summary at the bottom of their screen before scrolling up,
>> drilling in, etc.
>>
>> [see examples below]
>>
>> 3. a main() file that is a somewhat more useful driver than the stock
>> Main.cpp. It brings together the above predicate and test reporter
>> and
>> provides command line options for everything:
>>
>> >test_driver -h
>> Usage: <test driver> [suite]:
>> -s [ --suite ] arg test suite to run (default: 'all')
>> -i [ --include ] arg tests to include (default: all)
>> -x [ --exclude ] arg tests to exclude (default: none)
>> -t [ --maxtesttime ] arg global test time constraint [ms] (default:
>> disabled)
>> -h [ --help ] get usage information
>>
>> It is possible to select a single UnitTest++ suite via -s option or
>> by
>> giving suite name as the only cmd line parameter. -i and -x allow
>> including and excluding testcases by name regexes, e.g.
>>
>> >test_driver -i ".*Construction.*" runs all tests in
>> all suites that
>> have to do with validating construction logic
>> >test_driver -x "dbsuite:.*" runs everything
>> *except* "dbsuite" suite
>>
>> More than one match patterns can be specified for both inclusion and
>> exclusion
>>
>> >test_driver -i "suiteA:.*, suiteB:.*" -x
>> ".*Construction.*" runs
>> suites A and B except for tests dealing with construction logic
>>
>>
>> An example of progress reporting:
>>
>> >test_driver base
>>
>> running suite [base]
>> ----------------------------------------------------------------------
>> START: some_test1 [base_tests.cpp]
>> ... std::cout output from "some_test1" ...
>> FINISH: some_test1 (0.001 s)
>> ----------------------------------------------------------------------
>> START: some_test2 [base_tests.cpp]
>> FINISH: some_test2 (0.03 s)
>> ----------------------------------------------------------------------
>> START: some_test3 [base_tests.cpp]
>> FINISH: some_test3 (0.003 s)
>> ----------------------------------------------------------------------
>> ...
>> ----------------------------------------------------------------------
>> START: some_test10 [base_tests.cpp]
>> FINISH: some_test10 (0.003 s)
>> =
>> =====================================================================
>>
>> 'base' PASSED (11 tests, 0.063 s)
>>
>> =
>> =====================================================================
>>
>>
>> An example of a test run summary [only] when something goes wrong:
>>
>> >test_driver
>> ...
>> ----------------------------------------------------------------------
>> START: some_base_test1 [base_tests.cpp]
>> *** some_base_test1 (line: 17): Expected 1 but was 2
>> FINISH: some_base_test1 (0 s)
>> ...
>> ----------------------------------------------------------------------
>> START: some_core_test1 [core_tests.cpp]
>> *** some_core_test1 (line: 10): Expected 10 but was 20
>> FINISH: some_core_test1 (0 s)
>> =
>> =====================================================================
>>
>> *** FAILURES in 'all' (2 tests/2 failures in a total of 11 test(s))
>> ***
>>
>> base:
>> {
>> 1 some_base_test1 (base_tests.cpp)
>> }
>> core:
>> {
>> 1 some_core_test1 (core_tests.cpp)
>> }
>>
>> *** FAILURES ***
>>
>>
>> The code has been in production use for some time on win32, Linux,
>> and
>> MacOS. I have cleared this code with my employers and it can be
>> released under any desired license. If there is interest, what would
>> be my next step: submit a patch?
>>
>> Cheers,
>> Vlad
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market
>> and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> unittest-cpp-devel mailing list
>> unittest-cpp-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
>>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> unittest-cpp-devel mailing list
> unittest-cpp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
unittest-cpp-devel mailing list
unittest-cpp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
