SPONSORS:






User Tag List

Results 1 to 10 of 10
  1. #1
    Senior Member
    Join Date
    Nov 2001
    Location
    UK, Oxford
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    SP 3 and j2sdk1.4.1. True support?

    Background:
    AUT: a java applet
    The applet displays a tabbed pane. Each tabbed pane contains a list. You can open any item from the list, which creates an inspector window. The inspector windows themselves can spawn various dialogs.

    I have been testing this applet with no problems (well, none that I can't find a work around for), using Silktest5.5 SP1 and jdk1.3.1.

    Now the developers have switched to j2sdk1.4.1 and so I have re-installed Silktest to version 5.5.3.1[1047] which claims to support java 1.4

    Everything seemed OK, I was getting object recognition, and tests were running fine.
    Then some failed and I noticed that a whole bunch of windows of the same type(the inspector windows) were not being recognised. I checked out one of these windows using the 'Record Window Declarations' dialog and noticed that whereas before it had been of type JavaMainWin, now it was of type DialogBox.
    none of its content was being recognised.
    Silktest quite happily recognises the dialogs and their contents which spring from the 'inspector' windows. I checked their type: JavaDialogBox.

    Why is Silktest suddenly seeing these inspector windows as type DialogBox rather than JavaMainWin. The developers have changed nothing. I could sort of understand if it saw them as type JavaDialogBox, but even then why the change?

    This is not a setup issue (SilkTest_Java2.jar et al)
    So, any ideas, guys...?

    The inspector windows are of type JFrame in the java code. I know many optimizations have been made to Swing in 1.4, I was wondering if perhaps JFrame has been tied to a different underlying component...?
    ------------------


    [This message has been edited by johntest (edited 10-07-2002).]

    [This message has been edited by johntest (edited 10-07-2002).]
    Tempus fugit, Carpe Diem, et al

  2. #2
    Senior Member
    Join Date
    Nov 2001
    Location
    UK, Oxford
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: SP 3 and j2sdk1.4.1. True support?

    Ok, this is Segue's fault.

    After the usual rigmarole of navigating the lower eschelons of the Segue support network, I finally got to talk to a developer who was very helpful, or rather very informative.
    There is a problem with SP3 (5.5.3.1), how it copes with JavaMainWin.
    I was advised that I should open up partner.ini and in the class map section, to map our classes (the inspector classes) to JavaMainWin:
    com.decisionsoft.xmeta.client.structure.StructureI nspector=JavaMainWin
    I did this for each of the inspector classes and it worked.
    The recent hotfix for SP3 does not fix this problem so beware.
    It really is a horrible hack, and although eventually they were helpful, they should publicise these known issues (there was nothing in the release notes and I found nothing on the Segue site)
    An external bug-tracking system would be a start...?
    What a waste of time!

    Also, I was advised that version 6.0 was due at the end of this month.
    I asked for a specific date. None was forthcoming.
    I asked if the above issues would be fixed in the release.
    They would not guarantee it.

    Oh Segue, how we love you.
    ------------------


    [This message has been edited by johntest (edited 10-08-2002).]

    [This message has been edited by johntest (edited 10-08-2002).]
    Tempus fugit, Carpe Diem, et al

  3. #3
    Senior Member
    Join Date
    Nov 2001
    Location
    UK, Oxford
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: SP 3 and j2sdk1.4.1. True support?

    I spoke too soon.
    While all the above does help, if you dynamically change anything in the window, such as adding a tab to the tabbed pane, suddenly SilkTest loses the ability to recognise the contents of the window.
    It seems to do this randomly but generally the behaviour is as follows:
    I open an inspector, and using 'Record Window Identifiers' dialog, I can see everthing, I add a tab and the suddenly I cannot recognise any of the content any more.

    Will keep you posted just in case anyone else stumbles across this problem.

    ------------------
    Tempus fugit, Carpe Diem, et al

  4. #4
    Senior Member
    Join Date
    Nov 2001
    Location
    UK, Oxford
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: SP 3 and j2sdk1.4.1. True support?

    After a week or so of Segue support, I am in need of a holiday.(at the very least they could change the jingle)

    Finally, we discovered that the problem lies with using 5.5.3.1 and Jdk 1.4.1 on windows 2000.
    I had reduced the steps to reproduce the bug:
    click 'Edit' menu, hover over a menuitem without clicking and then move the mouse to the window title bar. This immediately caused a loss of recognition, or 'injection' as they call it.
    Their initial tests were on NT4 and they couldn't reproduce it.
    Later they tested on windows 2000 and hey presto.
    This has been logged as a defect.

    They suggested a work around:
    if I could tempoarily use NT4.

    Nice...:-)

    ------------------
    Tempus fugit, Carpe Diem, et al

  5. #5
    Senior Member
    Join Date
    Sep 2002
    Location
    ONDlodnol
    Posts
    111
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: SP 3 and j2sdk1.4.1. True support?

    Yeah, guys you can thank me for that. I made segue aware of the issue on 9/20 and the bug is logged per my discovery. My machine is WinNT4.0. I wasn't unware of the issue on win2000 thanks johntest for following up on that.

    ------------------
    Goodness is a part of life just like the Devil

  6. #6
    Senior Member
    Join Date
    Aug 1999
    Location
    MA
    Posts
    129
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: SP 3 and j2sdk1.4.1. True support?

    I just logged a new report with Segue about this issue:

    SilkTest did not recognize Java applets in IE6 when I used JRE 1.4.1_01 on Windows 2000 Server SP3. I applied SilkTest 5.5 SP3 Hotfix 1 but it did not solve the problem.

    In the same configuration with a version of the AUT that is IE6 / JRE 1.3.1_02 all is well.

    I'll update here when I get an updated status from Segue.

    ------------------
    Steven Tyler
    SQA Automation Team Manager
    Workforce Central Group
    Kronos Incorporated
    E-Mail: styler@kronos.com
    www.kronos.com
    Improving the Performance of People and Business™
    Steven Tyler
    Manager - Performance Engineering

    Kronos Incorporated
    tel: +1 978 947 4219

  7. #7
    Guest

    Re: SP 3 and j2sdk1.4.1. True support?

    Agggghhh! I had this EXACT same problem! My testcases ran wonderfully perfect using JDK 1.3.1_04 then our developers upgraded to JDK 1.4.0_01 and my tests no longer worked and my application appeared as a Dialog box rather than a JavaMainWin! Three hours later and numerous calls to TechSupport, I finally got this fixed but can confirm that this problem is not addressed on their website or in the release notes!

    If you too have this problem follow these steps (2 minutes compared to 3 hours):

    1. Download Spy ++ from this website: http://www.lynn3686.freeserve.co.uk/download.html
    2. Make sure this file: Msvcirt.dll is copied in your os folder which for Win2000 is WINNT/SYSTEM 32
    3. In Spy ++, click on Search/Find Window
    4. Drag and drop target icon onto your application to find out the EXACT name of your application
    5. Find and open your partner.ini file
    6. Paste: [Classmap]
    <your application name>=JavaMainWin
    7. Close your application and SilkTest

    Everything should work fine now.


    ------------------

  8. #8
    Senior Member
    Join Date
    Aug 1999
    Location
    MA
    Posts
    129
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: SP 3 and j2sdk1.4.1. True support?

    Unfortunately in my case I have an applet, and Internet Explorer 6.0 is seen correctly.

    QATester25, it's great you shared the Spy++ tip, that will save the Java app testers here lots of time.

    I did a WebEx session with Segue today and the engineer there saw the problem I have with JRE 1.4.1_01 and SilkTest. I learned a new Segue term called "injection", this is the term they use when Silk has hooked into the AUT. So my problem is "no injection" into the Java applet...

    I'll know the next steps from Segue in the coming week.

    ------------------
    Steven Tyler
    SQA Automation Team Manager
    Workforce Central Group
    Kronos Incorporated
    E-Mail: styler@kronos.com
    www.kronos.com
    Improving the Performance of People and Business™
    Steven Tyler
    Manager - Performance Engineering

    Kronos Incorporated
    tel: +1 978 947 4219

  9. #9
    Senior Member
    Join Date
    Aug 1999
    Location
    MA
    Posts
    129
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: SP 3 and j2sdk1.4.1. True support?

    Issue resolved by Segue support. Apparently you have to uninstall previous JRE versions, and run the 5.5 SP3 Hotfix 1 from the \Program Files\Segue\SilkTest directory. I did neither of these.

    Here's what worked for me:
    1) Uninstalled all JRE's from the system
    2) Copied the SilkTest 5.5 SP3 Hotfix 1(SilkTest55_SP3HF1.exe) to the \Program Files\Segue\SilkTest directory
    3) Ran the SilkTest 5.5 SP3 Hotfix 1 from the SilkTest directory
    4) Installed the plugin via Kronos application logon screen
    5) Copied the newer SilkTestJava2.jar file to the JRE 1.4.1 ext directory
    6) Ran SilkTest and the objects were recognized.

    ------------------
    Steven Tyler
    SQA Automation Team Manager
    Workforce Central Group
    Kronos Incorporated
    E-Mail: styler@kronos.com
    www.kronos.com
    Improving the Performance of People and Business™
    Steven Tyler
    Manager - Performance Engineering

    Kronos Incorporated
    tel: +1 978 947 4219

  10. #10
    Senior Member
    Join Date
    Nov 2001
    Location
    UK, Oxford
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: SP 3 and j2sdk1.4.1. True support?

    That's good news.
    However, I thought 5.5.3.1 contained hotfix 1. Hence the .1
    Where do we get this .exe from and I wonder if they have one for 6.0.

    Also I wonder if this fixes the loss of injection caused by playing around with menuitems which I described earlier in this thread...?

    ------------------
    Tempus fugit, Carpe Diem, et al

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 12:33 AM.

Copyright BetaSoft Inc.