March 2014 - arquillian-issues - Jboss List Archives

[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 commented on ARQ-1702: ---------------------------------------- in upstream and resolving as done https://github.com/arquillian/arquillian-recorder/commit/adfc54756a6cc18c... > 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 > Priority: Minor > > 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

12 years

1
0
0 / 0

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

12 years

1
0
0 / 0

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

12 years

1
0
0 / 0

[JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin... ] Juraj Húska updated ARQGRA-423: ------------------------------- Assignee: (was: Juraj Húska) > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- 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] (ARQGRA-423) Provide a way to intercept in some order

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin... ] Juraj Húska updated ARQGRA-423: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/99 (was: https://github.com/arquillian/arquillian-graphene/pull/95) Linking a new PR, with all fixes according to [~lfryc] comments. > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Assignee: Juraj Húska > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- 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] (ARQGRA-423) Provide a way to intercept in some order

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin... ] Juraj Húska updated ARQGRA-423: ------------------------------- Status: Open (was: Pull Request Sent) Rejecting this pull request, as new one will be created against different branch > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Assignee: Juraj Húska > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- 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-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 resolved ARQ-1703. ------------------------------------ Assignee: Stefan Miklosovic Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > 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

12 years

1
0
0 / 0

[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 commented on ARQ-1703: ---------------------------------------- in upstream and resolving https://github.com/arquillian/arquillian-recorder/commit/3a55c1783573b62b... use it like {code} @Test @ReportMessage("This test should be executed manually too") public void throwExceptionTest() { Assert.assertTrue(true); } {code} It will be added to the method report properties when non-empty. > 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 > Priority: Minor > > 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

12 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1703) Add annotation to add comments to test report

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1703?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1703: ---------------------------------- This is great idea. > 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 > Priority: Minor > > 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

12 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1535) Warp: getting intermittent issues in RichFaces tests

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1535?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved ARQ-1535. ----------------------------- Resolution: Rejected Probably fixed by ARQ-1683 > Warp: getting intermittent issues in RichFaces tests > ---------------------------------------------------- > > Key: ARQ-1535 > URL: https://issues.jboss.org/browse/ARQ-1535 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: warp_1.0.0.Alpha7 > > > See RF-13222 for issue details. -- 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