Look at the Calendar posted on the blog every day.
( URL … https://reviewboardstudents.wordpress.com/calendar/ )
This is not targeted at anyone specifically in the group, just a general note.
Q / A:
Q : How to execute unit tests?
A : This shows you how to run *all* of the tests:
( http://www.reviewboard.org/docs/codebase/dev/getting-started/#running-unit-tests )
If you want to run tests under a certain “app” directory, like “accounts”, this blog post tells you how to do that:
( https://reviewboardstudents.wordpress.com/2011/09/24/running-subsets-of-review-board-tests/ )
Q : How to write unit tests?
A : The best way to start is to see what the current tests do.
granted, there aren’t many of them.
( https://github.com/reviewboard/reviewboard/blob/master/reviewboard/accounts/tests.py )
Q : How would I go about finding all the review requests that are dependant on the review within review_request_details?
I have two M2Ms, depends_on_draft, and depends_on_published.
A : They do, they’re just not exposed in the UI, so ReviewRequest should have a ManyToManyField that points to other. ReviewRequests. Say that’s called depends_on with the related_name being “blocks”. From there, you can easily go both ways.
You can access review_request_1.depends_on or from the other end, review_request_2.blocks.
Django magically links that up.