• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Automated/load testing for WO apps
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Automated/load testing for WO apps


  • Subject: Re: Automated/load testing for WO apps
  • From: Mike Mitchell <email@hidden>
  • Date: Wed, 14 Jul 2004 08:28:53 -0500

They're predictable once you've seen them. :-) The problem is that the guys doing test automation have absolutely no clue what they're going to be when doing the scripting. Furthermore, our pages are quite dynamic with regard to content, so you don't know how many components there are, or necessarily what they point to, whereas if these were typical readable links you would know what they were from their names and could script some kind of navigation.

Another problem is, every time we do a new release, the component IDs change because the app's different. We cannot be doing that much re-writing of test scripts every time the code changes. I mean, you need to do SOME rewriting because you need to handle the new/changed functionality, but with WO, *every* link in the entire app changes to something that is, for all practical purposes, random and unpredictable.

/mike

-----------------------------------
Mike Mitchell
MissionMode Solutions, Inc.
office: 952.447.5780
mobile: 952.221.3497
email@hidden


On Jul 13, 2004, at 11:59 PM, Chuck Hill wrote:

They actually work in a very predicable way. The first number (6 and 26 below) is the number of request for that session, aka the contextID. If you click a link and then hit refresh over and over you will see this increment while the rest (0.1.1.6.2) remains constant. The rest of the numbers are the elementID they uniquely identify a particular element (WODynamicElement) in the page relative to what else is in the page. They tend to be fairly constant other than inside a WORepetition and a few other circumstances where data affects how many of them there are. If you test against the same data and follow the same path through the app they will not change.

Chuck


On Jul 13, 2004, at 9:42 PM, Mike Mitchell wrote:

That's all well and good, but my problem is NOT the session ID. It's the WO component IDs that follow it. Pretty much every link on the site is a WO component, and they're different every session. One day my home page is 6.0.1.1.6.2 and the next it's 26.0.1.1.6.3. So basically I cannot count on any link on the site being static, which makes it hard if not impossible to script navigation.

/mike


On Jul 13, 2004, at 2:57 PM, Michael Henderson wrote:

Hi,

 I downloaded grinder : http://grinder.sourceforge.net

and modified it to rewrite recorded URLS, replacing the recorded session id with the current session id
when replaying a recorded session. ( I modified my app to include a header with the session id in it so I can get the session id
from the first request).


Mike
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Automated/load testing for WO apps (From: Mike Mitchell <email@hidden>)
 >Re: Automated/load testing for WO apps (From: Michael Henderson <email@hidden>)
 >Re: Automated/load testing for WO apps (From: Mike Mitchell <email@hidden>)
 >Re: Automated/load testing for WO apps (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: mod_rewrite
  • Next by Date: Re: Using mod_rewrite
  • Previous by thread: Re: Automated/load testing for WO apps
  • Next by thread: Re: Automated/load testing for WO apps
  • Index(es):
    • Date
    • Thread