This issue existed in Trac. The original can be viewed at http://trac.turbogears.org/ticket/2225
This issue existed on SourceForge. The original can be viewed at https://sourceforge.net/p/turbogears2/tickets/18
Original Author: pedersen, Original Timestamp: 2011-03-27 20:31:02.981000
Original Body: 03/14/09 20:01:03 changed by mramm
milestone changed from 2.0rc1 to 2.0rc2.
Delete 04/15/09 15:09:47 changed by jorge.vargas
summary changed from Write a Unittesting a turbogears application tutorial to Write a testing a turbogears application tutorial.
Delete 04/15/09 15:10:53 changed by jorge.vargas
Delete 10/01/09 13:18:04 changed by percious
milestone changed from 2.1a1 to 2.1 docs.
Delete 02/20/10 23:25:15 changed by rwilcox
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: github.com/rwilcox/turbogears2_setup_and_testing
Delete 02/23/10 10:40:10 changed by chrisz
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?
Original Author: pedersen, Original Timestamp: 2012-08-24 01:35:47.111000
Original Body: - version: 2.1.0 --> 2.1.5