Test Suite for Cross Browser DHTML API

If a test succeeds, it will print true.

If it fails, it will print false.

To quickly search for a failure, open the test document and use Edit-->Find to search for "false."

If you change the functions in the xbdhtml.js script, run this test suite to make sure you haven't broken any of the functionality. In this way, test suites make it easier to reuse and extend existing software modules. Script developers can easily and quickly retest all of a script's functions after making changes. Quality Assurance automation speeds development and raises software quality.

Write a test suite at the same time that you develop a module. Each time you write a function, write a set of tests that ensure the function is working. Make sure the set of tests covers all the inputs the function is expected to handle. Pay particular attention to boundary values.

Writing a test suite takes more time at first, but it pays off later in development when you modify core functions and must retest them to make sure they haven't been broken. There is never time to retest functions manually. Test suites make it easy to test code on multiple platforms or application versions. Test suites also reduce stress for the developer by giving him or her confidence that the software has been thoroughly tested.

HTML Positioning testpos.html
Getting Nested Elements testnest.html
Get/Set Clip Area testclip.html
Hide/Show testhide.html
Z-Index Ordering testz.html
Background Color backgnd.html
Background Image backimg.html
Markup Generation testmark.html