[JBoss JIRA] (ARQ-1919) Android SDK with no images fails while testing on physical device
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1919?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1919:
-----------------------------------
Fix Version/s: droidium_1.0.0.Final
(was: droidium_1.0.0.Beta1)
> Android SDK with no images fails while testing on physical device
> -----------------------------------------------------------------
>
> Key: ARQ-1919
> URL: https://issues.jboss.org/browse/ARQ-1919
> Project: Arquillian
> Issue Type: Bug
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha6
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Fix For: droidium_1.0.0.Final
>
>
> When you want to test on a physical device, there is not any need to have system images installed. This issue is rarely hit in practice, however when using Droidium in CI environment, testing on physical device and not requiring system images to be even installed is major performance improvement.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite)
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.sy... ]
Aslak Knutsen commented on ARQ-567:
-----------------------------------
The work has started! :)
General impl discussion here: http://discuss.arquillian.org/t/arquillian-core-suite-subsuite-support/162
And user API disussion here. http://discuss.arquillian.org/t/arquillian-core-suite-subsuite-how-to-def...
> Supporting Test Suites (@ArquillianSuite)
> -----------------------------------------
>
> Key: ARQ-567
> URL: https://issues.jboss.org/browse/ARQ-567
> Project: Arquillian
> Issue Type: Feature Request
> Reporter: Mousavi Jahan Abadi S. M.
> Assignee: Aslak Knutsen
> Fix For: 1.1.8.Final
>
>
> Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like:
> @RunWith(ArquillianSuite.class)
> @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } )
> public class AllTests{
> @Deployment
> public static JavaArchive createTestArchive(){
> return ShrinkWrap.create(JavaArchive.class,"test.jar");
> }
> }
> The advantages of above approach for users of Arquillian framework are:
> - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users).
> - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions.
> The advantage of above approach for framework itself is:
> - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months