Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Following the Test Driven Development process. #21

Open
chirag200666 opened this issue Mar 29, 2015 · 1 comment
Open

Following the Test Driven Development process. #21

chirag200666 opened this issue Mar 29, 2015 · 1 comment

Comments

@chirag200666
Copy link
Contributor

The various testing tools available for testing django like Selenium, django-debug-toolbar, django test.py, etc , have to be evaluated and the best suited for the project has to chosen. After which the project should follow the TDD principals .

@ajayaa
Copy link
Contributor

ajayaa commented Mar 30, 2015

When we talk about test-driven development there are two parts to it.

  • Functional testing + Integration testing
  • Unit testing

Functional testing is going to be done by Selenium. The unit tests are going to be written by sub-classing unittest module in python or testtools module. If there is any wrapper which Django provides around unittest that would be helpful.

Also if you can find any other library for testing which is better than above mentioned ones and has tighter integration with django then we can use that as well.

django-debug-toolbar is for printing debug information about various components of your application. From what I could understand it is not useful in test driven development in any way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants