• entries
    383
  • comments
    1075
  • views
    352274

Testing times

Sign in to follow this  
Trapper Zoid

51 views

Using Boost's test library I've crafted together a unit testing framework for black box testing of my library components. To start with I've written a couple of test cases for the signal system.

My tests so far have been successful. And by "successful", I mean they found an annoying memory allocation bug that would have bitten me on the arse if I'd have just ploughed ahead with the rest of my engine. I'm not sure what's going on in there, but my stress test found that if you disconnect and reconnect slots from signals over and over again that my hacked together memory manager can't cope.

Something is assuredly broken in there, but I'm not sure if it's worth the effort to fix. It's probably better if I replace my hacked together memory manager with something like Boost's pool system, which I found out about with a recent query on the forums. I'm sure Boost handles memory far better than I do, and it will clean up the nasty hacks I had to do to use a std::vector as a memory pool.

This means I've actually gone back a step on my check list; I'm back to working on signals again. Hopefully the new version will pass the unit testing phase.

Sign in to follow this  


0 Comments


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now