[JBoss JIRA] (ARQ-945) Extract Spring Integration out of Spring Deployer
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-945:
---------------------------------
Summary: Extract Spring Integration out of Spring Deployer
Key: ARQ-945
URL: https://issues.jboss.org/browse/ARQ-945
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Spring Integration
Affects Versions: spring_1.0.0.Alpha1
Reporter: Aslak Knutsen
Assignee: Marius Bogoevici
Fix For: spring_1.0.0.next
In Alpha1 the Service Deployer and the Service Integration is one module, these should be two separate where the Service Integration part can be reused between the Service Deployer and the upcoming Service Container
Service Integration = Enrichers
Service Deployer = Related to moving Spring to a Container (packaging)
--
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
12 years, 5 months
[JBoss JIRA] (ARQRUSH-26) Support detection of changes in cases and tests (removals, additions, modifications)
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQRUSH-26:
---------------------------------
Summary: Support detection of changes in cases and tests (removals, additions, modifications)
Key: ARQRUSH-26
URL: https://issues.jboss.org/browse/ARQRUSH-26
Project: Arquillian RushEye
Issue Type: Feature Request
Components: Core, Manager
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
{quote}
T 1341996997 31<lfryc>30 (5) problem of changes in test suite
T 1341997028 31<lfryc>30 basically what to do when "screenshots1" and "screenshots2" differs
T 1341997042 31<lfryc>30 in case of:
T 1341997047 31<lfryc>30 a) test additions
T 1341997050 31<lfryc>30 b) test removals
T 1341997055 31<lfryc>30 c) test modifications
T 1341997087 31<lfryc>30 the Manager should inteligently show the test case with matching images
T 1341997100 31<lfryc>30 and even allow context-menu resolution
T 1341997163 31<lfryc>30 we are currently investigating what's the stability of test suite (if the list of images doesn't differ between runs)
T 1341997163 18<fafnir88> if there is no corresponding image for test, this big image warning will be shown
T 1341997204 31<lfryc>30 yeah, this would need to be more smart..
T 1341997220 31<lfryc>30 let's see this case, you get those tests (images):
T 1341997248 31<lfryc>30 00-open
T 1341997248 31<lfryc>30 01-click
T 1341997248 31<lfryc>30 02-click
T 1341997248 31<lfryc>30 03-type
T 1341997248 31<lfryc>30 04-click
T 1341997248 31<lfryc>30 05-click
T 1341997274 31<lfryc>30 but then you get other just those:
T 1341997279 31<lfryc>30 00-open
T 1341997283 31<lfryc>30 01-click
T 1341997285 31<lfryc>30 03-type
T 1341997304 31<lfryc>30 those images identifies all changes during the automated browser test
T 1341997316 31<lfryc>30 then you have problem
T 1341997321 31<lfryc>30 (sorry 02-type)
T 1341997337 31<lfryc>30 the Manager could fallback to heuristics
T 1341997359 31<lfryc>30 and in case of the images does not match in suite and samples..
T 1341997378 18<fafnir88> so, you want to have a test pruning for missing cases?
T 1341997380 31<lfryc>30 it can offer alternative mode, when it could try determine what happened
T 1341997390 18<fafnir88> *test tree
T 1341997394 31<lfryc>30 yep
T 1341997402 31<lfryc>30 it should show something like:
T 1341997407 31<lfryc>30 OK 00-open
T 1341997412 31<lfryc>30 OK 01-click
T 1341997434 31<lfryc>30 02-click (missing sample)
T 1341997445 31<lfryc>30 02-type (missing pattern)
{quote}
--
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
12 years, 5 months
[JBoss JIRA] (ARQ-1020) Arquillian doesnt set ThreadLocalClassLoader to the @Deployment
by Mark Struberg (JIRA)
Mark Struberg created ARQ-1020:
----------------------------------
Summary: Arquillian doesnt set ThreadLocalClassLoader to the @Deployment
Key: ARQ-1020
URL: https://issues.jboss.org/browse/ARQ-1020
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Base Implementation
Affects Versions: 1.0.1.Final, 1.0.0.Final
Reporter: Mark Struberg
Arquillian doesn't set the ThreadLocalClassLoader to the @Deployment archive. This leads to getResources() calls not finding any deployed resources.
The following code fragment from Apache DeltaSpike should make clear what I mean:
{code}
@RunWith(Arquillian.class)
public class PropertyConfigSourceTest
{
@Deployment
public static WebArchive deploy()
{
return ShrinkWrap.create(WebArchive.class, "beanProvider.war")
.addAsLibraries(ArchiveUtils.getDeltaSpikeCoreArchive())
.addAsResource(new StringAsset("prop=value"), "myconfig.properties")
.addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml");
}
@Test
public void testCustomPropertyConfigSources() throws Exception
{
Enumeration<URL> resources = Thread.currentThread().getContextClassLoader().getResources("myconfig.properties");
// kawumms...
Assert.assertTrue(resources.hasMoreElements());
}
}
{code}
--
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
12 years, 5 months