June 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1015) Testing of JPA queries with @UsingDataSet and @ShouldMatchDataSet

by Nicklas Karlsson (JIRA)

Nicklas Karlsson created ARQ-1015: ------------------------------------- Summary: Testing of JPA queries with @UsingDataSet and @ShouldMatchDataSet Key: ARQ-1015 URL: https://issues.jboss.org/browse/ARQ-1015 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha4 Reporter: Nicklas Karlsson Assignee: Bartosz Majsak It would be handy to automagically be able to test JPA queries with a method like @Test @UsingDataSet("all.xls") @ShouldMatchDataSet("hits.xls") public List<Customer> getAllowedCustomers() { return em.createNamedQuery("customers", Customer.class).getResultList(); } for methods with signatures returning List<?>. Currently I have functionality like @Test @UsingDataSet("all.xls") public void testCustomers() throws Exception { IDataSet expected = new XlsDataSet(getClass().getResourceAsStream("/hits.xls")); ITableMetaData metadata = expected.getTableMetaData(expected.getTableNames()[0]); IDataSet real = new PojoDataSet(em.createNamedQuery("customers", Customer.class).getResultList(), metadata); Assertion.assertEquals(expected, real); } and ublic class PojoDataSet extends DefaultDataSet { public PojoDataSet(List<?> entities, ITableMetaData metaData) { try { DefaultTable table = new DefaultTable(metaData); for (Object entity : entities) { List<Object> values = new ArrayList<Object>(); for (Column column : metaData.getColumns()) { values.add(BeanUtils.getNestedProperty(entity, column.getColumnName())); } table.addRow(values.toArray()); } addTable(table); } catch (Exception e) { throw new IllegalArgumentException(e); } } } With the column names in the metadata (from the xls) mapped to Apache BeanUtils nested properties. This approach only verifies the identities of the top-level objects (OK, it can descend @OneToOne relations) and doesn't cover the whole POJO structure. It would be nice if this process could somehow be automated with Arquillian-persistence. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
1
0 / 0

[JBoss JIRA] (ARQGRA-148) Configuration for RemoteWebDriver Drone extension

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-148: --------------------------------- Summary: Configuration for RemoteWebDriver Drone extension Key: ARQGRA-148 URL: https://issues.jboss.org/browse/ARQGRA-148 Project: Arquillian Graphene Issue Type: Sub-task Components: core Reporter: Lukáš Fryč Fix For: 2.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
12
0 / 0

[JBoss JIRA] (ARQ-868) Update Selenium version to 2.21.0

by Karel Piwko (JIRA)

Karel Piwko created ARQ-868: ------------------------------- Summary: Update Selenium version to 2.21.0 Key: ARQ-868 URL: https://issues.jboss.org/browse/ARQ-868 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.0.0.Final Reporter: Karel Piwko Assignee: Karel Piwko Update Arquillian Drone to reflect new changes in Selenium 2.21.0. * Update version * Add support for new parameters of Selenium Server * Add support for Safari driver From: http://selenium.googlecode.com/svn/trunk/java/CHANGELOG {code} WebDriver: * Safaridriver has now been added ! * Issue 3489, maximize the browser window * Significant stability improvements in firefoxdriver. * Issue 3357 log-path for chromedriver * IE driver issue 3360 * Android driver issue 3504 * Firefox issue 3559, max-connections-per-server * Issue 3520 * Issue 2826 * Native events support for Firefox 11 * Dropped native events support for Firefoxes 4-9 Grid: * Significant changes in the timeout strategy0 between hub, nodes and browser. See http://code.google.com/p/selenium/wiki/Grid2 section on timeouts. Compatibility note: It is recommended to at least update the nodes to 2.21. Upgrading only the hub will effectively disable the browser-death timeout and is *not* recommended. * Improved error messages on console * Content length issue solved, Issue 2362 * Issues 3328,3366 * Improvements in thread dumps in both hub and node, possible to corrolate the two. * Added hub api to query parameters Server: * -browserTimeout <timeoutInSeconds> added to differentiate between browser hang and client gone (which is -timeout <timeout>) - System property -Dselenium.server.timeout removed, use -timeout instead. See http://code.google.com/p/selenium/wiki/RemoteWebDriverServer for further details. * Issue 3577 {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
6
0 / 0

