[JBoss JIRA] (ARQ-1480) After/Before methods are always fired on both container/in client
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1480?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak resolved ARQ-1480.
---------------------------------
Resolution: Done
Thx!
> After/Before methods are always fired on both container/in client
> -----------------------------------------------------------------
>
> Key: ARQ-1480
> URL: https://issues.jboss.org/browse/ARQ-1480
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Spock TestRunner
> Affects Versions: spock_1.0.0.Beta1
> Reporter: Karel Piwko
> Assignee: Aslak Knutsen
> Priority: Critical
> Fix For: spock_1.0.0.next
>
>
> Current behavior of setup() methods does not follow other Arquillian test runners. Namely, the problem is in method being always executed in both environments, making following call impossible:
> {code}
> @Inject Foo foo;
> def setup() {
> assert foo != null
> }
> {code}
--
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, 6 months
[JBoss JIRA] (ARQ-1481) Remove redundancy of both ArquillianSputnik and ArquillianSpecification
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1481?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak resolved ARQ-1481.
---------------------------------
Fix Version/s: spock_1.0.0.next
Resolution: Done
Even though it's some sort of API change in BETA phase, it fixes quite important problem we were not really aware of before (as we probably had poor tests ;)). Therefore I think it's not really that outstanding problem to introduce it in Beta 2 version.
> Remove redundancy of both ArquillianSputnik and ArquillianSpecification
> -----------------------------------------------------------------------
>
> Key: ARQ-1481
> URL: https://issues.jboss.org/browse/ARQ-1481
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Spock TestRunner
> Affects Versions: spock_1.0.0.Beta1
> Reporter: Karel Piwko
> Assignee: Karel Piwko
> Fix For: spock_1.0.0.next
>
>
> It should be possible to remove @ArquillianSpecification, as it is redundant to @RunWith call.
> {code}
> @ArquillianSpecification
> @RunWith(ArquillianSputik)
> {code}
--
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, 6 months
[JBoss JIRA] (ARQ-1529) Enhance error reporting when user transaction cannot be found
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1529?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak updated ARQ-1529:
--------------------------------
Summary: Enhance error reporting when user transaction cannot be found (was: Enhance error reporting)
> Enhance error reporting when user transaction cannot be found
> -------------------------------------------------------------
>
> Key: ARQ-1529
> URL: https://issues.jboss.org/browse/ARQ-1529
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Transaction
> Affects Versions: transaction_1.0.0.Alpha3
> Reporter: Bartosz Majsak
> Assignee: Bartosz Majsak
> Priority: Minor
> Fix For: transaction_1.0.0.next
>
>
> When extension failed to load transaction (in particular JTA SPI), it does not include which JNDI name has been used, leaving user with unclear cause of the problem.
--
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, 6 months
[JBoss JIRA] (ARQ-1529) Enhance error reporting
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-1529:
-----------------------------------
Summary: Enhance error reporting
Key: ARQ-1529
URL: https://issues.jboss.org/browse/ARQ-1529
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Transaction
Affects Versions: transaction_1.0.0.Alpha3
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Priority: Minor
Fix For: transaction_1.0.0.next
When extension failed to load transaction (in particular JTA SPI), it does not include which JNDI name has been used, leaving user with unclear cause of the problem.
--
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, 6 months