June 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1803) Deployments not being un-deploying when JUnit Category is used

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1803?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1803: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/3ded7d2612915b4db352... > Deployments not being un-deploying when JUnit Category is used > --------------------------------------------------------------- > > Key: ARQ-1803 > URL: https://issues.jboss.org/browse/ARQ-1803 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.4.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1803) Deployments not being un-deploying when JUnit Category is used

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1803?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1803: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/67 > Deployments not being un-deploying when JUnit Category is used > --------------------------------------------------------------- > > Key: ARQ-1803 > URL: https://issues.jboss.org/browse/ARQ-1803 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.4.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1803) Deployments not being un-deploying when JUnit Category is used

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1803: ---------------------------------- Summary: Deployments not being un-deploying when JUnit Category is used Key: ARQ-1803 URL: https://issues.jboss.org/browse/ARQ-1803 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Harness Integration Affects Versions: 1.1.4.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.1.5.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1758) Test passes although it fails unexpectedly

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1758?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen edited comment on ARQ-1758 at 6/22/14 6:00 PM: ------------------------------------------------------------- pushed upstream https://github.com/arquillian/arquillian-core/commit/e39433696861f1158818... was (Author: aslak): pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537d... > Test passes although it fails unexpectedly > ------------------------------------------ > > Key: ARQ-1758 > URL: https://issues.jboss.org/browse/ARQ-1758 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Robert Panzer > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > Attachments: debug.png > > > I have an erronous test class that cannot be loaded in the container due to a NoClassDefFoundError. (A dependent class is missing.) > The test passes unexpectedly and all test methods are reported to have passed although log entries or SystemOuts show that the methods are actually never invoked. > The problem seems to be a regression that came with the last release. > In JUnitTestRunner the TestResults exception is overwritten with null in such a case. > I will attach a screenshot of the debugger showing that. > I also have a try of a patch that I will link as soon as I prepared the pull request on github. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1796) Regression: JUnit ExpectedException is not handled correctly

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1796?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen edited comment on ARQ-1796 at 6/22/14 6:00 PM: ------------------------------------------------------------- pushed upstream https://github.com/arquillian/arquillian-core/commit/e39433696861f1158818... was (Author: aslak): pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537d... > Regression: JUnit ExpectedException is not handled correctly > ------------------------------------------------------------ > > Key: ARQ-1796 > URL: https://issues.jboss.org/browse/ARQ-1796 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Rich DiCroce > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > I have many tests using JUnit's ExcpectedException rule. In Arquillian 1.1.3, these tests worked perfectly. When I tried to update to 1.1.4, they broke. It seems like Arquillian now catches the exceptions before ExpectedException does, and propagates them back to the client. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-286) Should support JUnit @Rules

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen edited comment on ARQ-286 at 6/22/14 6:00 PM: ------------------------------------------------------------ pushed upstream https://github.com/arquillian/arquillian-core/commit/e39433696861f1158818... was (Author: aslak): pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537d... > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1773. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/e39433696861f1158818... > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1758) Test passes although it fails unexpectedly

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1758?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1758. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537d... > Test passes although it fails unexpectedly > ------------------------------------------ > > Key: ARQ-1758 > URL: https://issues.jboss.org/browse/ARQ-1758 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Robert Panzer > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > Attachments: debug.png > > > I have an erronous test class that cannot be loaded in the container due to a NoClassDefFoundError. (A dependent class is missing.) > The test passes unexpectedly and all test methods are reported to have passed although log entries or SystemOuts show that the methods are actually never invoked. > The problem seems to be a regression that came with the last release. > In JUnitTestRunner the TestResults exception is overwritten with null in such a case. > I will attach a screenshot of the debugger showing that. > I also have a try of a patch that I will link as soon as I prepared the pull request on github. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1796) Regression: JUnit ExpectedException is not handled correctly

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1796?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1796. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537d... > Regression: JUnit ExpectedException is not handled correctly > ------------------------------------------------------------ > > Key: ARQ-1796 > URL: https://issues.jboss.org/browse/ARQ-1796 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Rich DiCroce > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > I have many tests using JUnit's ExcpectedException rule. In Arquillian 1.1.3, these tests worked perfectly. When I tried to update to 1.1.4, they broke. It seems like Arquillian now catches the exceptions before ExpectedException does, and propagates them back to the client. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-286) Should support JUnit @Rules

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen resolved ARQ-286. ------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537d... > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2014