17 Aug 2005, at 09:02, Shane Mingins wrote:
[snip]
I have just started a new job where each developer's development
environment is quite "heavy". We have a local copies of the
application server, the web server, the database, and soon the BPM
server.

I like this sort of environment myself. Being able to do everything
from a developer box is a boon as far as I'm concerned.

This results in 1. a lot of setup for a new development PC;

Can't you make the setup simpler? Have standard boxes and some sort
of disk imaging to setup?

and 2. a
lot of resource requirements;

Is this a problem?

and 3. long build/deploys for running
and testing the appliications.

This is bad, but doesn't seem related to having "heavy" development
machines, but a bad testing process.

Testing is currently deploy and run and manually check the results.

This looks to me the most productive area to spend your time. Try and
automate more things and look to mocking out stuff on unit tests if
it's slowing things down.

They wish to move to a lite-weight development environment for
developers with having all the heavy stuff on an intergration machine.
[snip]

I personally like the developers boxes to be able to do everything
the integration box can do. It makes things so much simpler if
everything is the same, and boxes can be swapped around if things
break. So, unless you don't have the money for it, I'd suggest
spending your time automating the setting up of machines, and looking
to speed up your testing.

Cheers,

Adrian

To Post a message, send it to: extremeprogramming (AT) eGroups (DOT) com

To Unsubscribe, send a blank message to: extremeprogramming-unsubscribe (AT) eGroups (DOT) com

ad-free courtesy of objectmentor.com
Yahoo! Groups Links

<*To visit your group on the web, go to:

<*To unsubscribe from this group, send an email to:
extremeprogramming-unsubscribe (AT) yahoogroups (DOT) com

<*Your use of Yahoo! Groups is subject to:

lightweight approach that most people don't seem to know about is
using Jetty to run servlets in the same process as JUnit. Jetty has a
much nicer internal API than Tomcat. After writing a wrapper class you
can have tests like this:

protected void setUp() {
webserver = new WebServer(); // starts on localhost with an
arbitrary unused port
servlet = webserver.addServlet(MyServlet.class);
}

protected void tearDown() {
webserver.shutdown();
}

You can test using HttpUnit as usual, but it saves Tomcat deploys and
you can also access objects in the servlet directly since you're in the
same process.

If your webapp isn't too complicated, you can also write a main()
method to run your webapp without bothering with building a war file.
- Brian

To Post a message, send it to: extremeprogramming (AT) eGroups (DOT) com

To Unsubscribe, send a blank message to: extremeprogramming-unsubscribe (AT) eGroups (DOT) com

ad-free courtesy of objectmentor.com
Yahoo! Groups Links

<*To visit your group on the web, go to:

<*To unsubscribe from this group, send an email to:
extremeprogramming-unsubscribe (AT) yahoogroups (DOT) com

<*Your use of Yahoo! Groups is subject to: