Hello to everyone. I am a junior developper in a financial company that has an it department. Recentlty I have developped a number of web applications. The applications have been tested and been looked at by several senior staff. However, I feel it is better that we document the actual testing in order to have some sort of trace of where problems occurred (to try and avoid them in the future...). As the last one in the team, my weight does not weigh as much as others, but I try to defend my arguments as best as I can. I was just wondering if anyone could point me to resources(links, manuals etc...) explaining in detail what and how should web applications be tested( hyperlinks, etc...). I have found a few on the net but that are not very detailed, as I am interested in developping a systematic approach to the documentation of such applications. Thak you kindly for all your help.
Maybe it's time to add unit tests to the applications, if your company doesn't have them already. If you're starting from zero, create them for new functionality and for other changes being made, as well as regressions that crept in. By doing this you'll slowly increase the amount of code that's covered by tests, which should lead to quality improvements.
There are a few JUnit extensions that are useful for web apps; I like jWebUnit in particular. Some parts of the code may be amenable to testing with dbUnit or sqlUnit. [ May 25, 2007: Message edited by: Ulf Dittmer ]
If you were a tree, what sort of tree would you be? This tiny ad is a poop beast.