This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes Java in General and the fly likes Java test enviroment Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Java » Java in General
Bookmark "Java test enviroment" Watch "Java test enviroment" New topic

Java test enviroment

Douglas Zaconeta Piva

Joined: Jul 28, 2011
Posts: 1

I have a doubt, in my job the people who are responsabel of the configuration of the server (production enviroment / teste enviroment).
They made the configuration of O. S. in Test enviroment difrentent of the producion enviroment.
Could This generete some issue?
Detecting problems could be more difficult?
john price
Ranch Hand

Joined: Feb 24, 2011
Posts: 495

Welcome to Java Ranch! Yes, a different environment can generate problems and detecting problems can be more difficult. For programming (coding wise), it should be the same. When you are running the server, it could fix problems and you may have an easier time detecting problems too. It could go either way. Generally, Java is pretty consistent server (networking) wise, in my experience. The main different OS wise that I've seen is GUI. I haven't noticed a big increase or reduction in problems or detection rates. The best thing to do is just retest everything in that new environment. You've run the tests once, so you should be able to run them again faster and quicker than last time. These are just my opinion and I don't have a lot of experience (although I have done cross-OS server tests) in different environment testing code, so if someone else says something contradictory, it would be probably best to go with them. I am just trying to answer your questions with the best of my ability.

Enjoy your stay here,
John Price

“Don’t worry if it doesn’t work right. If everything did, you’d be out of a job.” (Mosher's Law of Software Engineering)
“If debugging is the process of removing bugs, then programming must be the process of putting them in.” (Edsger Dijkstra)
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: Java test enviroment
It's not a secret anymore!