# RadControl Testing Considerations

When writing unit tests it's often convenient to use a RadControl, not as a child of a form, but standalone. This makes for faster performance and simplicity of the test setup and tear-down methods. Whenever a property having an effect on element size or children arrangement is changed explicitly, a request to the layout system is added to the queue of events to be processed. In order to force the processing of this change, the **UpdateLayout()** method has to be called on the element in question.

## See Also

* [Clipping](https://www.telerik.com/products/winforms/documentation/telerik-presentation-framework/layout/clipping)

* [Custom Layouts](https://www.telerik.com/products/winforms/documentation/telerik-presentation-framework/layout/custom-layouts)

* [Element Offset Calculations](https://www.telerik.com/products/winforms/documentation/telerik-presentation-framework/layout/element-offset-calculations)

* [Layout Activation](https://www.telerik.com/products/winforms/documentation/telerik-presentation-framework/layout/layout-activation)

* [Layout Logic](https://www.telerik.com/products/winforms/documentation/telerik-presentation-framework/layout/layout-logic)

* [Layout Overview](https://www.telerik.com/products/winforms/documentation/telerik-presentation-framework/layout/layout-overview)

* [Layout Structure](https://www.telerik.com/products/winforms/documentation/telerik-presentation-framework/layout/layout-structure)

* [Sample Arrange Stage Scenarios](https://www.telerik.com/products/winforms/documentation/telerik-presentation-framework/layout/sample-arrange-stage-scenarios)