You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will, in any case, set the self.evidence object to Evidence of type RawDisk
Additional information
Not sure if this is a bug or a misunderstanding on my side, but intuitively I would expect the Evidence type class to be instantiated and assigned to self.evidence later. Something like this:
What steps will reproduce the bug?
Using the regular developer setups as proposed in the Wiki when trying to create new Tests that do not use
RawDisk
asEvidence
typeWhat is the expected behavior?
In my opinion when I look at these lines of code
turbinia/turbinia/workers/workers_test.py
Lines 47 to 49 in a56d21e
I expect to be able to pass a
Evidence
type and use that in the unittest.What do you see instead?
Looking at a couple of lines later we see this:
turbinia/turbinia/workers/workers_test.py
Line 70 in a56d21e
This will, in any case, set the
self.evidence
object to Evidence of typeRawDisk
Additional information
Not sure if this is a bug or a misunderstanding on my side, but intuitively I would expect the
Evidence
type class to be instantiated and assigned toself.evidence
later. Something like this:The
task_class
parameter does that in the line:turbinia/turbinia/workers/workers_test.py
Line 59 in a56d21e
The text was updated successfully, but these errors were encountered: