For some reason I chose the scalability testing (perhaps it was my naivety).
This sort of thing is done in the form of a Django Management Command (a python script with the “Command” class). This subclasses something in Django and overrides a function that does all the work.
Look at reviewboard/reveiws/management/commands/*.py
Others are reviewboard/*/management
Run by: “./reviewboard/manage.py fixscreenshots”
What it does
ChipX86: “what’s useful is that they’re run with the site’s settings pre-loaded. You’ll have access to all our code for interacting with the database, and the right database will automatically be used in a dev tree, they’re run with: ./reviewboard/manage.py commandname args in a site install: rb-site manage /path/to/site commandname — args”
Running a Command
To Rn: ./reviewboard/manage.py commandname args
Will perform the operation on the database & you can see the results
Then you need to purge the database and start again.
purge with: ./reviewboard/manage.py flush
I created a db.py file and test ran some simple text from the file. Thinking I need the LabelCommand subcommand of the BaseCommand class, which should allow for any kind of “string” as arguments. Not much documentation on BaseCommand in Django & not much on other django books.
Plans for Tomorrow:
Determine which type of command to pursue (most likely LabelCommand).
Collect the Sprint Status Reports and post those reports.