Opened 12 years ago
Last modified 10 years ago
#551 accepted enhancement
Create test that makes sure all migrations are sane
| Reported by: | Christopher Allan Webber | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | programming | Keywords: | test |
| Cc: | lotusecho | Parent Tickets: |
Description
We should have a unit test that instantiates the tables at their first, pre-migration state (basically right after the move to SQL, commit ce29c140ed90fe0e19ed1b68ca8f7cf27aa03e8e) and runs all migrations, then creates a new database and instantiates the models at their current state, and sees if they match. If they don't, the test should fail.
Note: we can't test for constraints in sqlalchemy, but we should otherwise be able to test to moderately general migration sanity.
(Bonus points if it adds a user and a couple of media entries with appropriate media files, etc, but not required to close this bug.)
Change History (4)
comment:1 by , 11 years ago
| Cc: | added |
|---|
comment:2 by , 11 years ago
| Owner: | set to |
|---|---|
| Status: | new → in_progress |
I'm adding this to my list of things to do for OPW.
comment:3 by , 11 years ago
| Owner: | removed |
|---|---|
| Status: | in_progress → accepted |
comment:4 by , 11 years ago
| Keywords: | test added |
|---|
Note:
See TracTickets
for help on using tickets.
Cc'ing LotusEcho who will be working on testing stuff. This might be something good to plan into the testing overhaul OPW work.