stk/unit is not DROP DATABASE-safe
Bug #1239258 reported by
Federico Razzoli
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| STK-Unit |
Won't Fix
|
Low
|
Federico Razzoli | ||
| 1.0.x |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
* run a working test case
* DROP the test case
* try running the test case again
Old results will re-appear. If the database was empty, only the results template will appear.
Fix should be easy:
1) return error if db no exists
2) use @__stk_u_tr to show results
Revision history for this message
| Federico Razzoli (santec) wrote | #1 |
Revision history for this message
| Federico Razzoli (santec) wrote | #2 |
| Changed in stk-unit: | |
| assignee: | nobody → Federico Razzoli (santec) |
| Changed in stk-unit: | |
| milestone: | none → 1.1.0 |
| Changed in stk-unit: | |
| milestone: | 1.1.0 → 1.0 |
Revision history for this message
| Federico Razzoli (santec) wrote | #3 |
Revision history for this message
| Federico Razzoli (santec) wrote | #4 |
| Changed in stk-unit: | |
| importance: | Critical → Low |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Put more dbug_log()s, before the test begins. If tbe problem occurs so early, no dbug info is logged.