Opened 18 years ago
Closed 18 years ago
#3174 closed enhancement (fixed)
[patch] Adding functionality concerning setup of test environment for boulder-oracle-sprint-branch
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Testing framework | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The setup of the regression test environment in the boulder-oracle-sprint branch always tries to create a new tablespace. The used statement is not feasible if working on 10g RAC having ASM. This patch gives the possibility to only create a user in a given database or to run the tests against a given user without creating anything. This should meet many scenarios. To use the functionality the user has to provide additional strings in settings.py. Keywords are:TEST_DATABASE_CREATE, TEST_USER_CREATE, TEST_DATABASE_NAME, TEST_DATABASE_USER, TEST_DATABASE_PASSWD, TEST_DATABASE_TBLSPACE, TEST_DATABASE_TBLSPACE_TMP. As soon as the variables TEST_DATABASE_CREATE and TEST_USER_CREATE exist, they can have a value which evaluates to False, which means that the corresponding part is not created. The other variables determine the names of the created database objects. If you do not set any of these variables the old behaviour should remain untouched.
Attachments (1)
Change History (2)
by , 18 years ago
| Attachment: | patch-boulder-oracle-sprint.diff added |
|---|
comment:1 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
(In [4278]) boulder-oracle-sprint: Fixed #3174 with Andreas Mock's patch.