here is the multi-session worklog:
- add 2 new attributes, host and port.
- on init parse the 'server' argument extracting host and port
- add accessors for host and port.
- these changes will make it easier to port the older scripts which hardcode a localhost value.
- replace hardcoded constants with framework server instance's accessors
- get adminuser auth from Slingusers::User.admin_user hmm may want to do this across the board in a later sweep
- Time.parse() introduced
Wasn't able to run consistently against the Indiana QA server. Runs fine against localhost. 3akai is having proxy errors just now.
I am finding is that kern-577 cannot consistently create a user at Indiana, and when it does it cannot consistently create a link to the user's test-uploaded document. ( gets a 500! ) It does sometimes pass, but it sure is flakey. ( return a day or two later) OK now. To be expected in a fluid environment.
- use Sling.url_for()
- use Sling.url_for()
- Sling.url_for() in WidgetServices methods
(later) fixed this and 854 by changing the xWidgetServicesConfiguration foo methods to use the Sling classes url_for() method. The code was putting in double slashes, which were failing.
- Sling.url_for() in WidgetServices method
That's it for the kern's. now for the tests. The first on my list
is a false positive.
had a few hardcoded localhost URLs which I modified to use the Sling service's setup
This test had failed because I don't have mailtrap installed in my ruby repository of gem wonder. This test runs mailtrap on localhost, so changing it to something else doesn't make sense. Now to go see what mailtrap is. http://rubymatt.rubyforge.org/mailtrap/ yeppers. makes no sense for a remote host test. sweet.
Roll this stuff into my branch, then update my checkout against the current master to see what I've missed.
modify tools/runalltests.rb to contain a 'remote' blacklist. Not sure how it could tell now :) I'll take a big swing, add a "remote" flag, and have runalltests.rb do the sed stuff I posted about earlier.
use one definition for admin user. this is just clean up, but it'll make it easier for folks who change their default admin user down the road.
modify / remove timestamp based userID generation to use new User service method using random numbers. ( check speed )
extend the users module thing to centralize creation of temporary users. doing this will reduce ID collisions in multi-load/thread testing