Examples of com.volantis.mcs.protocols.TestDOMOutputBuffer

com.volantis.mcs.protocols.TestDOMOutputBuffer
A DOMOutputBuffer which is "designed" for use with test cases.
Note that the original "design" for this was simply to collect together all the existing usages demonstrated in the various inner classes which had previously extended DOMOutputBuffer before the existance of this class, so the code is not necessarily the best at the moment. However, with continued use and more refactoring, this should evolve into something which is useful for all test cases.
Make sure you run ALL the test cases if you modify this class!
NOTE: several of the methods of this class are to do with collecting output from the output buffer after it is finished. There are two basic strategies for this, the first is to collect the entire output as a string, the second is to inspect the DOM elements created. Of these two basic strategies, there are quite a few variations used in the existing test cases, as they were all implemented separately. Neither of the two here are optimal in my opinion, which is why I have deprecated them. The variations I have discovered so far are:
- Use {@link #getCurrentElement} to access DOM nodes, this seems reasonable and I have added {@link DOMProtocolTestAbstract#checkElementEquals}, etc based on this.
- Use {@link #popElement} to access DOM nodes, this seems like a duplication of the above so I have deprecated it.
- Use {@link com.volantis.mcs.protocols.html.XHTMLBasicTestCase#bufferToString}(which is based on {@link com.volantis.mcs.dom.DOMUtilities#toString}) to get the output as a String, this seems reasonable.
- Use {@link #getWriter}, and cast it to a {@link StringWriter} to getthe output as a String, seems like a duplication of the above so I have deprecated it.
- Use {@link DOMProtocolTestAbstract.MyPageOutputBuffer#getWriter} which is a variation on this class, it has a to do to that effect.
Note that I have also discovered {@link com.volantis.mcs.protocols.wml.WMLRootTestCase#transformMarkup} to normalise expected markup strings, this should be combined with whatever approach you choose above.

     * This is an extra test for doImage - tests align
     */
    public void testStyleVerticalAlignIMG() throws Throwable {
        privateSetUp();
        protocol.setMarinerPageContext(pageContext);
        TestDOMOutputBuffer buffer = new TestDOMOutputBuffer();
        buffer.initialise();


        MutablePropertyValues properties = createPropertyValues();


        // The middle attribute has to be set in the image attribute and not int the SSP
        // Since images do not go through the emulation renderer

View Full Code Here

     * Test that body text and background colour are set.
     */
    public void testBodytextColour() throws Exception {
        privateSetUp();
        protocol.setMarinerPageContext(pageContext);
        TestDOMOutputBuffer buffer = new TestDOMOutputBuffer();
        buffer.initialise();


        CanvasAttributes canvas = new CanvasAttributes();
        canvas.setStyles(StylesBuilder.getDeprecatedStyles());


        BodyAttributes attributes = new BodyAttributes();

View Full Code Here

     * not supported in i-mode in body.
     */
    public void testNoBackgroundImageInBody() throws Exception {
        privateSetUp();
        protocol.setMarinerPageContext(pageContext);
        TestDOMOutputBuffer buffer = new TestDOMOutputBuffer();
        buffer.initialise();


        CanvasAttributes canvas = new CanvasAttributes();
        canvas.setStyles(StylesBuilder.getDeprecatedStyles());


        BodyAttributes attributes = new BodyAttributes();

View Full Code Here




        helper.addOption(group, "Caption3", "Prompt3", "Value3",
                selectedOtions[2]);


        TestDOMOutputBuffer buffer = new TestDOMOutputBuffer();


        propertyValues.setComputedValue(
                StylePropertyDetails.MCS_SELECTION_LIST_STYLE,
                MCSSelectionListStyleKeywords.CONTROLS);
        propertyValues.setComputedValue(

View Full Code Here


        group = helper.addOptionGroup(atts, "Group4", "Prompt4");
        helper.addOption(group, "Caption2", "Prompt2", "Value2", false);




        TestDOMOutputBuffer buffer = new TestDOMOutputBuffer();
        testable.setCurrentBuffer(atts.getEntryContainerInstance(), buffer);


        StringBuffer sb = new StringBuffer();


        sb.append("<select ");

View Full Code Here

                    "Value" + (i + 1),
                    selectedOptions[i]);
        }




        TestDOMOutputBuffer buffer = new TestDOMOutputBuffer();


        TestMarinerPageContext testPageContext =
                (TestMarinerPageContext) protocol.getMarinerPageContext();
        testPageContext.setFormFragmentResetState(true);

View Full Code Here

0 1 2 3 4 5 6

TOP

Related Classes of com.volantis.mcs.protocols.TestDOMOutputBuffer

com.volantis.mcs.dom2wbsax.WBSAXOutputterTestCase

com.volantis.mcs.protocols.html.HTML_iModeTestCase

com.volantis.mcs.protocols.html.HTMLVersion4_0_IE6TestCase

com.volantis.mcs.protocols.html.MMLBasicTestCase

com.volantis.mcs.protocols.html.XHTMLBasicTestCase

com.volantis.mcs.protocols.html.XHTMLFullTestCase

com.volantis.mcs.protocols.menu.shared.MenuEntityCreation

com.volantis.mcs.protocols.menu.shared.model.ConcreteMenuTestCase

com.volantis.mcs.protocols.menu.shared.renderer.AbstractStyledTextMenuItemRendererTestAbstract

com.volantis.mcs.protocols.menu.shared.renderer.ConcreteMenuBufferTestCase

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.