I'm sorry of this seems a silly question, but I have to ask it - seaching for an answer generates a lot of inappropiate results, and I don't know where to start.

Basically I have a small Perl CGI application that dynamically generates lots of web pages, a light-weight XSLT-like templating framework, not dissimilar to AxKit, only it's a lot smaller and simpler. We are a small organisation, and there are only a handful of people involed in the web project - though more will contribute content one we have demonstrated that we can manage it all.

I have it running on a NT and Linux box using Apache and Apache/mod_Perl, and it has the functionality I want, and no defects as far as I can see. We're intranet based, so though I think it's securly designed, I know it's not going to be used in a very hostile environment.

I previously asked How to write documentation?, and at the moment, I'm working through that to make sure I have some, but now I need to test the application in anger, and get feedback. As far as I can figure out, the only way to do that is get users to test it. I need to know:

• What users find is wrong with it
• What features are missing from it
• How to make it faster and other load issues

My questions are, how do I do this? and what else do I need to find out? Obviously I ask people to use it, but how do I get meaningful comments back from them? What works?

The development team is small (just me), so I don't have a lot of people to ask for a code review, what red flags should I look out for?

I'm sure that there are lots of things that need fixing, but until I find out about them they are hard to fix...

As ever, many thanks in advance for any suggestions, however small.