The description should retain $output information when being reported

Bug #386368 reported by Marc Tardif on 2009-06-12
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Checkbox
Low
Unassigned

Bug Description

Hello,

According to my experience, output is captured for both manual and shell plugin since it's possible to use the $output syntax in the description. However, it seems it's only logged for the shell plugin.

Currently, I'm working on some test cases that, after gathering certain information, show it to the user and ask something such as "Is this correct?". Since from time to time a human error or a change in the pass criteria could happen, I think it would be nice to have the output of those commands in the report so that when reviewing old results it could be found what was the information that was supplied to the tester to decide the test result.

Do you agree on this?

Best regards,
    Javier

Marc Tardif (cr3) on 2009-06-18
Changed in checkbox:
assignee: nobody → Marc Tardif (cr3)
importance: Undecided → High
milestone: none → 0.8-alpha3
status: New → Confirmed
Daniel Manrique (roadmr) wrote :

Javier,

This bug just turned 2 years old, so as a birthday present I'd like to close it, but I'd like to get your confirmation on whether this feature is already implemented in recent Checkbox versions. I seem to remember that all the text we capture in the comments box gets added to the report but I'd prefer you to confirm if it works the way you want now.

Thanks for your time.

Javier Collado (javier.collado) wrote :

@Daniel

This problem is still present.

Ara Pulido (ara) on 2011-08-25
Changed in checkbox:
assignee: Marc Tardif (cr3) → Canonical Hardware Certification (canonical-hw-cert)
milestone: 0.8-alpha3 → 0.12.7
milestone: 0.12.7 → later
Ara Pulido (ara) on 2012-03-20
Changed in checkbox:
milestone: later → none

This really can't be high priority if it's been open for 3 years. I'll change to medium

Changed in checkbox:
importance: High → Medium
Changed in checkbox:
assignee: Canonical Hardware Certification (canonical-hw-cert) → nobody
Jeff Lane (bladernr) wrote :

Agreed with Last Year Brendan... but even more so, demoting it to Low... we only have 3 jobs that use this feature, in total, none of which are part of certification. I'm actually inclined to call this a wont-fix, but perhaps it's worth looking at at some point.

Changed in checkbox:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions