![]() ![]() If you are using servlets, you should be able to provide a fake HTTP request or fake parameters and get the output from the servlet directly.When you make components that are truly independent, write JUnit tests for them. ![]() For small applications, a manual regression test plan is a good place to start. ![]() I think the best approach is to use many different kinds of testing and divide and conquer. The database is particularly difficult because a good deal of data often needs to be set up before you can meaningfully test anything but the login screen. That boiler plate could change to a new color scheme or something else independent of the logic of your application that could potentially break all your tests. HTML is tough because you really want to isolate the data that comes specifically from a given method as opposed to the boiler-plate and layout scaffolding which is common to every page. This is a worst-case scenario for unit testing. Many of the "methods" in a web application take a HTTP request as input and produce HTML output with the side effect of using the database and updating some kind of session state somewhere. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |