Skip to content

Component Tests

William Wyatt Earnshaw edited this page Feb 20, 2016 · 1 revision
  1. Each component type successfully creates its own ObjectPool.
  2. Unique handles are created for each object in the pool.
  3. Throws and appropriate exception if given an invalid handle, or a handle to an inactive object.
  4. Moves active objects to contiguous memory if the object pool becomes over saturated with inactive objects.