March 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1679?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1679: ----------------------------------- Fix Version/s: (was: recorder_1.0.0.Alpha2) > When expected exception is thrown in test method, reporter should not report it > ------------------------------------------------------------------------------- > > Key: ARQ-1679 > URL: https://issues.jboss.org/browse/ARQ-1679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > When I have > {code} > @Test(expected = SomeException.class) > public void someTest() { > throw new SomeException("this is test exception"); > } > {code} > It should not appear in resulting report. Take JUnit @Rule into account as well. > Take into consideration various test frameworks. > https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arqui... -- 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
0
0 / 0

[JBoss JIRA] (ARQ-1674) Investigate implementation of visual feedback of user interaction with application in reports for reporter

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1674?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1674. ---------------------------------- Resolution: Rejected This is particulary job form implementators (like browser screenshooter from Graphene) and it has nothing to do with core reporter itself. > Investigate implementation of visual feedback of user interaction with application in reports for reporter > ---------------------------------------------------------------------------------------------------------- > > Key: ARQ-1674 > URL: https://issues.jboss.org/browse/ARQ-1674 > 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 > > It would be handy if user has not only possibility to see screenshots taken before and after test method (and other taken screenshots in a test itself) but he would also see where exactly WebDriver clicked on a page / Android activity. > E.g. when user clicks on a button, there would be some red rectangle around it so he would see where exactly test interacted with a tested application. -- 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
0
0 / 0

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

12 years

1
0
0 / 0

[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 commented on ARQ-1681: ---------------------------------------- https://github.com/arquillian/arquillian-recorder/commit/6d3a0126d1495f04... in upstream and resolving > 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 > > 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

12 years

1
0
0 / 0

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

12 years

1
0
0 / 0

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

12 years

1
0
0 / 0

[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 commented on ARQ-1681: ---------------------------------------- In my opinion, the most doable approach is to have conf property like <property name="language">es</property> which would default to "en" and there would be templates bundled in api jar with all translations so picking the right template is the matter of parsing that property in runtime and picking the right template for that language. In case of providing own languages, the most doable way is to just translate default template to target language and sent a PR. While it is not merge and released, user always can use its own translated template anyway. > 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 > Priority: Optional > > 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

12 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic edited comment on ARQ-1685 at 3/8/14 9:15 AM: ---------------------------------------------------------------- This is indeed good point however I do not know what is the best approach in order to pass this information to xslt template. 1) Whole Report could have some "ReportConfiguration" field which would act as metadata for all report so you could extract from there that information easilly. 2) Every screenshot / video report could have boolean displayAsLink property. 3) ? I think that the most wanted option is 1) since it is the most extensionable for the future. We could hook other properties to it quite easilly. Additionally, the logic behind this was that user can have its own xsl template set in configuration so he modifies it in any way we wants when he is not satisfied with defaults. was (Author: smikloso): This is indeed good point however I do not know what is the best approach in order to pass this information to xslt template. 1) Whole Report could have some "ReportConfiguration" field which would act as metadata for all report so you could extract from there that information easilly. 2) Every screenshot / video report could have boolean displayAsLink property. 3) ? I think that the most wanted option is 1) since it is the most extensionable for the future. We could hook other properties to it quite easilly. > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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
0
0 / 0

[JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1685: ---------------------------------------- This is indeed good point however I do not know what is the best approach in order to pass this information to xslt template. 1) Whole Report could have some "ReportConfiguration" field which would act as metadata for all report so you could extract from there that information easilly. 2) Every screenshot / video report could have boolean displayAsLink property. 3) ? I think that the most wanted option is 1) since it is the most extensionable for the future. We could hook other properties to it quite easilly. > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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
0
0 / 0

[JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reassigned ARQ-1685: -------------------------------------- Assignee: Stefan Miklosovic > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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
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