| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
Check selecting a category and selecting a sub category
|
|
|
|
|
| |
The existing fixture script generates random results so is no use for
front end testing.
|
| |
|
|
|
|
| |
Remove old unused setup-contacts code, superceded by fixtures.
|
| |
|
| |
|
|
|
|
|
| |
A new 'state' column replaces confirmed and deleted, allowing
categories to be unconfirmed, confirmed, deleted or inactive.
|
|
|
|
| |
Also include areas in auto-generated problems.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Historically in UK cobrands, bodies have had IDs the same as the MapIt
area ID they cover. This can be confusing (if you are setting up a dev
environment, say) and should not be necessary. This commit removes the
requirement entirely, by switching any ID checks to either the name of
the body, or the actual area it covers.
One note: the body name in the test has to match so that we do not get
two bodies both covering 2237 created. This will not be necessary when
the tests are compartmentalized in the next commit.
|
|
Given a MapIt area ID, the script will create a body and categories,
users with different levels of permissions, and some random problems
and updates. It can optionally empty out the database first.
|