• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Testing on Linux and Solaris

 
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I built my application using JDK 1.4.02, using Windows XP and 98. I have just tested my application on Solaris 10, and Linux 7.2 Red Hat. I had some unexpected results.

The Solaris 10 box was running JDK 1.5. Everything came up ok, but at first there was a focus issue. Upon initial launching of my standalone or network client, I could not type in any of the text fields. I could select rows in my JTable, but could not give focus to a text field. Also I could not select rows in the JTable with the up and down arrow keys. So the application seemed unresponsive to the keyboard. Then I switched focus to another window altogether and then went back to my application window. At that point everthing seemed to work fine. I cannot imagine anything in my code that would have caused this. So that's problem number 1.

The Linux 7.2 box was running JDK 1.4.001, a previous version of the JDK than what I used to build my application. My application ran fine in standalone mode, and the server started ok as well. But when trying to run the network client, it seemed unable to make a network connection to the server. My network client startup dialog just froze up and hung, so I was hosed at that point. That's problem number 2.

Aside from those issues it seemed to work fine. My question is this: how thorough must we be in our testing on other operating systems? I imagine the examiner will try it out on Solaris (since we're talking about Sun here) and Windows. Are these issues I should be concerned about?

I think that problem number 2 (Linux problem) could be due to running my application with a previous version of the JDK than what I built the application with. In that case, I would think that you should only test your application with the same JDK that you used to build with, or a later one (not a previous one). Otherwise, it seems that it would be an invalid test.

Has anyone had similar problems? Do you think I should be concerned about these issues?

Thanks for any input!!!
 
Ranch Hand
Posts: 147
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi David,

that should not be a problem, just make sure it works well if you run your client and server applications on different Windows (XP, 98) machines and for the JDK version you are using. Then document the JDK and OS versions in your version.txt. I think your assignment documentation mentions that in the deliverables section.

I had something like:

Java version: 1.5.0_02
Platform: Windows XP Service Pack 2, Debian GNU/Linux (testing)

(both did run without changes though...)
 
Ranch Hand
Posts: 329
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
what if I don't Solaris or Linux to test my application?? I have mention in version.txt about JDK version and platform (win 2k & XP)..

I know it should run on any platform since it is java but nothing mention (must condition) about platform in URLbird assignment.

Thanks
 
Wei-ju Wu
Ranch Hand
Posts: 147
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Nehul,

writing an application in Java does not mean that it your platform will automatically run on any platform. For example, file separators could be different, a platform might put less restrictions on the usage of ports, one system might have different security settings....

You should be fine if you list Windows XP as your only host platform in version.txt (at least my assignment said so in the "Deliverables" section), but make sure you have another Windows box available so you can run the server and client on a separate machine (for a long time the Windows version of Java has been the best one in terms of quality and performance anyways...).
 
Ken Boyd
Ranch Hand
Posts: 329
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I do understand about file system different from on platform to other but valid argument can be drawn (result in point cuts) but not failure for sure.

I am not going to test on other platform for sure (as I don't have it) and mention that in versions.txt.

Thanks for input.
 
Ranch Hand
Posts: 808
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You could always download one of the CD-bootable Linux releases to temporarily boot under Linux to test. Just a thought...
 
reply
    Bookmark Topic Watch Topic
  • New Topic