> Now that I've appended a number to the test names to indicate the correct
> order, they work just fine.
Maintaining the numbers to keep correct order can become a pain as
your test suite grows. You can also make the tests run in the order
you defined them by subclassing Watir::TestCase instead
Paul,
Thank you, thank you, thank you
I had moved on, assuming there was something weird about the way the login was
working.
This morning, I added a new test case that wasn't in alphabetical order and
I've been beating my head against my desk trying to figure out why debug
statements fro
If the code below is an actual snippet from your code then could the *order*
the tests be the problem?
Please remember that the _default_ order of execution is ascending alpha, so
the script would likely try to run the tests in the following order
regardless of how they are arranged in the script
Thanks for the suggestion!
I tried it and I'm pointing to the correct link, so I still don't know what my
problem with this is. Looking up objects using IRB did help me with a
different issue I was working through, however!
___
Wtr-general mailing lis
Have you tried the login and subsequent click in irb? If that does not work
(and it shouldn't yet, for consistency), you might want to try a
show_all_objects and a show_frames to make sure you're looking in the right
spot, and have the right target name.
Chong
__
Thanks for the suggestion, but I don't think that's my problem.
I've continued adding tests to the framework and I have the assert method in my
other tests as well.
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/list
Suppose your login method didn't work properly because it was referencing to
assert method,
which is located in the class Test::Unit::TestCase class.
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-genera
I noticed the line:
$ie.text_field(:name, "Find Account").click
Is in both the end of the login method and the beginning of the
clickLinks method. Maybe that is throwing off the state that
clickLinks expects?
Also, maybe check to see if test_clickLinks is running before
test_login. If I recall
After some tinkering, I think I've figured out my problem. It seems the
Test::Unit::TestCase functionality is expecting to open files and run them as
test cases rather than calls to methods in other files.
I was hoping to get all the data I need from a spreadsheet once, with the
harness code,
*Sorry - here is my harness code (I've simplified it by removing the XLS
interface code and addAccounts test so that it might be easier to drill down on
the problem. I have run this code to make sure the problem still happens.):*
require "win32ole"
require "watir"
require "test/unit"
requir
Tiffany Fodor wrote:
> Am I missing something? Any help would be appreciated!
>
You'll have to share more of your code with us for us to help.
Bret
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-gener
Hi!
I'm creating a test harness that will first collect all of the data necessary
to run the test cases then then execute the test cases.
Here's the code that is calling the test cases:
class TestScript < Test::Unit::TestCase
def test_login
login($producerName, $produc
12 matches
Mail list logo
