This turned out to be the Ant version. Lori had specified ant 1.7 in her .profile, but something changed on her box so that it wasn't reading and loading up the .profile variables anymore. Another mystery solved! -- Lisa
On Wed, Feb 29, 2012 at 11:47 AM, Lisa Crispin <[email protected]>wrote: > I'm forwarding this on behalf of my teammate. She and another teammate are > having this issue. I don't have this problem, and neither does yet another > teammate. We can't figure out what the difference is between the > environments where the tests run fine and the ones that have this issue > with dynamic properties not being populated. Anyone have any ideas? We are > on version 1762 - we want to update to the latest version (we tried last > fall), but there are a lot of backward compatibility issues and we need a > lot of time to update our scripts. > thanks > Lisa > > ---------- Forwarded message ---------- > From: Lori Thayer <[email protected]> > Date: Tue, Feb 28, 2012 at 12:22 PM > Subject: FW: Dynamic Property issue > To: Lisa Crispin <[email protected]> > > > > > From: Lori Thayer <[email protected]> > Date: Tue, 28 Feb 2012 08:50:07 -0700 > To: "[email protected]" <[email protected]> > Subject: Dynamic Property issue > > Greetings, > > Due to some IntelliJ issues I had to blow away my code locally and recheck > out all of our code/tests this morning. Since then the dynamic properties > won't resolve. > > Below is an example from one test that fails for me locally although it > passes in our build environment and for my coworkers. > > I've tried to track down a difference but haven't been successful so far. > If someone has any ideas I would love to hear them. > > Storing the values > * 6* [image: ok] *storeDynamicProperty* > nameusername valuetucker=> valuetucker > 1 * 7*[image: ok] *storeDynamicProperty* > namepassword valuetest1234 => valuetest1234 > > Setting the input fields > * 34* [image: ok] *setinputfield* > Enter userid > nameusername valuetucker > 9* 35* [image: ok] *setinputfield* > Enter password > namepassword valuetest1234 > > > Results page shows the property didn't resolve before it was set, even > though it looks like it was in the setinputfield above. > > Username: invalid username/password combination!Username: Password: > > > > -- > Lisa Crispin > Co-author with Janet Gregory, _Agile Testing: A Practical Guide for > Testers and Agile Teams_ (Addison-Wesley 2009) > Contributor to _Beautiful Testing_ (O'Reilly 2009) > http://lisacrispin.com > @lisacrispin on Twitter > http://entaggle.com/lisacrispin > > -- Lisa Crispin Co-author with Janet Gregory, _Agile Testing: A Practical Guide for Testers and Agile Teams_ (Addison-Wesley 2009) Contributor to _Beautiful Testing_ (O'Reilly 2009) http://lisacrispin.com @lisacrispin on Twitter http://entaggle.com/lisacrispin
