in reply to Building a test environment

You could make your newly created users log in. It's just another Mech request, right? As for the file, you can set their age with the touch command or override the way your code finds out what day it is.

Replies are listed 'Best First'.
Re^2: Building a test environment
by talexb (Chancellor) on Jun 05, 2007 at 14:51 UTC

    Yes, sorry, the PM server was so slow this morning I didn't do my usual compose, compose, compose, compose, compose, compose, post cycle. Here's more detail.

    The user names are E-Mail addresses, and a new user is E-Mailed their temporary, one-time password. They have to use that to log in, and the only thing they can do is set their password to a new value. My SysAdmin has set up a couple of E-Mail addresses that just re-direct to me, so right now I think my plan is to run the first part of the test, then perhaps have the test pause, while I use cut and paste to change the test users' passwords to known values, then continue the test.

    It's a little clumsy, which is why I was asking for guidance.

    Alex / talexb / Toronto

    "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

      The way we handle e-mail on my current project is to run SMTP-Server and have the mail we want to test sent to localhost. It shows up as a file which you can then open and extract what you need. It's a little cumbersome, but doesn't rely on any outside network configuration.