How to test a library?

How to test a library?

[Victor Porton]

What is the correct way to test a (shared) library I am going to create?

I assume there are special libraries for unit tests or something like this. 
Where to get more info on this?

-- 
Victor Porton - http://portonvictor.org

Re: How to test a library?

[Shark8]

On 21-May-14 13:34, Victor Porton wrote:
> What is the correct way to test a (shared) library I am going to create?
>
> I assume there are special libraries for unit tests or something like this.
> Where to get more info on this?
>


I don't know if there's an official way to do it; but what I'd be 
inclined to do is have a testbed-program (that tests all the [exported] 
subprograms of the library) and issues a report.

Re: How to test a library?

[mockturtle]

On Wednesday, May 21, 2014 9:34:46 PM UTC+2, Victor Porton wrote:
> What is the correct way to test a (shared) library I am going to create?
> 
> I assume there are special libraries for unit tests or something like this. 
> Where to get more info on this?
> 

I know about AUnit that is available on the AdaCore site.  If I remember correctly, it is integrated in some way inside GPS.  However, I never used it since I use my own home-brew library suited for my own need.

As a side note, I find it very convenient to have the test code being a procedure that is a child of the tested package.  For example, the test for package foo.bar could be

    procedure Foo.Bar.Test is
      ...
    end Foo.Bar.Test;

Of course, if you use GPS/GNAT you must register in the project file that foo-bar-test.adb is a main.

In this way you have also the visibility of the internal details of your package and sometimes (not often, at least in my experience) this is useful in testing.   Also, I like this solution for its "cleanness," since the package brings its own test with it...

Riccardo