[JBoss JIRA] (ARQ-970) Drone: Merge tests for reusable remote session

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-970: ------------------------------ Summary: Drone: Merge tests for reusable remote session Key: ARQ-970 URL: https://issues.jboss.org/browse/ARQ-970 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: drone_1.1.0.next -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
6
0 / 0

[JBoss JIRA] (ARQ-847) Support OperaDriver in Drone

by Jan Papousek (JIRA)

Jan Papousek created ARQ-847: -------------------------------- Summary: Support OperaDriver in Drone Key: ARQ-847 URL: https://issues.jboss.org/browse/ARQ-847 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: 1.0.0.CR4 Reporter: Jan Papousek Assignee: Jan Papousek Add support for OperaDriver (http://code.google.com/p/selenium/wiki/OperaDriver). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
5
0 / 0

[JBoss JIRA] (ARQGRA-147) Fast development turnaround using Selenium Server and RemoteWebDriver session reusal

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-147: --------------------------------- Summary: Fast development turnaround using Selenium Server and RemoteWebDriver session reusal Key: ARQGRA-147 URL: https://issues.jboss.org/browse/ARQGRA-147 Project: Arquillian Graphene Issue Type: Feature Request Components: core Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 2.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (ARQ-293) Support container targeted deployments

by Aslak Knutsen (JIRA)

Support container targeted deployments -------------------------------------- Key: ARQ-293 URL: https://jira.jboss.org/browse/ARQ-293 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Fix For: 1.0.0.CR1 in some cases it is useful to be able to define different @Deployments pr target container. e.g. Container X needs a different defined deployment descriptor to work etc.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
9
0 / 0

[JBoss JIRA] (ARQ-1011) Support Groups of Containers of different Type

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1011: ---------------------------------- Summary: Support Groups of Containers of different Type Key: ARQ-1011 URL: https://issues.jboss.org/browse/ARQ-1011 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.1.Final Reporter: Aslak Knutsen Fix For: 1.1.0.CR1 Currently only Groups of Containers using the same Configuration/Adaptor are supported. e.g. Multiple JBoss AS Remote Containers. We need to extend this to allow for multiple Containers of different types. e.g. One JBoss AS 7 and one GlassFish. The current problem is the lack of ClassLoader isolation/control on the Client side. In the Embedded case we need to isolate a complete container from another while in a Remote/Managed case only the container client libs need to be isolated. Arquillian is not the one that controls the AppCL at this point which makes this hard. We would need to load the containers/client libs outside of appcl in a separate cl pr container. The required dependencies etc would be defined outside of your normal build system (e.g. arq.xml). A Module system in Arquillian Core would help, but would probably force us to fork JVM to start of with a clean app cl. This again complicates e.g. debugging the containers as you'll have to attach the debugger to the remote jvm running Arquillian/Containers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (ARQ-578) Create a Extension for handling Server State assertion during normal Servlet/JSF requests

by Aslak Knutsen (JIRA)

Create a Extension for handling Server State assertion during normal Servlet/JSF requests ----------------------------------------------------------------------------------------- Key: ARQ-578 URL: https://issues.jboss.org/browse/ARQ-578 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Aslak Knutsen The general requirements would be: * hook into existing lifecycle callbacks from server (after_render, request_destory) * inject and assert on state during request in container ** we want this to happen during request so all state is still available (@RequestScope) * assert on output on client side ** this limits the need for incontianer deps / packaging Rough API idea/draft: https://gist.github.com/1184904 If we can piggyback the ServerState Assertion object to 'any' HTML request, we should be able to reuse existing tools for client testing like htmlunit / selenium, but with incontainer assertions. This could be JSFUnit 3+ combined with a Serlvet Extension. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQ-355) Support fluent API and @DeploymentTarget for Rules

by Aslak Knutsen (JIRA)

Support fluent API and @DeploymentTarget for Rules -------------------------------------------------- Key: ARQ-355 URL: https://issues.jboss.org/browse/ARQ-355 Project: Arquillian Issue Type: Feature Request Components: Extension - Byteman Reporter: Aslak Knutsen Priority: Minor With multi container support in arquillian, the byteman integration should support @DeploymentTarget for specifying which container a rule should be deployed on. Byteman integration could follow the ShrinkWrap fluent API and make a API for rule creation, instead of having it only declarative via Annotaitons. @BMRule @DeploymentTarget("name") public static Rule createExceptionRule() { return Byteman.rule()..... } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2012