Re^3: A better way to see module changes in a running web server

when developing a web application you also need to test out your application in the browser as you develop.

Yes, but that's a view part, and there's usually no need to restart webserver if you're making changes in templates.

Comment on Re^3: A better way to see module changes in a running web server

Replies are listed 'Best First'.
Re^4: A better way to see module changes in a running web server by stvn (Monsignor) on Sep 13, 2009 at 00:17 UTC
Yes, but that's a view part, and there's usually no need to restart webserver if you're making changes in templates. That is an oversimplification since the view is not just the template but also the parts of the controller that is coupled to the view (in Catalyst this is the stash, most other systems have something similar). When your controller code changes then you will need to restart the server in order to force the recompile. Not testing your models and controllers (assuming your doing some form of variant of MVC) within the context of the running web application and from a users point of view, is just irresponsible. You can test your models and your controllers using TDD, you can even test your views using TDD (Test::WWW:Mechanize, Selenium and the like), but these are tests in controlled environments following specific pathways. User Acceptance style testing should not just be done at the end, but should be done all the way through the build. It is important to know your application runs well out in the wild on a real server with real concurrency and real users using real browsers. To not do so would be just foolish and asking for trouble, remember that tests cant prove the absence of bugs. -stvn	[reply]

Replies are listed 'Best First'.

Re^4: A better way to see module changes in a running web server
by stvn (Monsignor) on Sep 13, 2009 at 00:17 UTC

Yes, but that's a view part, and there's usually no need to restart webserver if you're making changes in templates.

That is an oversimplification since the view is not just the template but also the parts of the controller that is coupled to the view (in Catalyst this is the stash, most other systems have something similar). When your controller code changes then you will need to restart the server in order to force the recompile.

Not testing your models and controllers (assuming your doing some form of variant of MVC) within the context of the running web application and from a users point of view, is just irresponsible. You can test your models and your controllers using TDD, you can even test your views using TDD (Test::WWW:Mechanize, Selenium and the like), but these are tests in controlled environments following specific pathways. User Acceptance style testing should not just be done at the end, but should be done all the way through the build. It is important to know your application runs well out in the wild on a real server with real concurrency and real users using real browsers. To not do so would be just foolish and asking for trouble, remember that tests cant prove the absence of bugs.

-stvn

[reply]