[JBoss JIRA] (ARQ-1672) Provide default xstl template possibility for screenshooter and recorder implementators
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1672?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1672.
----------------------------------
> Provide default xstl template possibility for screenshooter and recorder implementators
> ---------------------------------------------------------------------------------------
>
> Key: ARQ-1672
> URL: https://issues.jboss.org/browse/ARQ-1672
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Affects Versions: recorder_1.0.0.Alpha1
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: recorder_1.0.0.Alpha2
>
>
> In case of HTML exporter, template used for XSLT transformation can be configured in arq.xml via property so it is up to user of that extension to come with a custom one. When no such property is defined, default XSLT template bundled in reporter is used - it is also shipped in jar.
> However, there is no way how to define different default template for screenshooter / recorder implementators so target user would use template of that implementation and not the core one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (ARQ-1676) Configure frequency of exporting reports for reporting extension
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1676?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1676.
----------------------------------
> Configure frequency of exporting reports for reporting extension
> ----------------------------------------------------------------
>
> Key: ARQ-1676
> URL: https://issues.jboss.org/browse/ARQ-1676
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Affects Versions: recorder_1.0.0.Alpha1
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Fix For: recorder_1.0.0.Alpha2
>
>
> By default, gathered report is exported at the end of the whole Arquillian lifecycle. In case something terrible happens and test does not reach this point and report is gone. It would be useful to provide a configuration option which would say when exactly user wants that report get generated, e.g. after every method or test class. By doing so, even test fatally crashes in the middle, he has at least some knowledge about the test results finished up to that point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (ARQ-1681) Implement multilanguage support in Arquillian Exporter
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1681?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1681.
----------------------------------
> Implement multilanguage support in Arquillian Exporter
> ------------------------------------------------------
>
> Key: ARQ-1681
> URL: https://issues.jboss.org/browse/ARQ-1681
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Affects Versions: recorder_1.0.0.Alpha1
> Reporter: Alex Soto
> Assignee: Stefan Miklosovic
> Priority: Optional
> Fix For: recorder_1.0.0.Alpha2
>
>
> Currently Reports are generated in English. In reports there are some static information like some labels or footnotes, ...
> Because test results are also documentation, it has sense that the report may be a part of rendered final documents, but if for example all of them are written in Spanish, then it is strange to have one document in English.
> For this reason I think we should add some internal and external default directories where to find translations so people can collaborate in translations, but also allowing users to provide their own.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (ARQ-1675) Implement multiple file extensions for report type for reporter
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1675?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1675.
----------------------------------
> Implement multiple file extensions for report type for reporter
> ---------------------------------------------------------------
>
> Key: ARQ-1675
> URL: https://issues.jboss.org/browse/ARQ-1675
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Affects Versions: recorder_1.0.0.Alpha1
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Fix For: recorder_1.0.0.Alpha2
>
>
> ReportType class (https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-...) returns an string of extension report type (which in fact it is the extension of the file). There are some output formats which accepts different extensions, for example valid AsciiDoc extensions are ad, adoc or asciidoc.
> So it would be a good approach to adapt the interface to allow the definition of multiple extensions.
> Of course this generates a problem with which exporter to use in case of conflicts:
> For example one can define:
> html, html5
> and
> html, html4
> and asks for html exporter. I think that in this case the first match should be returned.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (ARQ-1670) Create recording & reporting extension for Arquillian
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1670?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1670.
----------------------------------
> Create recording & reporting extension for Arquillian
> -----------------------------------------------------
>
> Key: ARQ-1670
> URL: https://issues.jboss.org/browse/ARQ-1670
> Project: Arquillian
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Fix For: recorder_1.0.0.Alpha1
>
>
> There is not any reporting facility for Arquillian as such - besides plain surefire / junit reports.
> It would be useful if screenshots and video records of tests were incorporated to such extension in connectin with reporting of all Arquillian setup in one place, possibly with exporting such report to various output formats (html, xml, json, asciidoc).
> Additionally, there is a need to be able to provide single SPI which would any Arquillian extension use in order to report its execution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (ARQ-1703) Add annotation to add comments to test report
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1703?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1703.
----------------------------------
> Add annotation to add comments to test report
> ---------------------------------------------
>
> Key: ARQ-1703
> URL: https://issues.jboss.org/browse/ARQ-1703
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Reporter: Alex Soto
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: recorder_1.0.0.Alpha2
>
>
> Sometimes when you write some automatic tests, you also want that QA team execute them manually, maybe because that business case is critical or because automatic test can only cover one part.
> So it would be good if for example we could annotate test method with an annotation like:
> @Report("This test should be executed manually too")
> And then this message may be available on reporter class and could be written to report.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (ARQ-1702) Add optional label for report title
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1702?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1702.
----------------------------------
> Add optional label for report title
> -----------------------------------
>
> Key: ARQ-1702
> URL: https://issues.jboss.org/browse/ARQ-1702
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Reporter: Alex Soto
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: recorder_1.0.0.Alpha2
>
>
> By default report title is fixed in xslt template or in AsciiDoc document. Allow users to define its own title may open the door to do something like:
> <extension>
> <property name="title">Tests results under ${env}</property>
> So the title can be for example "Test results under PRE environment", "Test results under QA environment", and so on, instead of fixed title.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months