[JBoss JIRA] (ARQ-1687) Support setting process basedir
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1687:
--------------------------------
Summary: Support setting process basedir
Key: ARQ-1687
URL: https://issues.jboss.org/browse/ARQ-1687
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Spacelift
Affects Versions: spacelift_1.0.0.Alpha1
Reporter: Karel Piwko
Is is not possible to setup a home directory of spawned/executed process.
--
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
12 years
[JBoss JIRA] (ARQ-1686) Make testRunnerAdapter.test(...) more flexible
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1686?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1686:
-------------------------------
Fix Version/s: 2.0.0.Beta1
> Make testRunnerAdapter.test(...) more flexible
> ----------------------------------------------
>
> Key: ARQ-1686
> URL: https://issues.jboss.org/browse/ARQ-1686
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Test Protocol SPIs and Implementation
> Affects Versions: 1.1.3.Final
> Reporter: Tair Sabirgaliev
> Priority: Minor
> Fix For: 2.0.0.Beta1
>
>
> On client side a test case in a test class is represented by java.lang.reflect.Method. This makes impossible to easily integrate frameworks like ScalaTest, where a test case is not necessarily a class method.
> As a solution, it would be great to:
> (a) relax the test representation to just a String identifier, and leave the interpretation to relevant TestRunner implementation (which is already the case?)
> (b) be able to pass optional params at testRunnerAdapter.test(...), so that they are transmitted to container side as additional hints. Map<String,String> would be good enough.
--
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
12 years
[JBoss JIRA] (ARQ-1686) Make testRunnerAdapter.test(...) more flexible
by Tair Sabirgaliev (JIRA)
Tair Sabirgaliev created ARQ-1686:
-------------------------------------
Summary: Make testRunnerAdapter.test(...) more flexible
Key: ARQ-1686
URL: https://issues.jboss.org/browse/ARQ-1686
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Test Protocol SPIs and Implementation
Affects Versions: 1.1.3.Final
Reporter: Tair Sabirgaliev
Priority: Minor
On client side a test case in a test class is represented by java.lang.reflect.Method. This makes impossible to easily integrate frameworks like ScalaTest, where a test case is not necessarily a class method.
As a solution, it would be great to:
(a) relax the test representation to just a String identifier, and leave the interpretation to relevant TestRunner implementation (which is already the case?)
(b) be able to pass optional params at testRunnerAdapter.test(...), so that they are transmitted to container side as additional hints. Map<String,String> would be good enough.
--
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
12 years
[JBoss JIRA] (ARQ-812) Split DBUnit and Core implemenation
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-812?page=com.atlassian.jira.plugin.sy... ]
Bartosz Majsak updated ARQ-812:
-------------------------------
Description: Split Core and DBUnit modules in order to prepare the ground for extension model which will open integration with other tools such as Liquibase. (was: Introduce SPIs for core functionalities.)
> Split DBUnit and Core implemenation
> -----------------------------------
>
> Key: ARQ-812
> URL: https://issues.jboss.org/browse/ARQ-812
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Reporter: Bartosz Majsak
> Assignee: Bartosz Majsak
>
> Split Core and DBUnit modules in order to prepare the ground for extension model which will open integration with other tools such as Liquibase.
--
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
12 years
[JBoss JIRA] (ARQ-1009) ClassNotFoundException when using CLEAN_INSERT
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1009?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak resolved ARQ-1009.
---------------------------------
Resolution: Won't Fix
As already mentioned by [~brzhk] configuration is case sensitive. To be precise it is 1-1 mapping between the fields exposed by configuration objects to property names in the XML file. I have lately introduced warning message which is prompted when there is no match with the corresponding configuration. Pushed upstream [@8a98920|https://github.com/arquillian/arquillian-extension-persistence/commit/8a989200d2128e8feee42d6894ad8a6754740180].
> ClassNotFoundException when using CLEAN_INSERT
> ----------------------------------------------
>
> Key: ARQ-1009
> URL: https://issues.jboss.org/browse/ARQ-1009
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha4
> Environment: Windows 7, Java 1.6.0_31
> Reporter: Karsten Ohme
> Assignee: Bartosz Majsak
> Fix For: persistence_1.0.0.next
>
>
> I set in arquillian.xml the configuration property:
> <property name="dataSeedStrategy">CLEAN_INSERT</property>
> When starting the test I get a ClassNotFoundException in ConfigurationTypeConverter in line 182:
> Object instance = Class.forName(value).newInstance();
--
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
12 years