STK-Unit

stk/unit is not DROP DATABASE-safe

Bug #1239258 reported by Federico Razzoli on 2013-10-13

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	STK-Unit	Won't Fix	Low	Federico Razzoli	STK-Unit 1.0
	1.0.x	Won't Fix	Undecided	Unassigned

* 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 on 2013-10-13:

Put more dbug_log()s, before the test begins. If tbe problem occurs so early, no dbug info is logged.

Revision history for this message

Federico Razzoli (santec) wrote on 2013-10-13:

...and during de-initialization too. Dbug log should show if everything has been deinit-ed

Changed in stk-unit:
assignee:	nobody → Federico Razzoli (santec)

Federico Razzoli (santec) on 2013-10-13

Changed in stk-unit:
milestone:	none → 1.1.0

Federico Razzoli (santec) on 2013-10-13

Changed in stk-unit:
milestone:	1.1.0 → 1.0

Revision history for this message

Federico Razzoli (santec) wrote on 2013-10-15:

added a check in tc(), as the problem only happens if you call tc.
problem will naturally disappear when exception handling will be refactored

Revision history for this message

Federico Razzoli (santec) wrote on 2013-10-15:

WONT FIX AT ALL
wait for refactor

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.