WDK ATF 2.5 errors

Hello,

We are getting this error when running some of the ATF 2.5 tests we have designed for a Webtop 6.5 customization.

Has anyone seen this before? Any help would be much appreciated.

error
--------------------------------------------------------------------------------
case:[case: testcase002]
--------------------------------------------------------------------------------
cause: Not able to generate row selection event since cannot find matching checkbox / actionmultiselectcheckbox / datagridrowevent control from component= id: objectlist, class: com.ecs.webtop.library.objectlist.ObjectList
reason:
path: /adhoc testsuite:ticket=29/testcase:id=testcase002
time (START): 16-Dec-2008 04:19:32 - time (END): 16-Dec-2008 04:19:44
time (ELAPSED): 0:0:12.437

Stack Trace
com.documentum.web.test.controlevent.dmf.databound.DatagridRowMouseDownEvent.<init>(DatagridRowMouseDownEvent.java:88)
packagename002.testcaseclass002$Step9.controlEvent_1_generate(testcaseclass002.java:502)
packagename002.testcaseclass002$Step9.getClientEvents(testcaseclass002.java:487)
com.documentum.web.test.ComponentTestCaseMediator.getClientEventsFromStep(ComponentTestCaseMediator.java:138)
com.documentum.web.test.TestCaseMediator.doGetClientEventsFromStep(TestCaseMediator.java:289)
com.documentum.web.test.TestCaseMediator.doGetClientEvents(TestCaseMediator.java:227)
com.documentum.web.test.TestCaseProcessor$GetClientEventJavaScriptAction.execute(TestCaseProcessor.java:710)
com.documentum.web.test.TestCaseActionInvoker.invoke(TestCaseActionInvoker.java:51)
com.documentum.web.test.TestCaseProcessor.getClientEventJavaScript(TestCaseProcessor.java:91)
com.documentum.web.form.FormTag.renderTestCasePlaybackInitJS(FormTag.java:828)
com.documentum.web.form.FormTag.doEndTag(FormTag.java:401)
org.apache.jsp.ecs.library.objectlist.objectlist_jsp._jspService(objectlist_jsp.java:824)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
com.documentum.web.form.FormProcessor.dispatchURL(FormProcessor.java:2186)
com.documentum.web.formext.component.URLDispatchBridge.dispatch(URLDispatchBridge.java:107)
com.documentum.web.formext.component.ComponentDispatcher.mapRequestToComponent(ComponentDispatcher.java:463)
com.documentum.web.formext.component.ComponentDispatcher.doPost(ComponentDispatcher.java:339)
javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
com.documentum.web.formext.component.ComponentDispatcher.doService(ComponentDispatcher.java:300)
com.documentum.web.formext.component.ComponentDispatcher.serviceAsNonController(ComponentDispatcher.java:138)
com.documentum.web.formext.component.ComponentDispatcher.service(ComponentDispatcher.java:119)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
com.documentum.web.form.FormProcessor.dispatchURL(FormProcessor.java:2186)
com.documentum.web.form.FormProcessor.doFreshInclude(FormProcessor.java:1079)
com.documentum.web.form.FormProcessor.doFreshInclude(FormProcessor.java:1055)
com.documentum.web.form.FormProcessor.redirect(FormProcessor.java:1007)
com.documentum.web.form.FormProcessor.openForm(FormProcessor.java:254)
com.documentum.web.form.WebformTag.doStartTag(WebformTag.java:127)
org.apache.jsp.ecs.library.objectlist.objectlist_jsp._jspx_meth_dmf_005fwebform_005f0(objectlist_jsp.java:852)
org.apache.jsp.ecs.library.objectlist.objectlist_jsp._jspService(objectlist_jsp.java:72)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
com.documentum.web.servlet.ResponseHeaderControlFilter.doFilter(ResponseHeaderControlFilter.java:303)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
com.documentum.web.servlet.CompressionFilter.doFilter(CompressionFilter.java:84)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
com.documentum.web.env.WDKController.processRequest(WDKController.java:95)
com.documentum.web.env.WDKController.doFilter(WDKController.java:83)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
java.lang.Thread.run(Thread.java:595)

Find more posts tagged with

Comments

ljwong

Hi Saul,

That type of error occurs when the system can't figure out or can't find the exact control it needs to select. Here's a table of possible reasons I can think of off the top of my head.

