tdd - Unit testing when developing a website? -
After learning about TDD and Unit Testing, I'm actually looking to write code when I prioritize the code because I see profit coding in Python I am developing a website, and according to the requirements I am trying to write a test, but it is proving more difficult than expected.
When you are building a library, then I can see the benefits of writing. Code to develop a website with a public interface to use others where there really is no logic , And most of the database seems to be a little harder in reading and writing unit exams. Mostly, I need to create / edit / delete rows in the database.
I am using the framework (3 Kohana for PHP), so 99% of all libraries and assistants who are being used are already being tested (hopefully) What is there to write the test for them?
I'm talking about scripting mostly languages, not about CSS or HTML, I already know about cross-browser testing.
EDIT: Is this a sign of lack of activity? I understand that some things should be tested, such as safety and like, but how much can be written from the unit tests and TDD is the question.
Thank you.
Developing a website, where there is not really much logic, and reading and writing for most databases seems a little harder in examinations. Mostly, I have to create / edit / delete rows in the database.
Not quite right.
You have data model processing. Does verification work? Can the database be calculated on the rows reported?
You have controls, sequences, and navigation on pages - what links work? The test setup will provide a log-in user will take the exam (1) to bring a page to GET or one, then (2) confirm the actually loaded page and it is the right stuff.
You have authorization - Who can do that? Each separate test setup will provide a different login-in user will attempt (1) GET or POST to take action on one page. Some tests (2) will confirm that they were directed to error-response pages. Some tests (2) acknowledge that GET or Post has worked.
Do you have content on the page - what data was brought? The test setup will provide a log-in user that exams (1) a GET or a post to get a page, then (2) confirm the actually loaded page and it is the right stuff.