[JBoss JIRA] Created: (ARQ-77) Support @EJB injection
by Andrew Lee Rubinger (JIRA)
Support @EJB injection
-----------------------
Key: ARQ-77
URL: https://jira.jboss.org/jira/browse/ARQ-77
Project: Arquillian
Issue Type: Feature Request
Components: OpenEJB Containers
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Tests should be able to have class or instance members injected according to @EJB semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible resolvers (which need an EJB name, module name, app name, and business interface name). Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (ARQ-299) Create a IN_CONTAINER Exception Proxy
by Aslak Knutsen (JIRA)
Create a IN_CONTAINER Exception Proxy
-------------------------------------
Key: ARQ-299
URL: https://jira.jboss.org/browse/ARQ-299
Project: Arquillian
Issue Type: Feature Request
Reporter: Aslak Knutsen
On Exception, the IN_CONTAINER TestRunner tries to serialize the caught Exception back to the Client so it can be displayed as if it was local. The problem is if you don't have the Client lib on Client Classpath or you have the wrong version of it. This results in a Deserialization exception on the Client.
We probably have to not Serialize the actual Exception, but serialize a Textual representation of it, which we can create a 'proxy' Exception of on the client side and make it 'look' like the original.
--
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, 1 month
[JBoss JIRA] Created: (ARQAJO-67) Reduce logging levels
by Karel Piwko (JIRA)
Reduce logging levels
---------------------
Key: ARQAJO-67
URL: https://issues.jboss.org/browse/ARQAJO-67
Project: Arquillian Ajocado
Issue Type: Feature Request
Components: junit, testng
Affects Versions: 1.0.0.Alpha2
Reporter: Karel Piwko
Assignee: Lukáš Fryč
Ajocado outputs many debug information under INFO logging level. This level should be reduced to debug or even debug/fine.
It makes execution of the test slower and this information is not required until debugging.
It manifest namely with JUnit which redirects test output to console.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (ARQ-591) Create extension for running JavaScript unit tests by Drone
by Lukáš Fryč (JIRA)
Create extension for running JavaScript unit tests by Drone
-----------------------------------------------------------
Key: ARQ-591
URL: https://issues.jboss.org/browse/ARQ-591
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Drone
Reporter: Lukáš Fryč
This extension can handle several JS unit testing libraries,
but at initial point, I suggest to go with QUnit [1].
At first, extension needs to go through available test definitions
and prepare list of tests to provide it to test runner (JUnit/TestNG).
At second, test needs to open tested page by Selenium (Drone).
It would be necessary to run tests by several particular browser brands (HtmlUnit, Firefox, IE, ...).
QUnit tests are traditionally at once - you open the page and all tests are ran.
Then runner needs to collect all the results OR it can force QUnit to run only one test at time.
[1] http://docs.jquery.com/Qunit
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] Created: (ARQ-563) @ArquillianResource in TestNG based tests causes test body not to be evaluated
by Karel Piwko (JIRA)
@ArquillianResource in TestNG based tests causes test body not to be evaluated
------------------------------------------------------------------------------
Key: ARQ-563
URL: https://issues.jboss.org/browse/ARQ-563
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Protocol SPIs and Implementation
Affects Versions: 1.0.0.CR4
Environment: Surefire 2.7.2, 2.9
TestNG 5.14.6, 5.14.9
AS 7.0.1 web
Reporter: Karel Piwko
Priority: Blocker
Suppose following test case:
{code}
public class LowercaseConverterTest extends Arquillian {
@Inject
private LowercaseConverter lowercaseConverter;
@Deployment
public static JavaArchive createTestArchive() {
return ShrinkWrap
.create(JavaArchive.class, "test.jar")
.addClasses(LowercaseConverter.class)
.addAsManifestResource(EmptyAsset.INSTANCE,
ArchivePaths.create("beans.xml"));
}
@Test
public void testConvertToLowercase() {
Assert.assertEquals("martin",
lowercaseConverter.convertToLowercase("Martin"));
}
}
{code}
However, if @ArquillianResource is used for a field injection, such as:
{code}
@ArquillianResource URL field;
{code}
than test body is no longer executed and *all tests are reported as passed* even an obvious failure like:
{code}
@Test
public void testConvertToLowercase() {
Assert.fail();
Assert.assertEquals("karel",
lowercaseConverter.convertToLowercase("Martin"));
}
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months