[Aceunit-devel] [ aceunit-Feature Requests-1873848 ] Framework should support fixture data

[SourceForge.net <no...@so...>]

Feature Requests item #1873848, was opened at 2008-01-17 16:00
Message generated for change (Comment added) made by christianhujer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1873848&group_id=207094

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core Framework
Group: None
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Christian Hujer (christianhujer)
Assigned to: Christian Hujer (christianhujer)
Summary: Framework should support fixture data

Initial Comment:
In very resource constraint environments, RAM is a scarce resource.
Test fixtures very likely will need RAM. That RAM will only be needed while this particular fixture is executed.

Theoretically, users could solve this by using overlays in linker configurations. But there is an overlay mechanism in the system that could be used instead that is provided for free: The stack.

The framework should support fixture data handled by the framework, and it should be possible for the user to configure whether that fixture data is
* allocated on the stack
* allocated on the heap
* configured by himself using overlays
or whatever.

When fixture data is limited in size, there should be means of verifying that the global fixture data space is not exceeded by a fixture.

----------------------------------------------------------------------

>Comment By: Christian Hujer (christianhujer)
Date: 2008-01-27 00:44

Message:
Logged In: YES 
user_id=465603
Originator: YES

I've closed this now. If somebody needs a more sophisticated solution,
submit a new feature request.

----------------------------------------------------------------------

Comment By: Christian Hujer (christianhujer)
Date: 2008-01-17 22:14

Message:
Logged In: YES 
user_id=465603
Originator: YES

A preliminary implementation is delivered with r304 which allows defining
a macro ACEUNIT_RUNNERDATA_EXTENSION to define additional fields for
AceUnitRunnerData_t.

I'm leaving this feature request open because we might come up with a more
sophisticated solution in future.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1873848&group_id=207094