--
Ticket URL: <http://trac.turbogears.org/ticket/2225>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
* milestone: 2.0rc1 => 2.0rc2
--
Ticket URL: <http://trac.turbogears.org/ticket/2225#comment:1>
* summary: Write a Unittesting a turbogears application tutorial =>
Write a testing a turbogears application
tutorial
Old description:
> We need to provide a nice tutorial on how to do this, specially after the
> enhancements made in #2198
New description:
We need to provide a nice tutorial on how to do this, specially after the
enhancements made in #2198
This should focus on.
- nose as the test running
- ModelTest for SA
- WebTest for the controllers
--
Ticket URL: <http://trac.turbogears.org/ticket/2225#comment:2>
> We need to provide a nice tutorial on how to do this, specially after the
> enhancements made in #2198
>
> This should focus on.
> - nose as the test running
> - ModelTest for SA
> - WebTest for the controllers
New description:
We need to provide a nice tutorial on how to do this, specially after the
enhancements made in #2198
This should focus on.
- nose as the test running
- ModelTest for SA
- WebTest for the controllers
Comment (by jorge.vargas):
syntax typo
--
Ticket URL: <http://trac.turbogears.org/ticket/2225#comment:3>
* milestone: 2.1a1 => 2.1 docs
--
Ticket URL: <http://trac.turbogears.org/ticket/2225#comment:4>
I have a turbogears 2.0 sample app that does part of this, doing
functional tests via scrape.py (http://zesty.ca/scrape/).
Maybe we can use this sample project as the basis for a more complete
testing application tutorial?
See: [http://github.com/rwilcox/turbogears2_setup_and_testing
github.com/rwilcox/turbogears2_setup_and_testing]
--
Ticket URL: <http://trac.turbogears.org/ticket/2225#comment:5>
I have already added something during the last doc sprint:
http://turbogears.org/2.1/docs/main/Testing/
Is this enough? If not, which aspects need more elaboration?
--
Ticket URL: <http://trac.turbogears.org/ticket/2225#comment:6>