February 2013 - arquillian-issues

[JBoss JIRA] (ARQ-679) dependencies in manifest.mf ignored when running maven install

by Dmitri Voronov (JIRA)

[ https://issues.jboss.org/browse/ARQ-679?page=com.atlassian.jira.plugin.sy... ] Dmitri Voronov commented on ARQ-679: ------------------------------------ Hi Mike, I'm facing the same issue. > dependencies in manifest.mf ignored when running maven install > -------------------------------------------------------------- > > Key: ARQ-679 > URL: https://issues.jboss.org/browse/ARQ-679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JBoss AS Containers > Affects Versions: 1.0.0.CR6 > Environment: Windows > Reporter: Michael Voegele > Labels: arquillian, manifest, maven > > I use following components / versions: > arquillian-junit-container - 1.0.0.CR6 > jboss - 7.1.0.Beta1 > jboss-as-arquillian-container-remote - 7.1.0.Beta1 > junit - 4.10 > I have folloging testcase: > @RunWith(Arquillian.class) > public class DatasourceSessionBeanTest { > @Deployment > public static JavaArchive createTestArchive() { > JavaArchive javaArchive = ShrinkWrap.create(JavaArchive.class, "datasource-test.jar"); > javaArchive.addClasses(BeanInterceptor.class); > javaArchive.addClasses(DatasourceServiceRemote.class, DatasourceSessionBean.class); > javaArchive.addClasses(AlcatrazUser.class, DataTransferObject.class); > javaArchive.addClasses(AlcatrazDAO.class, MatchMode.class); > javaArchive.addAsManifestResource("META-INF/persistence.xml", "persistence.xml"); > javaArchive.addAsManifestResource("META-INF/MANIFEST.MF", "MANIFEST.MF"); > // javaArchive.addPackages(true, "org.slf4j"); > // javaArchive.addPackages(true, "org.jboss.logmanager"); > System.out.println(javaArchive.toString(true)); > return javaArchive; > } > @EJB(mappedName = "java:app/datasource-test/DatasourceSessionBean") > private DatasourceServiceRemote datasourceService; > @Test > public void testGetByRoid() { > AlcatrazUser alcatrazUser = datasourceService.getByRoid("2531781"); > assertNotNull("Result should not be null.", alcatrazUser); > } > } > -> A manifest.mf is added containing 'Dependencies: org.slf4j' > When running the test "as a junit test", slf4j is found and logging works. > When the tests are executed from maven lifecycle, I get a ClassNotFoundException org.slf4j.Logger and the test fails. > By adding dependencies to org.slf4j and org.jboss.logmanager to the pom and by adding them to the ShrinkWrap archive (see the two commented lines), the test works, although no logging is done. > Dependencies to modules in manifest.mf should also be recognized when the tests are run from maven. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1310) Update Arquillian Core in Drone to 1.0.3.Final

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1310?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1310: ----------------------------- Fix Version/s: drone_1.2.0.Alpha2 (was: drone_1.1.1.Final) > Update Arquillian Core in Drone to 1.0.3.Final > ---------------------------------------------- > > Key: ARQ-1310 > URL: https://issues.jboss.org/browse/ARQ-1310 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.1.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.0.Alpha2 > > > Align version with the latest available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1310) Update Arquillian Core in Drone to 1.0.3.Final

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1310: -------------------------------- Summary: Update Arquillian Core in Drone to 1.0.3.Final Key: ARQ-1310 URL: https://issues.jboss.org/browse/ARQ-1310 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.1.0.Final Reporter: Karel Piwko Assignee: Karel Piwko Fix For: drone_1.1.1.Final Align version with the latest available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-994) Allow Arquillian Drone to wait asynchronously for instance creation

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-994?page=com.atlassian.jira.plugin.sy... ] Karel Piwko updated ARQ-994: ---------------------------- Priority: Major (was: Critical) > Allow Arquillian Drone to wait asynchronously for instance creation > ------------------------------------------------------------------- > > Key: ARQ-994 > URL: https://issues.jboss.org/browse/ARQ-994 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.0.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.0.next > > > Drone should create WebDriver/Selenium instances using a Future<> call or similar construction. > Sometime, an opening of browser fails (e.g. on Solaris, when something goes wrong, like machine having too many opened files) and create instance never actually returns, causing tests to hang forever.dron -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1309) Persistence extension does not work with Jacoco extension

by Peter Schonhofen (JIRA)

Peter Schonhofen created ARQ-1309: ------------------------------------- Summary: Persistence extension does not work with Jacoco extension Key: ARQ-1309 URL: https://issues.jboss.org/browse/ARQ-1309 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: 1.0.0.Alpha5 Reporter: Peter Schonhofen Assignee: Bartosz Majsak When the Jacoco and persistence extension is used together in a project, a "PersistenceExtensionInitializationException: Unable to create persistence configuration" is thrown. The cause of the exception is that in the ConfigurationImporter class the createConfiguration method receives a fieldsWithValues map with a "$jacocoData" item in it. Because the method cannot process this item, it fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1305) Defaults values for @SpringConfiguration and @SpringApplicationConfiguration

