[FlopCpp-tickets] [FlopC++] #13: Add a series of unit test programs which aren't really examples, but test bits of functionality

[FlopC++]

#13: Add a series of unit test programs which aren't really examples, but test
bits of functionality
-------------------------+--------------------------------------------------
 Reporter:  hpwalton     |       Owner:  somebody
     Type:  enhancement  |      Status:  new     
 Priority:  normal       |   Milestone:          
Component:  component1   |     Version:          
 Severity:  normal       |    Keywords:          
-------------------------+--------------------------------------------------
 Motivation:
 Much of FlopC++ is untested in the current examples code.  This in itself
 is fine.  However, there are cases with MSVC where runtime code may not
 behave as expected even if the compile is successful.  This _can_ be the
 case with other compilers, but is less likely.

 Further, when working with multiple environments, changes which work in
 one environment may have subtle differences in other environments.  These
 can cause difficulties and behavior issues.

 Proposal:
 Create some simple unit tests for each major publicly exposed object
 which:
 1- At a minimum calls every method with a few different settings for
 parameters.
 2- Detects and verifies expected outcomes.
 3- Is set up in such a way that multiples can be run together if desired.
 4- Can be readily updated to regression test bugs which are found and
 repaired...thus eliminating the cause of repeated bugs.
 5- Can be used to ensure that extensions are unlikely to break existing
 code.

 I have some further ideas on this...if this is interesting I can create
 and attach additional information.

-- 
Ticket URL: <https://projects.coin-or.org/FlopC++/ticket/13>
FlopC++ <http://example.com/>
My example project