Cause	Explanation / How to fix
Item/control isn't on screen due to paging	1) Ensure test objects are always on screen by putting them in their own folders 2) Write code to test if the item is on the page and if not, insert code to go to the next page 3) Ensure test recording scenario is exactly the same as playback scenario (i.e., start with same repository status)
Multiple controls with the same name on the same page	Make sure controls have unique names if they serve different purposes
Object has dynamic name	If an object has a dynamic name, add some code into test case which allows it to calculate or get the dynamic name of the object so that the correct object can be selected. This may involve setting the values of variables within the test case and/or changing some of the XML.
Key attribute needed to identify item in grid not included in recording	ATF comes with a default configuration which supports the key attributes used in the grids of the Webtop product. These values are used to distinguish items within a grid from other items in a grid. If your customization includes other attributes, you may need to customize the values in the <validargumentnames> configuration element of the test framework so that the right item can be found.

Hope this helps.

Linda

mingus

Hello Linda,

Thanks very much for your quick answer. I did some additional testing and discovered that we are running into this error every time we record a test navigating through the cabinets/folders using the navigation tree. If we record the test going down the folders double-clicking on them on the main screen there's no problem.

Has this behavior been reported before? could it be just some iexplorer settings ?

We are creating tests now without error, but we have an issue when we need to go back up the folder hierachy, going to the tree panel seems to kill the test when you run it.

I will post some other things we are finding out.

Thanks a lot again.

Best regards,

Saul

ljwong

Hi Saul,

I'm not aware of errors with ATF and navigation via the tree hierarchy. Matthew would have a better idea about current product bugs or issues, but I think he may be on vacation. As a workaround for the cases where you need to navigate back up the hiearchy in your tests, is it possible to use the breadcrumbs?

Linda

mingus

Hello Linda,

I made further testing but didn't manage to get a clear conclusion on why the playback is failing with that error.

I created a simple test scenario, opening folders and checking some properties of a document, and going up and down the folder tree. Then run the test, and some times it crashes, some times it does not, and sometimes it crashes in different steps. I am the only user in the system, and I am not aware of any changes on the environment from an execution to the other that could be causing this.

If I find out what's going on I'll let you know.

Thanks and best regards,

Saul

hasang

Dear All,

We also experience the same error regarding the browser tree navigation. We also notice that if we click on link control (like in user management) rather than the double click sometimes is also thrown error. I've noticed that ATF is used for internal testing of webtop before it is released to the market, so it's mean that the tools should be compatible and could be used to test at least basic webtop function. Please kindly advise.

Our test environment ATF 2.5 with webtop and CS 6.5 SP2

Thanks in advance,

Juan Hasang

ljwong

Hi Juan,

Do you have a customized application or are you using Webtop out of the box? If you're using it out of the box, can you include a set of steps with which you've seen the issue? If you have the problem causing test case java class and configuration, please attach that as well.

Linda

hasang

Hi Linda,

Thanks for the response. We are just using the standard Webtop and CS 6.5 SP2 without any customization. The test case are quite simple:

1. Login to webtop as superuser

2. Click on the cabinet tree

3. Click on the User Management Node

4. Click on the Users node

5. Click Show All User button.

The test could be reply back succesfully for the first time but it will failed if we played back again.The test also failed if we use the Users link on step 4 above instead of clicking the tree node

Please let me if you need the actual config or source files/

Thanks & Regards,

Juan Hasang

wongm2

Hi,

Did you record the login going through the login dialog or through the recorder's autologin functionality?

If you did the former, then the test case will expect the login dialog, so if you replay the case in the same browser session after having played it once the test case will expect the login screen while the session is already there and as such the login screen will not come up, and the case will hang.

In which case you may want to use the recorder's autologin functionality.

If you actually did use the latter, let me know.

Thanks

Matthew

hasang

Hi All,

I think this my third try using the same failed scenario. So here's some fact that I want to share :

1. Login -> is not using the login dialog instead I'm using the auto login

2. Click on the User Management node -> reply the test, it is still ok

3. Click on the Users node -> reply the test, it is still ok

4. Click on the Show All User button -> reply the test, it is still ok

5. Right Click on Administrator user -> it is not working

Please also note that I'm recording and replying the test with auto login features.

Attach also the test result that contain error description.

Thanks & Regards,

Juan Hasang

abothe

Hi Juan,

There should be no problem in executing the steps mentioned by you. We use these steps frequently in our test suites.

Can you provide me the exact environment setup of your webtop.

Also can you do a fresh recording and send across the generated java and xml file.

Thanks,

Amit