| 14 | | Testing sprints focus on ensure a release candidate is ready for the public. Below is a list of what we'll do in this sprint. Please add any idea youhave to the list below: |
| 15 | | |
| 16 | | * unit testing execution |
| 17 | | * testing the tutorials |
| 18 | | * installing and configuring demo apps. You can help developing an application that demonstrates a popular use case for our platform. |
| 19 | | * testing of demo apps. Using tools like [http://selenium-ide.openqa.org/ selenium] to automate functional testing and help future sprints. |
| 20 | | * testing code review |
| 21 | | * proof reading documentation - what part of the docs will be ready? |
| 22 | | * Updating Hebrew translations |
| | 14 | This sprint will test if '''1.0 release candidate''' is ready by examining the behavior of django-verse players. We will focus on two types of users: first timers and experienced users. If you don't know python going through the [http://www.python.org/doc/2.3.5/tut/node3.html python tutorials] is all you need to learn django. |
| | 15 | |
| | 16 | All experienced django users can participate by either: |
| | 17 | |
| | 18 | * refactoring an existing project to 1.0 |
| | 19 | * start a fresh project on top of 1.0rc |
| | 20 | * Set up a day of work with a friend and help him as he learns django 1.0 |