August 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on ARQ-1831 at 8/12/14 7:45 AM: ----------------------------------------------------------- Linked PR. I made to show only about 10 lines of stacktrace, first line is bold and bigger, and the stacktrace is scrollable after a click (there is a popup which encourages a tester to click on the stacktrace in order to make it scrollable). was (Author: jhuska): Linked PR. > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Minor > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1839) Reporter: if test does not have screenshots then next test report has wrong indentation

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQ-1839?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated ARQ-1839: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/9 > Reporter: if test does not have screenshots then next test report has wrong indentation > --------------------------------------------------------------------------------------- > > Key: ARQ-1839 > URL: https://issues.jboss.org/browse/ARQ-1839 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Trivial > Attachments: wrongIndentation.png > > > Please see screenshot for more information what I mean. > There is probably some small CSS issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated ARQ-1831: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/9 > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Minor > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on ARQ-1831: ---------------------------------- Linked PR. > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Minor > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic edited comment on ARQ-1728 at 8/11/14 8:42 AM: ----------------------------------------------------------------- I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation so I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but I gave it up in the middle. This approach is way to go, HTH was (Author: smikloso): I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation it I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but it gave it up in the middle. This approach is way to go, HTH > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic edited comment on ARQ-1728 at 8/11/14 8:44 AM: ----------------------------------------------------------------- I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation so I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but I gave it up in the middle. This approach is way to go, HTH Maybe [~jhuska] could do this in his spare time as a logging guy ;) was (Author: smikloso): I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation so I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but I gave it up in the middle. This approach is way to go, HTH > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1728: ---------------------------------------- I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation it I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but it gave it up in the middle. This approach is way to go, HTH > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1830) Only the last Test Class of some subset of Test classes is reported with TestNG runner

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQ-1830?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on ARQ-1830: ---------------------------------- [~smikloso] could you please give me some entry points, the places in the code where this issue is likely to be introduced ? > Only the last Test Class of some subset of Test classes is reported with TestNG runner > -------------------------------------------------------------------------------------- > > Key: ARQ-1830 > URL: https://issues.jboss.org/browse/ARQ-1830 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj Húska > > When you have TestNG test suite, after running some *subset* of all test classes (particular test classes or e.g. all classes in one package), then only the last test class is reported. > It works when you run all tests, and also with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1839) Reporter: if test does not have screenshots then next test report has wrong indentation

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQ-1839?page=com.atlassian.jira.plugin.s... ] Juraj Húska reassigned ARQ-1839: -------------------------------- Assignee: Juraj Húska > Reporter: if test does not have screenshots then next test report has wrong indentation > --------------------------------------------------------------------------------------- > > Key: ARQ-1839 > URL: https://issues.jboss.org/browse/ARQ-1839 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Trivial > Attachments: wrongIndentation.png > > > Please see screenshot for more information what I mean. > There is probably some small CSS issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-446: ----------------------------------- Hey Chris, your fix is now available in {{2.1.0.Alpha1}}: http://arquillian.org/blog/2014/08/07/arquillian-graphene-2-1-0-Alpha1/ > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Assignee: Chris Jones > Fix For: 2.1.0.Alpha1 > > Attachments: graphene-groovy-test.zip, groovy-page-support (fixed paths).patch, groovy-page-support.patch > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass(<generated>) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues August 2014