[JBoss JIRA] (ARQ-841) Should not scan for classes in Archive if it contains no beans.xml
by Karim de Fombelle (JIRA)
[ https://issues.jboss.org/browse/ARQ-841?page=com.atlassian.jira.plugin.sy... ]
Karim de Fombelle commented on ARQ-841:
---------------------------------------
Similar issue observed with Arquillian 1.0.3.Final / arquillian-weld-se-embedded-1.1 1.0.0.CR5 / weld-core 1.1.10.Final / Shrinkwrap 2.0.0-alpha-1
Test case below:
{code}
@RunWith(Arquillian.class)
public class ArquillianBeanXmlTest {
@Inject
private TestBean testBean;
@Deployment
public static JavaArchive createDeployment() {
return ShrinkWrap.create(JavaArchive.class)
.addClass(TestBean.class);
//.addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml");//sounds useless
}
//test is successful whereas it is expected to fail
@Test
public void testBeanInjected() {
assertNotNull(testBean);
}
}
{code}
And bean:
{code}
package org.jboss.arquillian.junit;
public class TestBean {
}
{code}
The pom is attached.
> Should not scan for classes in Archive if it contains no beans.xml
> ------------------------------------------------------------------
>
> Key: ARQ-841
> URL: https://issues.jboss.org/browse/ARQ-841
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Weld Containers
> Affects Versions: weld_1.0.0.CR3
> Reporter: Aslak Knutsen
> Labels: starter
> Fix For: weld_1.1.0.next
>
>
> A deployment with no beans.xml should not result in Beans being registered in the Weld Container.
--
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
11 years, 12 months
[JBoss JIRA] (ARQ-1027) Support CommandService Protocol SPI via Warp Protocol
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1027?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1027:
----------------------------
Priority: Critical (was: Major)
> Support CommandService Protocol SPI via Warp Protocol
> -----------------------------------------------------
>
> Key: ARQ-1027
> URL: https://issues.jboss.org/browse/ARQ-1027
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha1
> Reporter: Curtis McMillen
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Beta1
>
> Attachments: stacktrace.txt
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> It seems there is a problem with running Warp tests if arquillian-jacoco is on the classpath.
> When WarpFilter fires the AfterSuite event, the writeCoverageData observer in arquillian-jacoco is executing which ultimately leads to a NPE coming from servlet protocol. The full stacktrace is attached.
> You can reproduce by simply adding the following dependencies to the pom for warp in arquillian-showcase and then running the BasicJSFUnitTestCase.
> {code:xml}
> <dependency>
> <groupId>org.jboss.arquillian.extension</groupId>
> <artifactId>arquillian-jacoco</artifactId>
> <version>1.0.0.Alpha3</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jacoco</groupId>
> <artifactId>org.jacoco.core</artifactId>
> <version>0.5.7.201204190339</version>
> <scope>test</scope>
> </dependency>
> {code}
> Removing these dependencies isn't really an option because I have other arquillian tests not using Warp that I want code coverage on. I tried using alternative annotated with @Specializes thinking I could basically disable the observer in arquillian-jacoco simply by including a different beans.xml in the deployment of my Warp tests. This however fails with "WELD-000047 Specializing bean must extend another bean" which I'm thinking is due to https://issues.jboss.org/browse/WELD-1113.
> Any ideas for getting this to work?
--
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
11 years, 12 months
[JBoss JIRA] (ARQGRA-260) @InSequence with one or more test numbers i.e. @InSequence(1, 5, 9)
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-260?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-260:
-----------------------------------
Hey Emmanouil, I believe this is better to do with Java methods - the result will be actually more readable.
> @InSequence with one or more test numbers i.e. @InSequence(1,5,9)
> -----------------------------------------------------------------
>
> Key: ARQGRA-260
> URL: https://issues.jboss.org/browse/ARQGRA-260
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: junit, unit-test
> Affects Versions: 2.0.0.Beta1
> Reporter: Emmanouil Vlastos
> Priority: Minor
> Fix For: 2.0.0.Beta1
>
>
> The idea was to be able to execute the same test in different positions in the JUnit file.
> For example
> @Test
> @InSequence(1,5,9)
> public void resetUI(){
> //do something to reset some values
> }
> @Test
> @InSequence(2,6){
> public void initializeUI(){
> //do something to initialize some values
> }
> @Test
> @InSequence(3)
> public void test3(){}
> @Test
> @InSequence(4)
> public void test4(){}
> @Test
> @InSequence(7)
> public void test7(){}
> @Test
> @InSequence(8)
> public void test8(){}
--
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] (ARQGRA-260) @InSequence with one or more test numbers i.e. @InSequence(1, 5, 9)
by Emmanouil Vlastos (JIRA)
Emmanouil Vlastos created ARQGRA-260:
----------------------------------------
Summary: @InSequence with one or more test numbers i.e. @InSequence(1,5,9)
Key: ARQGRA-260
URL: https://issues.jboss.org/browse/ARQGRA-260
Project: Arquillian Graphene
Issue Type: Feature Request
Components: junit, unit-test
Affects Versions: 2.0.0.Beta1
Reporter: Emmanouil Vlastos
Priority: Minor
Fix For: 2.0.0.Beta1
The idea was to be able to execute the same test in different positions in the JUnit file.
For example
@Test
@InSequence(1,5,9)
public void resetUI(){
//do something to reset some values
}
@Test
@InSequence(2,6){
public void initializeUI(){
//do something to initialize some values
}
@Test
@InSequence(3)
public void test3(){}
@Test
@InSequence(4)
public void test4(){}
@Test
@InSequence(7)
public void test7(){}
@Test
@InSequence(8)
public void test8(){}
--
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