Hi,
I started testing the latest release. I could validate that the
bugs/feature requests I reported in 1.3 are perfectly fixed. Great.
On the other hand I sometimes had to change my test case to fit the new
release. This is problematic as the number of test cases becomes
important.
I realized one big difference is that 1.4 introduce more strongly typed
methods. This is indeed important to be able to validate the type of
widget (radio, checkboxes, list boxes, etc) simultaneously with the value
it contains.
I find it a bad idea to deprecate the lazily typed methods. When writing a
test you may well want to check that a form element contains a given value
regardless of the nture of the widget. It should be possible to write a
test so that refactoring the application turning a text field into a
select or a radio button group without changing the functionality does not
break the test.
I think both the lazily typed and the strongly typed test methods are
interesting. Using one or the other depends on the requirements of your
test case. In my opinion, the test framework should allow both approaches
Thanks for all.
Bernard
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jwebunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-users
