Home/ Questions/Q 950417
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T23:33:42+00:00

After learning about TDD and unit testing, I’m really looking to write tests when

  • 0

After learning about TDD and unit testing, I’m really looking to write tests when I code, preferably before I code because I see the benefits coding in Python. I’m developing a website, and I’m trying to write tests according to the requirements, but its proving more difficult than expected.

I can see the benefits of writing tests when you’re producing a library of code with a public interface for others to use. Developing a website, where there is really not much logic, and mostly Reading and Writing against a database seems a little harder to unit test. Mostly, I have to create/edit/delete rows in the database.

I’m using a framework (Kohana 3 for php), so 99% of all the libraries and helpers that I’m going to be using have already been tested (hopefully), so what else is their to write tests for?

I’m mostly talking about scripting languages, not about CSS or HTML, I already know about cross-browser testing.

How much can you really test when developing a web site, and how should you go about it?

Edit: Is the lack of activity on this question a sign? I understand that certain things MUST be tested, like security and the like, but how much can be written using unit tests and TDD is the question.

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Developing a website, where there is really not much logic, and mostly Reading and Writing against a database seems a little harder to unit test. Mostly, I have to create/edit/delete rows in the database.

    Not completely true.

    You have data model processing. Does the validation work? Do the calculations on the reported rows from the database work?

    You have control, sequence and navigation among pages — do the links work? The test setup will provide a logged-in-user. The test will (1) do a GET or a POST to fetch a page, then (2) confirm the page actually loaded and has the right stuff.

    You have authorization — who can do what? Each distinct test setup will provide a different logged-in-user. The tests will (1) attempt a GET or POST to process a page. Some tests will (2) confirm they got directed to error-response pages. Some tests will (2) confitrm that the GET or POST worked.

    You have content on the page — what data was fetched? The test setup will provide a logged-in-user. The test will (1) do a GET or a POST to fetch a page, then (2) confirm the page actually loaded and has the right stuff.

    • 0