May 2016 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reassigned ARQ-2032: ----------------------------------- Assignee: (was: Thomas Diesler) > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on ARQ-2032: ------------------------------------- OSGi on WildFly is not supported any more. > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-2032: --------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/49 > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-2032: --------------------------------- Priority: Minor (was: Major) > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.s... ] Martin Basovnik commented on ARQ-2032: -------------------------------------- I will provide pull request. > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true

by Martin Basovnik (JIRA)

Martin Basovnik created ARQ-2032: ------------------------------------ Summary: Do not start fragment bundles when property "autostartBundle" is true Key: ARQ-2032 URL: https://issues.jboss.org/browse/ARQ-2032 Project: Arquillian Issue Type: Feature Request Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2031) Test method missing in report

by Jessica Streicher (JIRA)

[ https://issues.jboss.org/browse/ARQ-2031?page=com.atlassian.jira.plugin.s... ] Jessica Streicher updated ARQ-2031: ----------------------------------- Attachment: TestTest.java SubTest.java > Test method missing in report > ----------------------------- > > Key: ARQ-2031 > URL: https://issues.jboss.org/browse/ARQ-2031 > Project: Arquillian > Issue Type: Bug > Components: Extension - Recorder > Affects Versions: 1.1.10.Final > Environment: Tests are run with Eclipse and JUnit plugin against an external Webserver (They're pure client UI tests) > Reporter: Jessica Streicher > Attachments: SubTest.java, TestTest.java > > > Whenever a testmethod fails (assertion fail), the test method is not available in the report. > I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. > The other "passed" test has two AfterTestLifecycleEvents, so an event seems to be missing when the test "fails"? > I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2031) Test method missing in report

by Jessica Streicher (JIRA)

[ https://issues.jboss.org/browse/ARQ-2031?page=com.atlassian.jira.plugin.s... ] Jessica Streicher commented on ARQ-2031: ---------------------------------------- I did some more testing and it seems to be a matter about an action that is not possible during the @After execution. In the failed test i switched the browser to an inner frame in the test method, then i tried to execute a click on an element that is not available in that frame in the @after method (the logout button basically, this is executed for all tests). I assume this messes with the events somehow. Should executing UI tasks in the @After method be generally avoided or is this a problem with Arquillian/JUnit/Recorder? > Test method missing in report > ----------------------------- > > Key: ARQ-2031 > URL: https://issues.jboss.org/browse/ARQ-2031 > Project: Arquillian > Issue Type: Bug > Components: Extension - Recorder > Affects Versions: 1.1.10.Final > Environment: Tests are run with Eclipse and JUnit plugin against an external Webserver (They're pure client UI tests) > Reporter: Jessica Streicher > > Whenever a testmethod fails (assertion fail), the test method is not available in the report. > I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. > The other "passed" test has two AfterTestLifecycleEvents, so an event seems to be missing when the test "fails"? > I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2031) Test method missing in report

by Jessica Streicher (JIRA)

[ https://issues.jboss.org/browse/ARQ-2031?page=com.atlassian.jira.plugin.s... ] Jessica Streicher updated ARQ-2031: ----------------------------------- Description: Whenever a testmethod fails (assertion fail), the test method is not available in the report. I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. The other "passed" test has two AfterTestLifecycleEvents, so an event seems to be missing when the test "fails"? I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. was: Whenever a testmethod fails (assertion fail), the test method is not available in the report. I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. The passed test also has two AfterTestLifecycleEvents, so an event seems to be missing when the test fails? I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. > Test method missing in report > ----------------------------- > > Key: ARQ-2031 > URL: https://issues.jboss.org/browse/ARQ-2031 > Project: Arquillian > Issue Type: Bug > Components: Extension - Recorder > Affects Versions: 1.1.10.Final > Environment: Tests are run with Eclipse and JUnit plugin against an external Webserver (They're pure client UI tests) > Reporter: Jessica Streicher > > Whenever a testmethod fails (assertion fail), the test method is not available in the report. > I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. > The other "passed" test has two AfterTestLifecycleEvents, so an event seems to be missing when the test "fails"? > I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2031) Test method missing in report

by Jessica Streicher (JIRA)

Jessica Streicher created ARQ-2031: -------------------------------------- Summary: Test method missing in report Key: ARQ-2031 URL: https://issues.jboss.org/browse/ARQ-2031 Project: Arquillian Issue Type: Bug Components: Extension - Recorder Affects Versions: 1.1.10.Final Environment: Tests are run with Eclipse and JUnit plugin against an external Webserver (They're pure client UI tests) Reporter: Jessica Streicher Whenever a testmethod fails (assertion fail), the test method is not available in the report. I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. The passed test also has two AfterTestLifecycleEvents, so an event seems to be missing when the test fails? I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2016