First, you can check table content (currently only text content) with assertTableEquals or assertTableMatch.
I can also easily add a new method to WebTestCase to get a Table object:
public Table getTable(String nameSummaryOrId)
Table object is defined by jWebUnit and should stay independent of the plugin. It currently store text, colspan and rowspan of each cell.
If you want to check if a link is present in a given cell of a given table, you can use XPath:
assertElementPresent(//[EMAIL PROTECTED]'***']//tr[n]//td[m]//[EMAIL PROTECTED]'XXX'])
We could also add a specific method, but I don't know exactly which. Perhaps a way to navigate in cells like in frames or forms:
void setCurrentCell(String tableName, int row, int col);
And after that, you could use assertLinkPresent()...
But I don't know if it is possible to realize.
I can also easily add a new method to WebTestCase to get a Table object:
public Table getTable(String nameSummaryOrId)
Table object is defined by jWebUnit and should stay independent of the plugin. It currently store text, colspan and rowspan of each cell.
If you want to check if a link is present in a given cell of a given table, you can use XPath:
assertElementPresent(//[EMAIL PROTECTED]'***']//tr[n]//td[m]//[EMAIL PROTECTED]'XXX'])
We could also add a specific method, but I don't know exactly which. Perhaps a way to navigate in cells like in frames or forms:
void setCurrentCell(String tableName, int row, int col);
And after that, you could use assertLinkPresent()...
But I don't know if it is possible to realize.
----- Message d'origine ----
De : Tetyana Gimgina <[EMAIL PROTECTED]>
À : Julien HENRY <[EMAIL PROTECTED]>
Envoyé le : Vendredi, 7 Juillet 2006, 1h44mn 01s
Objet : Re: Re : [Jwebunit-users] Re : no backward compatibility for tests developed with jwebunit 1.2 in 1.3-RC1
Hi Julien,
it's not that we are preferring HttpUnit over HtmlUnit. We simply have legacy code and tests that already in place and we don't really have time or resources to refactor them.
Because WebTestCase getDialog() used to return HttpUnitDialog there is a relience on the objects that can be obtained from the dialog such as WebClient and WebTable. There are number of tests on valid table structure, for example, that certain table cells contain certain links and the links text value may depend on value of other cells. Actually, I would really appreciate if you provide an example or point to documentation that shows how to do this with jWebUnit+HtmlUnit.
Hope, I answered your question.
Regards, tegi.
De : Tetyana Gimgina <[EMAIL PROTECTED]>
À : Julien HENRY <[EMAIL PROTECTED]>
Envoyé le : Vendredi, 7 Juillet 2006, 1h44mn 01s
Objet : Re: Re : [Jwebunit-users] Re : no backward compatibility for tests developed with jwebunit 1.2 in 1.3-RC1
Hi Julien,
it's not that we are preferring HttpUnit over HtmlUnit. We simply have legacy code and tests that already in place and we don't really have time or resources to refactor them.
Because WebTestCase getDialog() used to return HttpUnitDialog there is a relience on the objects that can be obtained from the dialog such as WebClient and WebTable. There are number of tests on valid table structure, for example, that certain table cells contain certain links and the links text value may depend on value of other cells. Actually, I would really appreciate if you provide an example or point to documentation that shows how to do this with jWebUnit+HtmlUnit.
Hope, I answered your question.
Regards, tegi.
On 7/6/06, Julien HENRY <
[EMAIL PROTECTED]> wrote:
In fact, as a response of this message, the dev team encourage me to drop HttpUnit, and I didn't wait until after 1.3 to drop it. HttpUnit had many unresolved bugs, with a bad _javascript_ support, and if we are waiting for improvement before releasing... we could wait for long time. HtmlUnit is much better.
Could you explain what usefull feature you found in jWebUnit+HttpUnit you don't found in jWebUnit+HtmlUnit ?----- Message d'origine ----
De : Tetyana Gimgina <[EMAIL PROTECTED]>À : Julien HENRY <[EMAIL PROTECTED]>; Usage problems for jWebUnit < [email protected]>
Envoyé le : Jeudi, 6 Juillet 2006, 1h33mn 02s
Objet : Re: [Jwebunit-users] Re : no backward compatibility for tests developed with jwebunit 1.2 in 1.3-RC1
Hi Julien,
thanks for answer.
I've raised the bug, but there is another issue for us: droppage of the httpunit plugin.
In you messageRe: JWebUnit 1.3 and the future of JWebUnit
2006-06-23 05:42, you wrote following:
I think it's time for a new 1.x release (1.3) before doing new (r) > evolutions. I tried to fix most of the bugs, and I cleaned > sourceforge bug tracking. Many bugs are due to httpunit, and I > don't think they will be fixed in a near future. That's why we > could release 1.3 with httpunit and htmlunit plugin to prepare the > real migration: jwebunit 2.x, with htmlunit and selenium plugins > (the two more promissing frameworks I know).>> I will create a new branch in SVN called 1.x I will first clean > everything to prepare the release (remove selenium and jacobie that > are not usable, use release instead of snapshots in > dependencies, ...). Once all will be ready, we will provide this > release and deploy the site with associated javadoc and doc.>> After that, main improvements will be done in trunk, and I plan to > drop httpunit and jacobie plugins as it is too hard to support 4 > plugins.
Bit it seems that you purged httpunit plugin in the 1.3-RC1 already (or at least the plug-in is not present in current distribution).
Is there any plans to have it in 1.3-RC2?
Regards, tegi.On 7/6/06, Julien HENRY < [EMAIL PROTECTED]> wrote:Hi,
Yes, it's possible. If you had time, could you please open a bug. This way, I will not forget it.
++
Julien----- Message d'origine ----
De : Tetyana Gimgina <[EMAIL PROTECTED]>
À : [email protected]
Envoyé le : Mercredi, 5 Juillet 2006, 12h11mn 02s
Objet : [Jwebunit-users] no backward compatibility for tests developed with jwebunit 1.2 in 1.3-RC1
Hi,
In our project there is number of tests developed with jwebunit 1.2.
We were very excited about 1.3 release, in particular about ability to select radio options, but found that it's not possible to move to new release without refactoring as we use setFormElement() method that now absent from WebTestCase.
Is there any chance to introduce the setFormElement() back as a depricated method that wraps it's replacement in next release candidate?
Regards, tegiUsing Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
Jwebunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-users
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jwebunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-users
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Jwebunit-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jwebunit-users
