June 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1606) Support deploymentExportPath to export Exploded

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1606?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1606. ------------------------------ > Support deploymentExportPath to export Exploded > ----------------------------------------------- > > Key: ARQ-1606 > URL: https://issues.jboss.org/browse/ARQ-1606 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Currently deploymentExportPath will export a Zipped file, but the reason for exporting it is to see the content. Allow to export as exploded. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 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 closed ARQ-1796. ------------------------------ > 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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on ARQ-1804 at 6/24/14 12:49 PM: ------------------------------------------------------------ I have verified it with current {{1.1.5.Final-SNAPSHOT}} Arquillian core, and it works for me. Now, the reporter extension is not reporting an expected exception. I have tested it in [this project, on this branch|https://github.com/richfaces/richfaces-qa/tree/drone2Trying/showca...]. To run the test issue: {code} mvn clean verify -Pwildfly-managed-8-1 -Dtest=TestAjax {code} The [test file|https://github.com/richfaces/richfaces-qa/tree/drone2Trying/showcase...], one test is expected to fail. was (Author: jhuska): I have verified it with current {{1.1.5.Final-SNAPSHOT}} Arquillian core, and it works for me. Now, the reporter extension is not reporting an expected exception. I have tested it in [this project, on this branch|https://github.com/richfaces/richfaces-qa/tree/drone2Trying/showca...]. To run the test issue: {code} mvn clean verify -Pwildfly-managed-8-1 -Dtest=TestAjax {code} > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1804. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream, https://github.com/arquillian/arquillian-core/commit/ade8eb99b3d4c808c75f... > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on ARQ-1804: ---------------------------------- I have verified it with current {{1.1.5.Final-SNAPSHOT}} Arquillian core, and it works for me. Now, the reporter extension is not reporting an expected exception. I have tested it in [this project, on this branch|https://github.com/richfaces/richfaces-qa/tree/drone2Trying/showca...]. To run the test issue: {code} mvn clean verify -Pwildfly-managed-8-1 -Dtest=TestAjax {code} > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1804: ------------------------------- Fix Version/s: 1.1.5.Final > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1751) Implement web-based console which streams reporting events in realtime

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1751?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1751: ------------------------------------ This is a _almost_ working prototype from DevNation hackfest; https://github.com/aslakknutsen/arquillian-recorder/tree/ARQ-1751 The missing parts; * probably integrate bowler with Maven to build the UI JS parts automatically * some missmatch in URL used by the UI and backend atm * possible some missmtach in the format used General improvements require some more changes in recorder core. e.g.; * Should the same JAX-B model be used on Client and Container side? * JAX-B in general generates XML, XML is hell'ish in a JS client ** Currently worked around by XML from Test client to Server, and Gson converted jax-b model from Server to JS client * The full report is pushed to server for each @Test * Missing image upload. > Implement web-based console which streams reporting events in realtime > ---------------------------------------------------------------------- > > Key: ARQ-1751 > URL: https://issues.jboss.org/browse/ARQ-1751 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Labels: hack-idea > > Every fired reporter event would be observed by additional observer which would send it to REST end point of some running "reporter server" so when user starts some test, he would see in web console in ordinary browser how some test is going. > Reporter would "stream" reporting events to console ui so user would not have to wait until the whole test is done but he would see how test is going on in realtime. > This can be handy particulary in CI environment. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1701. ------------------------------------ Resolution: Done > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > 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.Alpha4 > > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1701: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha4 > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > 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.Alpha4 > > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1751) Implement web-based console which streams reporting events in realtime

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1751?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reassigned ARQ-1751: -------------------------------------- Assignee: Stefan Miklosovic > Implement web-based console which streams reporting events in realtime > ---------------------------------------------------------------------- > > Key: ARQ-1751 > URL: https://issues.jboss.org/browse/ARQ-1751 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Labels: hack-idea > > Every fired reporter event would be observed by additional observer which would send it to REST end point of some running "reporter server" so when user starts some test, he would see in web console in ordinary browser how some test is going. > Reporter would "stream" reporting events to console ui so user would not have to wait until the whole test is done but he would see how test is going on in realtime. > This can be handy particulary in CI environment. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2014