Reporting - Add extension

[fedorov]

Extension is documented here: http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Extensions/Reporting

[jcfr]

Hi Andriy,

When building on my workstation, one test is failing qSlicerReportingModuleGenericTest, I will try the fix reported in http://www.na-mic.org/Bug/view.php?id=2251 and will keep you posted.

See http://slicer.cdash.org/testDetails.php?test=2496227&build=29670

Thanks
Jc

[fedorov]

JC, fyi I have the same error on my mac laptop. However the source of this issue is outside the Reporting module, right?

Also, see this issue https://github.com/fedorov/Reporting/issues/2, which explains how to run the test with the paths initialized properly, so that you can confirm the test itself passes.

Please consider that this version of the extension is not final, and our main goal at this point is to be able to share this module with the collaborators to make the extension available for early testing and to collect feedback on the provided functionality.

It is also very important for us to test the robustness of the whole process (installation, uninstallation and update of this extension by collaborators using different OSs), and get feedback from users asap.

Could we consider enabling extension while you work on the testing infrastructure fixes, to allow us to get feedback from users and concurrently work on fixing the reported issues in the extension?

[jcfr]

Good morning,
No problem. The plan is to integrate the extension. Will do it by noon.
Jc

On Tue, Jul 24, 2012 at 8:34 AM, Andrey Fedorov <
reply@reply.github.com

wrote:

JC, fyi I have the same error on my mac laptop. However the source of this
issue is outside the Reporting module, right?

Also, see this issue https://github.com/fedorov/Reporting/issues/2, which
explains how to run the test with the paths initialized properly, so that
you can confirm the test itself passes.

Please consider that this version of the extension is not final, and our
main goal at this point is to be able to share this module with the
collaborators to make the extension available for early testing and to
collect feedback on the provided functionality.

It is also very important for us to test the robustness of the whole
process (installation, uninstallation and update of this extension by
collaborators using different OSs), and get feedback from users asap.

Could we consider enabling extension while you work on the testing
infrastructure fixes, to allow us to get feedback from users and
concurrently work on fixing the reported issues in the extension?

---

Reply to this email directly or view it on GitHub:
#33 (comment)

+1 919 869 8849

[fedorov]

Thank you, JC!

On Tue, Jul 24, 2012 at 8:40 AM, Jean-Christophe Fillion-Robin
reply@reply.github.com
wrote:

Good morning,
No problem. The plan is to integrate the extension. Will do it by noon.
Jc

On Tue, Jul 24, 2012 at 8:34 AM, Andrey Fedorov <
reply@reply.github.com

wrote:

JC, fyi I have the same error on my mac laptop. However the source of this
issue is outside the Reporting module, right?

Also, see this issue https://github.com/fedorov/Reporting/issues/2, which
explains how to run the test with the paths initialized properly, so that
you can confirm the test itself passes.

Please consider that this version of the extension is not final, and our
main goal at this point is to be able to share this module with the
collaborators to make the extension available for early testing and to
collect feedback on the provided functionality.

It is also very important for us to test the robustness of the whole
process (installation, uninstallation and update of this extension by
collaborators using different OSs), and get feedback from users asap.

Could we consider enabling extension while you work on the testing
infrastructure fixes, to allow us to get feedback from users and
concurrently work on fixing the reported issues in the extension?

---

Reply to this email directly or view it on GitHub:
#33 (comment)

+1 919 869 8849

---

Reply to this email directly or view it on GitHub:
#33 (comment)

[jcfr]

Extension has been integrated into master - See a4aa076