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 |
| appeared in | <not specified> |
| done in | <not specified> |
| load | 0.500 |
| load left | 0.500 |
| closed by | <not specified> |
[register] [login]
#846774 Add a progress bar to cubicweb-ctl db-restore
Comments
+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.