August 2016 - arquillian-issues - Jboss List Archives

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-928?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak commented on ARQ-928: ------------------------------------ What's this all about? :) > Automation Test > --------------- > > Key: ARQ-928 > URL: https://issues.jboss.org/browse/ARQ-928 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-638) Option to "clean" the container before running tests

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-638?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak commented on ARQ-638: ------------------------------------ I see there are some bits in WildFly about this functionality, but mainly around embedded container. Shall we keep the issue open? /cc [~aslak] > Option to "clean" the container before running tests > ---------------------------------------------------- > > Key: ARQ-638 > URL: https://issues.jboss.org/browse/ARQ-638 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration, JBoss AS Containers > Affects Versions: 1.0.0.CR5 > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Optional > > It would be nice to have an option to have the container cleaned before launching it. > For AS7 as an example, that would mean deleting > * standalone/log > * standalone/data > * standalone/tmp > * standalone/deployments (?) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-244) Create a DeployableContainer integration for Google App Engine

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-244?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak commented on ARQ-244: ------------------------------------ Spring cleaning - how relevant is this issue after 6y? Can we close it? > Create a DeployableContainer integration for Google App Engine > -------------------------------------------------------------- > > Key: ARQ-244 > URL: https://issues.jboss.org/browse/ARQ-244 > Project: Arquillian > Issue Type: Feature Request > Components: GAE Containers > Reporter: Aslak Knutsen > Assignee: Ales Justin > Priority: Optional > > Arquillian should support start/stop/deploy and undeploy to a Google App Engine container. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-414) Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others)

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-414?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak commented on ARQ-414: ------------------------------------ I'm just wondering what shall we do with the showcase project. It seems rather outdated and most of the extensions have functional tests which are also quite good source of information. Any thoughts [~aslak] [~mjobanek] [~asotobu] > Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) > ----------------------------------------------------------------------- > > Key: ARQ-414 > URL: https://issues.jboss.org/browse/ARQ-414 > Project: Arquillian > Issue Type: Component Upgrade > Components: Examples/Showcase > Affects Versions: 1.0.0.Alpha5 > Reporter: Hendy Irawan > > Upgrade dependencies, including but not limited to: > - Arquillian 1.0.0.Alpha5 > - JUnit 4.8.2 > - cdi-api 1.0-SP4 > - glassfish 3.1-b41 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-358) Should be able to disable specific Enrichers

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-358?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak commented on ARQ-358: ------------------------------------ Is it still something we would like to implement [~aslak]? > Should be able to disable specific Enrichers > -------------------------------------------- > > Key: ARQ-358 > URL: https://issues.jboss.org/browse/ARQ-358 > Project: Arquillian > Issue Type: Feature Request > Components: Runtime Enricher SPI > Affects Versions: 1.0.0.Alpha4 > Reporter: Aslak Knutsen > > In some cases you don't want the other enrichers to jump in and resolve things. > e.g. in a CDI test suite, @EJB injections should only be handled by CDI, not the EJBEnricher as well if CDI fails (that might be the test) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2040) The Weld Arquillian adapter should not require JTA dependency in SE environment

by Antonin Stefanutti (JIRA)

Antonin Stefanutti created ARQ-2040: --------------------------------------- Summary: The Weld Arquillian adapter should not require JTA dependency in SE environment Key: ARQ-2040 URL: https://issues.jboss.org/browse/ARQ-2040 Project: Arquillian Issue Type: Feature Request Components: Weld Containers Affects Versions: 2.0.0.Beta1 Reporter: Antonin Stefanutti In a number of use cases, in the SE environment, CDI is used without JPA, while the adapter requires it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2039) The Weld Arquillian embedded adapter should not load classes that are excluded in beans.xml

by Antonin Stefanutti (JIRA)

Antonin Stefanutti created ARQ-2039: --------------------------------------- Summary: The Weld Arquillian embedded adapter should not load classes that are excluded in beans.xml Key: ARQ-2039 URL: https://issues.jboss.org/browse/ARQ-2039 Project: Arquillian Issue Type: Enhancement Components: Weld Containers Affects Versions: 2.0.0.Beta1 Reporter: Antonin Stefanutti In some use cases, like the Camel CDI extension, some classes are excluded in the beans.xml and may not be in the class path. In that case, that leads to having a {{ClassNotFoundException}} thrown by the adapter that tries to load the bean classes regardless the exclusions from the bean archive descriptor: https://github.com/arquillian/arquillian-container-weld/blob/d8f69bed899e... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1282) TestNG @DataProvider is fully invoked for each record

by Chris Dollar (JIRA)

[ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.s... ] Chris Dollar commented on ARQ-1282: ----------------------------------- Thanks for looking into this, Bartosz. Were you able to make any progress? Are there any other workarounds for using TestNG data providers with arquillian? > TestNG @DataProvider is fully invoked for each record > ----------------------------------------------------- > > Key: ARQ-1282 > URL: https://issues.jboss.org/browse/ARQ-1282 > Project: Arquillian > Issue Type: Bug > Components: JBoss AS Containers > Affects Versions: 1.0.3.Final > Reporter: Karel Cemus > Assignee: Bartosz Majsak > Attachments: ArquillianDataProvider.java, FlightServiceTest.java > > > h2. Expected behavior > TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider. > h2. Actual behavior > Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail. > h2. Example > {code:java} > @DataProvider > public Object[][] sumProvider() { > return new Object[][]{ > new Object[]{ 0, 0, 0 }, > new Object[]{ 1, 1, 2 }, > new Object[]{ 1, 5, 6 }, > new Object[]{ 5, 1, 6 } > }; > } > {code} > h3. Expected output in server log > {quote} > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > {quote} > h3. Actual output > {quote} > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2028) The precedence of ScreenshooterLifecycleObserver should be increased

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2028?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2028: -------------------------------- Fix Version/s: recorder_1.1.1.Final > The precedence of ScreenshooterLifecycleObserver should be increased > -------------------------------------------------------------------- > > Key: ARQ-2028 > URL: https://issues.jboss.org/browse/ARQ-2028 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Recorder > Affects Versions: recorder_1.1.0.Final > Reporter: Christian Schulz > Fix For: recorder_1.1.1.Final > > > Some people does cleanup after executing a test case which can lead into a blank page or similar, increasing the observer should prevent it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2037) Support additional browser capabilities for Chrome

by Standa Opichal (JIRA)

[ https://issues.jboss.org/browse/ARQ-2037?page=com.atlassian.jira.plugin.s... ] Standa Opichal commented on ARQ-2037: ------------------------------------- An example I have put to github issues not knowing the primary tracking system is here https://github.com/arquillian/arquillian-extension-drone/issues/64 > Support additional browser capabilities for Chrome > --------------------------------------------------- > > Key: ARQ-2037 > URL: https://issues.jboss.org/browse/ARQ-2037 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Final > > > Support additional browser capabilities for Chrome & remove obsolete solution that uses chrome.switches https://github.com/arquillian/arquillian-extension-drone/blob/master/dron... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues August 2016