add test suite

On Thu, Sep 18, 2014 at 04:09:26AM -0700, Josef Reidinger wrote:
> struct just make code easier. It do not provide any big significant advantage.
> 
>     When I was a young boy, I had learned that object should not expose its
>     variables to the world but use functions to read or write them. I wrote
>     very few classes until now, but, if I must, I had always this golden rule
>     on my mind.
> 
> Well, this is not so nice golden rule. Golden rule is minimalize API interface
> as you need to support it and also it should not break itself. If you make all
> attributes writable, then you need to assure, that no "object.attr = blabla"
> cannot make your object inconsistent or broken.

Yeah, and there is kernel of the poodle =)) of my not-understanding.

First, I can't imagine inconsistent state of an object of the class
FontsConfigState keeping its semantics in mind.

Second, I don't know how to save some API bits. I would be really glad
if you could elaborate registration/storage.rb example you gave me
above. I see there class SSLErrors, which appears to be subclass of
Struct. Then there is class Config, which very, very resembles 
current shape of FontsConfigState.

From API view, what is the real difference between:
1. SSLErrors and Config
2. Config and FontsConfigState

Thanks :)!
Confused Noob