[JBoss JIRA] (ARQ-1706) Add multilanguage to AsciiDocExporter
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1706?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1706:
-----------------------------------
Affects Version/s: recorder_1.0.0.Alpha2
> Add multilanguage to AsciiDocExporter
> -------------------------------------
>
> Key: ARQ-1706
> URL: https://issues.jboss.org/browse/ARQ-1706
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Affects Versions: recorder_1.0.0.Alpha2
> Reporter: Alex Soto
> Assignee: Alex Soto
> Priority: Minor
> Fix For: recorder_1.0.0.Alpha3
>
>
> Add multi language to AsciiDocExporter. Currently AsciiDoc document is generated in English. Although Reporter extension allows users to set the language, AsciiDocExporter ignores it.
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1715) Merge release profile to default profile
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1715?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1715.
------------------------------------
Resolution: Done
moved to build
> Merge release profile to default profile
> ----------------------------------------
>
> Key: ARQ-1715
> URL: https://issues.jboss.org/browse/ARQ-1715
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Affects Versions: recorder_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Fix For: recorder_1.0.0.Alpha3
>
>
> It does not make sense to have a separate profile -Prelease.
> Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in <build>
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1715) Merge release profile to default profile
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1715?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1715:
-----------------------------------
Fix Version/s: recorder_1.0.0.Alpha3
> Merge release profile to default profile
> ----------------------------------------
>
> Key: ARQ-1715
> URL: https://issues.jboss.org/browse/ARQ-1715
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Affects Versions: recorder_1.0.0.Alpha1
> Reporter: Karel Piwko
> Fix For: recorder_1.0.0.Alpha3
>
>
> It does not make sense to have a separate profile -Prelease.
> Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in <build>
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1715) Merge release profile to default profile
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1715?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1715:
--------------------------------------
Assignee: Stefan Miklosovic
> Merge release profile to default profile
> ----------------------------------------
>
> Key: ARQ-1715
> URL: https://issues.jboss.org/browse/ARQ-1715
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Affects Versions: recorder_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Fix For: recorder_1.0.0.Alpha3
>
>
> It does not make sense to have a separate profile -Prelease.
> Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in <build>
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1726) Reporter does not consider screenshots taken manually in test methods
by Stefan Miklosovic (JIRA)
Stefan Miklosovic created ARQ-1726:
--------------------------------------
Summary: Reporter does not consider screenshots taken manually in test methods
Key: ARQ-1726
URL: https://issues.jboss.org/browse/ARQ-1726
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Recorder
Affects Versions: recorder_1.0.0.Alpha2
Reporter: Stefan Miklosovic
Beside screenshots taken automatically before / after test method according to configuration, user can take screenshots manually with screenshooter injection like this
{code}
@ArquillianResource Screenshooter screenshooter;
public void test()
{
screenshooter.takeScreenshot();
}
{code}
It holds for Recoder injection point as well when user can record videos manually in test method like
{code}
@ArquillianResource Recoder recorder;
public void test()
{
recorder.start();
// something is happening
recorder.stop();
}
{code}
However, these screenshots and videos does not appear in final report file because when it is taken directly by injection interface, it does not fire any screenshot report event. Logic behind screenshooter and recorder knows this because it invokes screenshooter itself but concrete screenshooter implementation does not fire them.
There needs to be a way how to report these screenshots which were taken manually as well.
Taking of screenshots manually is the "last chance" for a user to take them exactly where he needs them to be taken and not showing them in report could be justified however due to user experience these should be taken into account as well definitely.
--
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
11 years, 9 months