Topic: WEBSITE TEST AUTOMATION REQUIREMENTS

Message

   Assuring WebSite quality requires conducting sets of
tests, automatically and repeatably, that demonstrate required
properties and behaviors. Here are some required elements of tools that
aim to do this.

Test Sessions. Typical elements of tests involve these characteristics:

    * Browser Independent. Tests should be realistic,
but not be dependent on a particular browser, whose biases and
characteristics might mask a WebSite's problems.

    * No Buffering, Caching. Local caching and buffering
-- often a way to improve apparent performance -- should be disabled so
that timed experiments are a true measure of the
Browser-Web-WebSite-Web-Browser response time.

    * Fonts and Preferences. Most browsers support a
wide range of fonts and presentation preferences, and these should not
affect how quality on a WebSite is assessed or assured.

    * Object Mode. Edit fields, push buttons, radio
buttons, check boxes, etc. All should be treatable in object mode, i.e.
independent of the fonts and preferences.

      Object mode operation is essential to
protect an investment in test suites and to assure that test suites
continue operating when WebSite pages experience change. In other
words, when buttons and form entries change location on the screen --
as they often do -- the tests should still work.

      However, when a button or other object
is deleted, that error should be sensed! Adding objects to a page
clearly implies re-making the test.

    * Tables and Forms. Even when the layout of a table
or form varies in the browser's view, tests of it should continue
independent of these factors.

    * Frames. Windows with multiple frames ought to be
processed simply, i.e. as if they were multiple single-page
frames. 

Author	Message
Neepa123 Newbie Joined: 01May2007 Online Status: Offline Posts: 1	Topic: WEBSITE TEST AUTOMATION REQUIREMENTS Posted: 01May2007 at 11:38pm
	Assuring WebSite quality requires conducting sets of tests, automatically and repeatably, that demonstrate required properties and behaviors. Here are some required elements of tools that aim to do this. Test Sessions. Typical elements of tests involve these characteristics: * Browser Independent. Tests should be realistic, but not be dependent on a particular browser, whose biases and characteristics might mask a WebSite's problems. * No Buffering, Caching. Local caching and buffering -- often a way to improve apparent performance -- should be disabled so that timed experiments are a true measure of the Browser-Web-WebSite-Web-Browser response time. * Fonts and Preferences. Most browsers support a wide range of fonts and presentation preferences, and these should not affect how quality on a WebSite is assessed or assured. * Object Mode. Edit fields, push buttons, radio buttons, check boxes, etc. All should be treatable in object mode, i.e. independent of the fonts and preferences. Object mode operation is essential to protect an investment in test suites and to assure that test suites continue operating when WebSite pages experience change. In other words, when buttons and form entries change location on the screen -- as they often do -- the tests should still work. However, when a button or other object is deleted, that error should be sensed! Adding objects to a page clearly implies re-making the test. * Tables and Forms. Even when the layout of a table or form varies in the browser's view, tests of it should continue independent of these factors. * Frames. Windows with multiple frames ought to be processed simply, i.e. as if they were multiple single-page frames. Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Web Testing @ OneStopTesting