Lumiera 0.pre.04~rc.1
»edit your freedom«
Loading...
Searching...
No Matches
Digxel_test Class Reference

Description

Test:
verify correct behaviour of an display "Digxel": A self-contained numeric element to support building displays.
  • build a Digxel
  • set a value
  • retrieve formatted display
  • verify comparisons and increments
  • performing side-effects from the setter-functor
  • formatted value caching

Definition at line 137 of file digxel-test.cpp.

Private Member Functions

virtual void run (Arg arg)
 
void checkSimpleUsage ()
 
void checkMutation ()
 
void verifyMutatorInfluence ()
 
void verifyAssignMutatingOperators ()
 
void verifyComparisons ()
 
void checkCopy ()
 
void checkDisplayOverrun ()
 
void timingMeasurements ()
 

Member Function Documentation

◆ run()

virtual void run ( Arg  arg)
inlineprivatevirtual

Definition at line 140 of file digxel-test.cpp.

References Digxel_test::checkCopy(), Digxel_test::checkDisplayOverrun(), Digxel_test::checkMutation(), Digxel_test::checkSimpleUsage(), Digxel_test::timingMeasurements(), Digxel_test::verifyAssignMutatingOperators(), Digxel_test::verifyComparisons(), and Digxel_test::verifyMutatorInfluence().

+ Here is the call graph for this function:

◆ checkSimpleUsage()

void checkSimpleUsage ( )
inlineprivate

Definition at line 158 of file digxel-test.cpp.

Referenced by Digxel_test::run().

+ Here is the caller graph for this function:

◆ checkMutation()

void checkMutation ( )
inlineprivate

Definition at line 173 of file digxel-test.cpp.

Referenced by Digxel_test::run().

+ Here is the caller graph for this function:

◆ verifyMutatorInfluence()

void verifyMutatorInfluence ( )
inlineprivate

Definition at line 197 of file digxel-test.cpp.

Referenced by Digxel_test::run().

+ Here is the caller graph for this function:

◆ verifyAssignMutatingOperators()

void verifyAssignMutatingOperators ( )
inlineprivate
Test:
verify the self-assigning increment/decrement operators.
Note
especially these need to invoke the mutator function, much like a direct assignment. We use a special mutator to protocol the previous / new value.

Definition at line 232 of file digxel-test.cpp.

Referenced by Digxel_test::run().

+ Here is the caller graph for this function:

◆ verifyComparisons()

void verifyComparisons ( )
inlineprivate

Definition at line 264 of file digxel-test.cpp.

Referenced by Digxel_test::run().

+ Here is the caller graph for this function:

◆ checkCopy()

void checkCopy ( )
inlineprivate

Definition at line 289 of file digxel-test.cpp.

Referenced by Digxel_test::run().

+ Here is the caller graph for this function:

◆ checkDisplayOverrun()

void checkDisplayOverrun ( )
inlineprivate
Test:
Digxel should be protected against display buffer overrun

Definition at line 311 of file digxel-test.cpp.

References VERIFY_ERROR.

Referenced by Digxel_test::run().

+ Here is the caller graph for this function:

◆ timingMeasurements()

void timingMeasurements ( )
inlineprivate
Test:
perform several timing measurements and especially verify the effect of caching formatted values. Digxel avoids reformatting unchanged values; besides that it is possible to install a "mutator" functor for invoking all kinds of special behaviour on value changes. Of course doing so comes with a (considerable) price tag....
Note
the measurement especially show the effects of locality, which can vary largely over several runs.

Definition at line 336 of file digxel-test.cpp.

References DISPLAY_TIMINGS, and START_TIMINGS.

Referenced by Digxel_test::run().

+ Here is the caller graph for this function:
+ Inheritance diagram for Digxel_test:
+ Collaboration diagram for Digxel_test:

The documentation for this class was generated from the following file: