[
https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.s...
]
Thomas Küstermann commented on ARQ-1779:
----------------------------------------
I activated {{arquillian.debug}} and observed a bunch of {{(E) ScriptExecutionException}}
entries. And indeed, there were errors in the scripts to execute (missed to set
{{sqlDialect}} to oracle). So the problem is not that the tests aren't executed. The
issue is that the exceptions don't fail the tests. The exceptions are not reported,
neither in Eclipse nor on the command line (using maven).
Tests are not executed using combinations of @ApplyScriptBefore /
@ApplyScriptAfter
-----------------------------------------------------------------------------------
Key: ARQ-1779
URL:
https://issues.jboss.org/browse/ARQ-1779
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha7
Reporter: Thomas Küstermann
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
Forum reference:
https://community.jboss.org/message/874117
The following test case succeeds (green bar) although it should fail:
{code:java}
@RunWith(Arquillian.class)
@DataSource("java:oracleDS")
@Cleanup(phase=TestExecutionPhase.NONE)
@ApplyScriptBefore("deploy-db-functionality.sql")
@ApplyScriptAfter("undeploy-db-functionality.sql")
public class PersistenceIT {
// @Deployment ...
@Test
@ApplyScriptBefore("trigger-db-functionality.sql")
public void shouldFail() {
Assert.fail("should fail, but doesn't");
}
}
{code}
Removing class level annotations does not work either:
{code:java}
@Test
@ApplyScriptBefore({ "deploy-db-functionality.sql",
"trigger-db-functionality.sql" })
@ApplyScriptAfter("undeploy-db-functionality.sql")
public void shouldFail() { ... }
{code}
What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation
per test, each with only one script to execute.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)