cubicweb #847652 re enable testing agains real db [open]
This is precious at least when porting to a new rdbms (who said sqlserver?). the generated skeletons need fixing and devtools probably needs some good hitting on the head. reminder: this feature is supposed to work with: cd mycube/test pytest --source path/to/etc/cubicweb.d/myinstance/source realdb_test_mycube.py with --source coming from pytestconf.py (generated by cwctl create) and realdb_test_mycube.py also generated. | |
| priority | normal |
|---|---|
| type | enhancement |
| done in | <not specified> |
| load | 0.500 |
| load left | 0.500 |
| closed by | <not specified> |
similar entities
- cubicweb #1056023 be able to specify the schema in which DB tables are created and used
- Unittesting with CubicWeb
- cubicweb #1154756 SQL Server support : do not use LIMIT and OFFSET keywords in generated SQL
- cubicweb #1809383 CWAttributeAddOp crash on sql server
- cubicweb #197668 database replication for readonly access
[see all]
Comments
-
2010/06/09 16:25, written by fcayre-old
-
2010/06/21 08:08, written by sthenault
-
2010/06/30 07:33
add comment+1 on this since it would help to work on fulltext search
testing against postgres db has been implemented, based on postgresql's templates to work similarly as with sqlite (eg a template database that only has to be regenerated on schema changes, while actual test db is simply a copy of the template, hence very quick to setup).
This is slightly different that the 'testing agains real db' we used to have. Better, imo. But not sure it's viable for other backend without such template feature.
Good news. We really need this for MS SQL.