| com.opensymphony.webwork.WebWorkTestCase com.opensymphony.webwork.views.jsp.AbstractTagTest
All known Subclasses: com.opensymphony.webwork.views.jsp.ui.DateTagTest, com.opensymphony.webwork.components.URLTest, com.opensymphony.webwork.views.jsp.SubsetIteratorTagTest, com.opensymphony.webwork.views.jsp.TextTagTest, com.opensymphony.webwork.views.jsp.AppendIteratorTagTest, com.opensymphony.webwork.components.ComponentTest, com.opensymphony.webwork.views.jsp.IncludeTagTest, com.opensymphony.webwork.views.jsp.ActionTagTest, com.opensymphony.webwork.views.jsp.SortIteratorTagTest, com.opensymphony.webwork.views.jsp.MergeIteratorTagTest, com.opensymphony.webwork.views.jsp.IteratorGeneratorTagTest, com.opensymphony.webwork.views.jsp.AbstractUITagTest,
AbstractTagTest | abstract public class AbstractTagTest extends WebWorkTestCase (Code) | | Base class to extend for unit testing UI Tags.
author: jcarreira |
Method Summary | |
public Action | getAction() Constructs the action that we're going to test against. | protected void | setUp() | protected void | tearDown() |
writer | protected StringWriter writer(Code) | | contains the buffer that our unit test will write to. we can later verify this buffer for correctness.
|
getAction | public Action getAction()(Code) | | Constructs the action that we're going to test against. For most UI tests, this default action should be enough.
However, simply override getAction to return a custom Action if you need something more sophisticated.
the Action to be added to the OgnlValueStack as part of the unit test |
|
|