I usually keep them in a separate XML file, and read at run time. So
these can be changed easily without needing any change in the library.
I do not prefer to use spreadsheet for keeping variables, courtesy
being heavy and no straight mechanism to read from.
On Mar 2, 4:43 pm, xguarder
This is not a watir question, it's a programming question.
I would either pass them in as commandline parameters or store them in a
separate spreadsheet. I would use them at the top level and pass them into
the login function (I always have a login function) that handles that part,
or pass
I think the problem is the conflict between the latest rspec and spec
used in taza framework.
The latest version of rspec is require 'rspec' instead of require
'spec'.
I tried editing it in /Library/Ruby/Gems/1.8/gems/taza-0.8.7/lib/taza/
tasks.rb file --but permission denied.
May be Charley
That's exactly right, I'll take a look at it. It's not quite that
simple but if you're running rspec2 then you'll run into problems. Let
me see what I can dig up.
Cheers,
Charley Baker
Lead Developer, Watir, http://watir.com
On Wed, Dec 15, 2010 at 3:13 PM, Kay karthigaya...@gmail.com wrote:
I couldn't run the sample rake command. Any help to get it going?
$ pwd
/Users/elizabethleong/taza/google
$ rake spec:isolation:google
(in /Users/elizabethleong/taza/google)
rake aborted!
no such file to load -- spec/rake/spectask
/Users/elizabethleong/taza/google/rakefile:3:in `top
Or you can plugin cucumber :-)
On Dec 10, 12:19 am, George george.sand...@gmail.com wrote:
I think the biggest issue for me is that I'm still very new to RSpec.
If I spend a little more time learning this, I should have a better
sense of how your framework...erm, works.
BTW, I tried to use
Or you can plugin cucumber :-)
On Dec 10, 12:19 am, George george.sand...@gmail.com wrote:
I think the biggest issue for me is that I'm still very new to RSpec.
If I spend a little more time learning this, I should have a better
sense of how your framework...erm, works.
BTW, I tried to use
Or you can plugin cucumber :-)
On Dec 10, 12:19 am, George george.sand...@gmail.com wrote:
I think the biggest issue for me is that I'm still very new to RSpec.
If I spend a little more time learning this, I should have a better
sense of how your framework...erm, works.
BTW, I tried to use
Or you can plugin cucumber :-)
On Dec 10, 12:19 am, George george.sand...@gmail.com wrote:
I think the biggest issue for me is that I'm still very new to RSpec.
If I spend a little more time learning this, I should have a better
sense of how your framework...erm, works.
BTW, I tried to use
Happy to do that if you can suggest what you're interested in. All the
basic elements are described along with examples. Let me know what
would help and I'll see what I can do.
Cheers,
Charley
On Wed, Dec 8, 2010 at 5:26 PM, George george.sand...@gmail.com wrote:
+1
It would be helpful to
I think the biggest issue for me is that I'm still very new to RSpec.
If I spend a little more time learning this, I should have a better
sense of how your framework...erm, works.
BTW, I tried to use your Google example and was fine except for the
deprecation warning for activesupport. I'm still
Hi Charley,
I would like to know more about Taza framework. I installed the gem
and had a little play around with it. Watched the 8 min screencast as
well, but couldn't find more of it on advanced features and cross-site
testing?
Thanks,
Yush
On Dec 8, 8:14 pm, Charley Baker
+1
It would be helpful to have a little more documentation on how to
implement this framework...
On Dec 8, 2:56 pm, Yush bismitha...@gmail.com wrote:
Hi Charley,
I would like to know more about Taza framework. I installed the gem
and had a little play around with it. Watched the 8 min
13 matches
Mail list logo