by Jakub Kurlenda (JIRA)

[ https://issues.jboss.org/browse/ARQ-1305?page=com.atlassian.jira.plugin.s... ] Jakub Kurlenda updated ARQ-1305: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-spring/pull/24 > Defaults values for @SpringConfiguration and @SpringApplicationConfiguration > ---------------------------------------------------------------------------- > > Key: ARQ-1305 > URL: https://issues.jboss.org/browse/ARQ-1305 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta1 > Reporter: Jakub Narloch > Assignee: Jakub Narloch > Fix For: spring_1.0.0.next > > > The idea is similar to the 'convention over configuration' approach from Spring Test. > When configuring test with @SpringConfiguration when no XML configuration will specified the extension by default should try to load file with exact same name as the test class and additional '-context.xml' suffix e.g. > For class org.sample.Test the default resource location should be org/sample/Test-context.xml. > In case of @SpringAnnotationConfiguration when no class or package has been specified the extension by default should scan for static (non final) class annoated with @Configuration and use it when instantiating the AnnotationApplicationContext. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1206) Add configuration option to delete all cookies on reusable browser instance

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1206?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1206: ---------------------------------- This was implemented as *reuseCookies* configuration property that is disabled by default. If set to true, we all cookies are deleted as the browser instance is created. > Add configuration option to delete all cookies on reusable browser instance > --------------------------------------------------------------------------- > > Key: ARQ-1206 > URL: https://issues.jboss.org/browse/ARQ-1206 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.1.0.Final > Reporter: Dan Allen > Assignee: Karel Piwko > Labels: starter > Fix For: drone_1.2.0.Alpha2 > > > Story: > *In order* to avoid false results from state leaking between deployments when using a reusable browser instance > *As a* tester > *I want* to be able to specify that Drone delete all cookies upon reconnecting the the resuable browser instance > Scenario: > *Given* that I've configured the WebDriver extension to use a remote reusable instance > : *And* I've configure the WebDriver extension to delete all cookies (by setting the deleteAllCookies property to true) > *When* I inject WebDriver into my test at a @Drone injection point > *Then* The browser should have no cookies > Rationale: > The deleteAllCookies configuration option eliminates potential side effects of using a remote reusable browser instance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1206) Add configuration option to delete all cookies on reusable browser instance

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1206?page=com.atlassian.jira.plugin.s... ] Karel Piwko edited comment on ARQ-1206 at 2/24/13 9:29 AM: ----------------------------------------------------------- This was implemented as *reuseCookies* configuration property that is disabled by default. If set to true, all cookies are deleted as the browser instance is created. was (Author: kpiwko): This was implemented as *reuseCookies* configuration property that is disabled by default. If set to true, we all cookies are deleted as the browser instance is created. > Add configuration option to delete all cookies on reusable browser instance > --------------------------------------------------------------------------- > > Key: ARQ-1206 > URL: https://issues.jboss.org/browse/ARQ-1206 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.1.0.Final > Reporter: Dan Allen > Assignee: Karel Piwko > Labels: starter > Fix For: drone_1.2.0.Alpha2 > > > Story: > *In order* to avoid false results from state leaking between deployments when using a reusable browser instance > *As a* tester > *I want* to be able to specify that Drone delete all cookies upon reconnecting the the resuable browser instance > Scenario: > *Given* that I've configured the WebDriver extension to use a remote reusable instance > : *And* I've configure the WebDriver extension to delete all cookies (by setting the deleteAllCookies property to true) > *When* I inject WebDriver into my test at a @Drone injection point > *Then* The browser should have no cookies > Rationale: > The deleteAllCookies configuration option eliminates potential side effects of using a remote reusable browser instance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1206) Add configuration option to delete all cookies on reusable browser instance

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1206?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1206. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/520c0527d... > Add configuration option to delete all cookies on reusable browser instance > --------------------------------------------------------------------------- > > Key: ARQ-1206 > URL: https://issues.jboss.org/browse/ARQ-1206 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.1.0.Final > Reporter: Dan Allen > Assignee: Karel Piwko > Labels: starter > Fix For: drone_1.2.0.Alpha2 > > > Story: > *In order* to avoid false results from state leaking between deployments when using a reusable browser instance > *As a* tester > *I want* to be able to specify that Drone delete all cookies upon reconnecting the the resuable browser instance > Scenario: > *Given* that I've configured the WebDriver extension to use a remote reusable instance > : *And* I've configure the WebDriver extension to delete all cookies (by setting the deleteAllCookies property to true) > *When* I inject WebDriver into my test at a @Drone injection point > *Then* The browser should have no cookies > Rationale: > The deleteAllCookies configuration option eliminates potential side effects of using a remote reusable browser instance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1177) Allow browser capabilities to be extensible

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1177?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1177. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/520c0527d... > Allow browser capabilities to be extensible > ------------------------------------------- > > Key: ARQ-1177 > URL: https://issues.jboss.org/browse/ARQ-1177 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.1.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.0.Alpha2 > > > Current Enum type for browser capabilities is not extensible. Move these to be loadable services via SPI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2013