January 2012 - arquillian-issues - Jboss List Archives

[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

11 years, 11 months

3
9
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

11 years, 11 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

11 years, 11 months

2
1
0 / 0

[JBoss JIRA] (ARQAJO-98) Turn off logging when adding selenium/page extensions

by Lukáš Fryč (Created) (JIRA)

Turn off logging when adding selenium/page extensions ----------------------------------------------------- Key: ARQAJO-98 URL: https://issues.jboss.org/browse/ARQAJO-98 Project: Arquillian Ajocado Issue Type: Enhancement Components: core Affects Versions: 1.0.0.CR2 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Output is too verbose and does not have any value. -- 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

11 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQAJO-97) Migrate implementation of ReferencedLocator from metamer to Ajocado

by Juraj Huska (JIRA)

Migrate implementation of ReferencedLocator from metamer to Ajocado ------------------------------------------------------------------- Key: ARQAJO-97 URL: https://issues.jboss.org/browse/ARQAJO-97 Project: Arquillian Ajocado Issue Type: Task Reporter: Juraj Huska Assignee: Lukáš Fryč Please, migrate implementation of ReferencedLocator from metamer to Ajocado, to be able to migrate Metamer fully on Arquillian. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQAJO-88) Add more usage examples to Utility Classes section in docs

by Juraj Huska (JIRA)

Add more usage examples to Utility Classes section in docs ---------------------------------------------------------- Key: ARQAJO-88 URL: https://issues.jboss.org/browse/ARQAJO-88 Project: Arquillian Ajocado Issue Type: Feature Request Components: doc Affects Versions: 1.0.0.CR1 Reporter: Juraj Huska Assignee: Lukáš Fryč The section with Utility Classes should provide code usage examples to show they functionality. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (ARQAJO-63) Screencast on Ajocado

by Lukáš Fryč (JIRA)

Screencast on Ajocado --------------------- Key: ARQAJO-63 URL: https://issues.jboss.org/browse/ARQAJO-63 Project: Arquillian Ajocado Issue Type: Task Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQAJO-64) Blog on Ajocado

by Lukáš Fryč (JIRA)

Blog on Ajocado --------------- Key: ARQAJO-64 URL: https://issues.jboss.org/browse/ARQAJO-64 Project: Arquillian Ajocado Issue Type: Task Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (ARQAJO-82) Cross-site request problems for Ajocado

by Karel Piwko (JIRA)

Cross-site request problems for Ajocado --------------------------------------- Key: ARQAJO-82 URL: https://issues.jboss.org/browse/ARQAJO-82 Project: Arquillian Ajocado Issue Type: Feature Request Components: integration Affects Versions: 1.0.0.CR1 Reporter: Karel Piwko Assignee: Lukáš Fryč Evaluate if Ajocado is affected by ARQ-521 and if proprosed solution will work for it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
2
0 / 0

[JBoss JIRA] (ARQAJO-119) isVisible JS condition should not fail when element is not present

by Juraj Huska (JIRA)

Juraj Huska created ARQAJO-119: ---------------------------------- Summary: isVisible JS condition should not fail when element is not present Key: ARQAJO-119 URL: https://issues.jboss.org/browse/ARQAJO-119 Project: Arquillian Ajocado Issue Type: Enhancement Components: api, core Affects Versions: 1.0.0.CR3 Reporter: Juraj Huska Priority: Minor The method isVisible of object selenium is failing (throwing exception element not found), when the element is not present on the page. This behavior is quite unhandy in for invocations such as: {code} waitModel.failWith("Popup did not show").until(elementVisible.locator(popup)); {code} It is only the example, but this will fail and no wait is done at all. To simulate it without failing, one has to write: {code} waitModel.failWith("Popup did not show").until(elementPresent.locator( jq( popup.getRawLocator + ":visible" ) )); {code} So he *has to use elementPresent condition and add :visible locator*, even when he really just wants to verify whether the element is visible, since it is obvious that the element can be present and not be visible at the same time. So my propose will be to *catch* the ElementNotFoundException in selenium invocation of isVisible and to *return false*, when the element is not present. For me this sounds quite reasonably. *Is there any problem with it? Will it be problem to change the Selenium API, and to make it not consistent with standard Selenium 1,2 ?* -- 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

11 years, 11 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2012