March 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic edited comment on ARQ-1534 at 3/6/14 8:26 AM: ---------------------------------------------------------------- It was (finally) included in ddmlib 22.7.0 when it was merged. I gladly resolve this. By default, port is set to 5038. System default is 5037 so started test will not polute eclipse logger anymore. was (Author: smikloso): It was (finally) included in ddmlib 22.7.0 when it was merged. I gladly close this. By default, port is set to 5038. System default is 5037 so started test will not polute eclipse logger anymore. > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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

12 years, 1 month

1
0
0 / 0

[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 resolved ARQ-1672. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > 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

12 years, 1 month

1
0
0 / 0

[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 reassigned ARQ-1672: -------------------------------------- Assignee: Stefan Miklosovic > 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 > > 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1677) Report is not colorblind friendly

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1677?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1677. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > Report is not colorblind friendly > --------------------------------- > > Key: ARQ-1677 > URL: https://issues.jboss.org/browse/ARQ-1677 > Project: Arquillian > Issue Type: Feature Request > 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.Alpha2 > > > It might be complicated for users to read results of reports. > Suggestions to improve: > 1/ introduce non-color based symbol for pass (/) and fail (x) > 2/ make red brighter and green darker > You can follow following references: > http://blog.templatemonster.com/2012/03/21/designing-colorblind-friendly-... > https://bugzilla.mozilla.org/show_bug.cgi?id=578994 -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1677) Report is not colorblind friendly

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1677?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reassigned ARQ-1677: -------------------------------------- Assignee: Stefan Miklosovic > Report is not colorblind friendly > --------------------------------- > > Key: ARQ-1677 > URL: https://issues.jboss.org/browse/ARQ-1677 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > It might be complicated for users to read results of reports. > Suggestions to improve: > 1/ introduce non-color based symbol for pass (/) and fail (x) > 2/ make red brighter and green darker > You can follow following references: > http://blog.templatemonster.com/2012/03/21/designing-colorblind-friendly-... > https://bugzilla.mozilla.org/show_bug.cgi?id=578994 -- 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

12 years, 1 month

1
0
0 / 0

[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 resolved ARQ-1675. ------------------------------------ Resolution: Done > 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 > > 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

12 years, 1 month

1
0
0 / 0

[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 updated ARQ-1675: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha2 > 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

12 years, 1 month

1
0
0 / 0

[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 reassigned ARQ-1675: -------------------------------------- Assignee: Stefan Miklosovic > 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 > > 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

12 years, 1 month

1
0
0 / 0

[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 resolved ARQ-1676. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > 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

12 years, 1 month

1
0
0 / 0

[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 reassigned ARQ-1676: -------------------------------------- Assignee: Stefan Miklosovic > 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 > > 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

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2014