The easiest techniques I have seen are:
- searching for key strings which can be numbers, names, etc
- post-test validation, ie other tests in a series that run after or
between UI level tests to check data in the database and such
-David
On Aug 26, 2006, at 2:09 PM, Al Byers wrote:
I just got Grinder up and working today and am very impressed. It
took 2-3 hours to get comfortable with it enough to get the
TCPProxy to work. I still have jython/python to learn, but you
don't need much to get it going. It is the TCPProxy filter that
allows you to capture your browser activity and then play it back
as a test. That is worth the price of admission right there.
What I don't see yet, is the best way to test the HTML that comes
back from a front-end test to see if it passes. Is it to compare it
to "standard"? That doesn't seem practical because a small
difference would make the test fail. I see that there is python
interface to Tidy, so i wonder if the answer isn't to run the
response thru Tidy and then use Freemarker to process the response
to see if the test criteria is met. Doing that from scratch for
each test would be prohibitive, so I am wondering if there is some
sort of shortcut that, perhaps, ofbiz can help with. I haven't
thought it thru, but maybe there are some sort of markers that can
be placed there, that could easily be found using the xpath
capabilities of freemarker. Maybe those markers can be triggered
from the widget definitions. Just thinking out loud there.
-Al
David E Jones wrote:
Try something like Grinder (on SourceForge). This is one candidate
for the in-progress OFBiz suite of testing tools.
-David
On Aug 25, 2006, at 10:37 PM, Sayoke Shome wrote:
Hi,
Is there any method in ofbiz which may help automating the front
end testing
process?
I need to test Ftls. Is there something similar to struts test
cases for
FTL's we use in ofbiz.
Thanks and regards,
Sayoke Shome | Technical Associate | Techmahindra Ltd. |
Bangalore | phone -
09886412359 |
====================================================================
========================================================
Tech Mahindra, formerly Mahindra-British Telecom.
Disclaimer:
This message and the information contained herein is proprietary
and confidential and subject to the Tech Mahindra policy
statement, you may review at <a href="http://www.techmahindra.com/
Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a>
externally and <a href="http://tim.techmahindra.com/
Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a>
internally within Tech Mahindra.
====================================================================
========================================================
