Explore BrainMass

From Dynamic HTML to DOM Scripting

This content was STOLEN from BrainMass.com - View the original, and get the already-completed solution here!

Assess the changes that have taken place in the journey from Dynamic HTML to DOM scripting.

© BrainMass Inc. brainmass.com October 25, 2018, 8:24 am ad1c9bdddf

Solution Preview

Question: Assess the changes that have taken place in the journey from Dynamic HTML to DOM scripting.


Every web-related technologies used in the vast domain of web that are to become a worldwide standard have to be agreed by the W3C [5]. DHTML [3] or Dynamic HTML is not one of these standards or a standalone technology. DHTML refers to the act of using the web standards JavaScript, CSS and HTML together to create web pages that appear to be dynamic. The pages built with DHTML only appear to be dynamic as they change their look without the need to reload. The dynamic pages which are real does a different job: they retrieve and send data from and to the backend systems [1]. The principle aim of DHTML was to perform the impossible tasks which were seemingly impossible in the past such as make pages look very dynamic, move things around on the click of a mouse or with timed animation and generally make web pages more engaging [1].

The very cool effect of the DHTML lost its impact rather quickly, especially when some of the browsers were unable to support it and they ended up on a page that was a dead end. As DHTML itself was considered as a great concept, it did bring out a kind of elitism to a certain group of developers such as the JavaScript developers; they did not put much importance in keeping the 'maintainable' property ...

Solution Summary

The expert forms dynamic HTML to DOM Scripting.

See Also This Related BrainMass Solution

Web Service Unit Testing Tools

I need assistance in the following problem please.
I am supposed to write 800 my own words with referencing please.

We have discussed a few web service Following are the Unit testing tools. In your opinion, are they really useful?
In several cases, we may want to test the web services without running a browser, HttpUnit/ServletUnit (http://httpunit.sourceforge.net/) help us to achieve this task. HttpUnit (written in Java) emulates the relevant portions of browser behavior, including form submission, JavaScript, basic http authentication, cookies and automatic page redirection, and allows Java test code to examine returned pages either as text, an XML DOM, or containers of forms, tables, and links. When combined with a framework such as JUnit that we have discussed during week 3, it is fairly easy to write tests that very quickly verify the functioning of a web site.

HtmlUnit (http://htmlunit.sourceforge.net/) is another java unit testing framework for testing web based applications. It is similar in concept to HttpUnit but with very different implementation. While HttpUnit models the http protocol (so we can deal with request and response objects), HtmlUnit models the returned document (so we can deal with pages and forms and tables).

jWebUnit (http://jwebunit.sourceforge.net/) is a Java testing framework that combines the functionality of HttpUnit with JUnit and includes ready-to-use assertions. jWebUnit extends JUnit with WebTestCase.

Quilt (http://quilt.sourceforge.net/) can be used for measuring coverage in the testing of Java programs and it could be applied to the above Unit test tools.

Other client side automatic web testing tools include:
 Canoo (http://webtest.canoo.com/) that lets you to specify a sequence of test steps and run it (e.g., get login page, validate the login page, input login name/password, click the OK button, and verify the returned page)
 MaxQ (http://maxq.tigris.org/) that records your using of a web site and turns the links you click on and any other input into a Python script that you can play back at any time
 JSpider (http://j-spider.sourceforge.net/) that can check web site errors, links, and analyze site structure
 JMeter (http://jakarta.apache.org/jmeter/) that can be used for performance test both on static and dynamic resources (files, Servlets, Perl scripts, Java Objects, Data Bases and Queries, FTP Servers and more)

Though the above mentioned tools are mainly for client side Web service Unit testing, Cactus (originally called J2EEUnit, http://jakarta.apache.org/cactus/) is a simple test framework for server-side unit testing tool (e.g., to test Servlets, EJBs, Tag Libs, Filters, etc.).

Thanks & Best Regards,

View Full Posting Details