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

In reply to Re^4: A better way to see module changes in a running web server by stvn
in thread A better way to see module changes in a running web server by swartz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.