Worker engine should not be testing against LOG calls

Bug #1284348 reported by Joshua Harlow
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Triaged
Medium
Unassigned

Bug Description

The worker engine right now has unittests that check whether LOG (warn, exception, error) functions are called and associates these calls with whether a test passes or fails. This binds unittests to logging in a very unnatural way; LOG calls are changed to easily and to often and should not be depended on for failing/passing unit tests. An alternate mechanism checking against exceptions being raised, functions being called (*or other*) would be much more appropriate.

Joshua Harlow (harlowja)
description: updated
Joshua Harlow (harlowja)
Changed in taskflow:
importance: Undecided → High
Joshua Harlow (harlowja)
Changed in taskflow:
importance: High → Medium
Joshua Harlow (harlowja)
Changed in taskflow:
milestone: none → next-kilo
Joshua Harlow (harlowja)
Changed in taskflow:
status: New → Triaged
Sowmya Divvi (sowmya)
affects: taskflow → heat (Ubuntu)
Changed in heat (Ubuntu):
milestone: 0.6.0 → none
affects: heat (Ubuntu) → ubuntu
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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