I've used SeIDE for almost two years and am now migrating tests to C#.
NUnit, C# and VS are new for me. I used to convert IDE to PERL and run
through SeServer but the Se folks have discontinued support for PERL.
SeIDE offers both assert and verify to check on screen elements. An
assert error will gen a message and stop the test. A verify error will
gen a message and continue in most cases. For example, if an element
is expectantly not found, verify will also halt the test. That is a
distinction that the Se folks coded into the IDE. (There may be good
reason for that but since there is no control logic in the IDE, a
better solution might have been to provide an optional/additional
command not to halt the test.)
The IDE can convert its html into C# to run via the SeServer and
NUnit. Unfortunately there isn't a one to one mapping of SeIDE
commands to C# & Se libs but it still does this modestly well. And
there is enough documentation and generous users available to share
their knowledge so that even a newbie like me can get it to work.
(Thanx :-)
The misfit between Se and NU is that NU isn't designed to handle long
tests with many Se asserts and verify's. NU will stop and fail the
test on the first assert that it sees and then move on to the next
test. Because of the way Se verify is converted in C#, NU will blindly
pass failing verify’s leaving the user to peruse the log for errors.
After converting the first 100 SeIDE tests, I've realized that NU's
Pass/Fail display can't be relied on to accurately reflect the SeIDE
flow. If I have to read the log after each run, then there isn't much
gain in using NUnit for this environment.
Note that I'm not maligning NUnit. It's just not a good fit with Se
tests.
Thinking out loud, Sparky
Maybe one thing you could consider is using verifies, but persisting
any that failed until the end of the test where you could then fail
the test which would result in a more reliable indication from nunit.
Just a thought.
David
Python would be a much better choice of a new environment, and the Python support in the Selenium Project is first-class.
Ross
Also, I would recommend Gallio/MbUnit has a far superior alternative
to nUnit. It offers many more features, such as the ability to record
and embed screenshots/video, advanced data driven testing features,
and the ability to mark a test as inconclusive.
You will save much time if you develop yourself a basic framework to
help resolve some of these issues. let me know if you need support or
help developing one.
Brian
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/FMtzS6rVW5wJ.