[JBoss JIRA] (ARQ-1902) Provide SPI for conditional execution of test methods
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1902?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1902:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/arquillian/arquillian-core/pull/76
> Provide SPI for conditional execution of test methods
> -----------------------------------------------------
>
> Key: ARQ-1902
> URL: https://issues.jboss.org/browse/ARQ-1902
> Project: Arquillian
> Issue Type: Feature Request
> Components: Base Implementation
> Affects Versions: 1.1.5.Final
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
>
> [~aslak]
> Let me explain.
> We want to do this:
> {code}
> @RunWith(Arquillian.class)
> @RunAsClient
> public class TestCase
> {
> @Test
> @Jira("ARQ-1")
> public void test() {
> // this test method will be executed
> // because Aslak created EJB Jar archive (JIRA status = done)
> }
> @Test
> @Jira("ARQ-xyz")
> public void test() {
> // this methods will NOT be executed (will be skipped)
> // becase lets say that its status is "open / unresolved"
> }
> }
> {code}
> While looking into the code, it seems these classes are most important (1), (2).
> So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
> In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
> Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider and whole JIRA api on class path in my custom extension.
> (1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
> (2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ARQ-1902) Provide SPI for conditional execution of test methods
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1902?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1902:
--------------------------------------
Assignee: Stefan Miklosovic
> Provide SPI for conditional execution of test methods
> -----------------------------------------------------
>
> Key: ARQ-1902
> URL: https://issues.jboss.org/browse/ARQ-1902
> Project: Arquillian
> Issue Type: Feature Request
> Components: Base Implementation
> Affects Versions: 1.1.5.Final
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
>
> [~aslak]
> Let me explain.
> We want to do this:
> {code}
> @RunWith(Arquillian.class)
> @RunAsClient
> public class TestCase
> {
> @Test
> @Jira("ARQ-1")
> public void test() {
> // this test method will be executed
> // because Aslak created EJB Jar archive (JIRA status = done)
> }
> @Test
> @Jira("ARQ-xyz")
> public void test() {
> // this methods will NOT be executed (will be skipped)
> // becase lets say that its status is "open / unresolved"
> }
> }
> {code}
> While looking into the code, it seems these classes are most important (1), (2).
> So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
> In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
> Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider and whole JIRA api on class path in my custom extension.
> (1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
> (2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ARQ-1902) Provide SPI for conditional execution of test methods
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1902?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on ARQ-1902:
------------------------------------
With 'skip in report' I'm referring to the normal JUnit outcome (regardless of what Arq Reporter does)..
You can't skip 'the whole before/test/after' phase. You'll have to skip them individually.
> Provide SPI for conditional execution of test methods
> -----------------------------------------------------
>
> Key: ARQ-1902
> URL: https://issues.jboss.org/browse/ARQ-1902
> Project: Arquillian
> Issue Type: Feature Request
> Components: Base Implementation
> Affects Versions: 1.1.5.Final
> Reporter: Stefan Miklosovic
>
> [~aslak]
> Let me explain.
> We want to do this:
> {code}
> @RunWith(Arquillian.class)
> @RunAsClient
> public class TestCase
> {
> @Test
> @Jira("ARQ-1")
> public void test() {
> // this test method will be executed
> // because Aslak created EJB Jar archive (JIRA status = done)
> }
> @Test
> @Jira("ARQ-xyz")
> public void test() {
> // this methods will NOT be executed (will be skipped)
> // becase lets say that its status is "open / unresolved"
> }
> }
> {code}
> While looking into the code, it seems these classes are most important (1), (2).
> So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
> In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
> Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider and whole JIRA api on class path in my custom extension.
> (1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
> (2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ARQ-1902) Provide SPI for conditional execution of test methods
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1902?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic commented on ARQ-1902:
----------------------------------------
Good catch, I guess that excluding Before and After from execution would be necessary as well. I see reporting as a marginal problem, I do not want to fire property events in Core. Core has to be clean of all extensions / apis. However, my "jira" extension could fire them on its own and mark it as skipped. I need to look at this more closely. I do not know right now how to skip whole before / test / after lifecycle.
> Provide SPI for conditional execution of test methods
> -----------------------------------------------------
>
> Key: ARQ-1902
> URL: https://issues.jboss.org/browse/ARQ-1902
> Project: Arquillian
> Issue Type: Feature Request
> Components: Base Implementation
> Affects Versions: 1.1.5.Final
> Reporter: Stefan Miklosovic
>
> [~aslak]
> Let me explain.
> We want to do this:
> {code}
> @RunWith(Arquillian.class)
> @RunAsClient
> public class TestCase
> {
> @Test
> @Jira("ARQ-1")
> public void test() {
> // this test method will be executed
> // because Aslak created EJB Jar archive (JIRA status = done)
> }
> @Test
> @Jira("ARQ-xyz")
> public void test() {
> // this methods will NOT be executed (will be skipped)
> // becase lets say that its status is "open / unresolved"
> }
> }
> {code}
> While looking into the code, it seems these classes are most important (1), (2).
> So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
> In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
> Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider and whole JIRA api on class path in my custom extension.
> (1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
> (2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ARQ-1902) Provide SPI for conditional execution of test methods
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1902?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on ARQ-1902:
------------------------------------
I assume you would want to skip the whole Before|Test|After phase? Not just Test?
Do you want it 'marked' as Skipped in report?
> Provide SPI for conditional execution of test methods
> -----------------------------------------------------
>
> Key: ARQ-1902
> URL: https://issues.jboss.org/browse/ARQ-1902
> Project: Arquillian
> Issue Type: Feature Request
> Components: Base Implementation
> Affects Versions: 1.1.5.Final
> Reporter: Stefan Miklosovic
>
> [~aslak]
> Let me explain.
> We want to do this:
> {code}
> @RunWith(Arquillian.class)
> @RunAsClient
> public class TestCase
> {
> @Test
> @Jira("ARQ-1")
> public void test() {
> // this test method will be executed
> // because Aslak created EJB Jar archive (JIRA status = done)
> }
> @Test
> @Jira("ARQ-xyz")
> public void test() {
> // this methods will NOT be executed (will be skipped)
> // becase lets say that its status is "open / unresolved"
> }
> }
> {code}
> While looking into the code, it seems these classes are most important (1), (2).
> So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
> In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
> Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider and whole JIRA api on class path in my custom extension.
> (1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
> (2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ARQ-1902) Provide SPI for conditional execution of test methods
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1902?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1902:
-----------------------------------
Description:
[~aslak]
Let me explain.
We want to do this:
{code}
@RunWith(Arquillian.class)
@RunAsClient
public class TestCase
{
@Test
@Jira("ARQ-1")
public void test() {
// this test method will be executed
// because Aslak created EJB Jar archive (JIRA status = done)
}
@Test
@Jira("ARQ-xyz")
public void test() {
// this methods will NOT be executed (will be skipped)
// becase lets say that its status is "open / unresolved"
}
}
{code}
While looking into the code, it seems these classes are most important (1), (2).
So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider and whole JIRA api on class path in my custom extension.
(1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
(2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
was:
[~aslak]
Let me explain.
We want to do this:
{code}
@RunWith(Arquillian.class)
@RunAsClient
public class TestCase
{
@Test
@Jira("ARQ-1")
public void test() {
// this test method will be executed
// because Aslak created EJB Jar archive (JIRA status = done)
}
@Test
@Jira("ARQ-xyz")
public void test() {
// this methods will NOT be executed (will be skipped)
// becase lets say that its status is "open / unresolved"
}
}
{code}
While looking into the code, it seems these classes are most important (1), (2).
So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider on class path in custom extension.
(1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
(2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
> Provide SPI for conditional execution of test methods
> -----------------------------------------------------
>
> Key: ARQ-1902
> URL: https://issues.jboss.org/browse/ARQ-1902
> Project: Arquillian
> Issue Type: Feature Request
> Components: Base Implementation
> Affects Versions: 1.1.5.Final
> Reporter: Stefan Miklosovic
>
> [~aslak]
> Let me explain.
> We want to do this:
> {code}
> @RunWith(Arquillian.class)
> @RunAsClient
> public class TestCase
> {
> @Test
> @Jira("ARQ-1")
> public void test() {
> // this test method will be executed
> // because Aslak created EJB Jar archive (JIRA status = done)
> }
> @Test
> @Jira("ARQ-xyz")
> public void test() {
> // this methods will NOT be executed (will be skipped)
> // becase lets say that its status is "open / unresolved"
> }
> }
> {code}
> While looking into the code, it seems these classes are most important (1), (2).
> So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
> In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
> Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider and whole JIRA api on class path in my custom extension.
> (1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
> (2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ARQ-1902) Provide SPI for conditional execution of test methods
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1902?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1902:
-----------------------------------
Description:
[~aslak]
Let me explain.
We want to do this:
{code}
@RunWith(Arquillian.class)
@RunAsClient
public class TestCase
{
@Test
@Jira("ARQ-1")
public void test() {
// this test method will be executed
// because Aslak created EJB Jar archive (JIRA status = done)
}
@Test
@Jira("ARQ-xyz")
public void test() {
// this methods will NOT be executed (will be skipped)
// becase lets say that its status is "open / unresolved"
}
}
{code}
While looking into the code, it seems these classes are most important (1), (2).
So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider on class path in custom extension.
(1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
(2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
was:
[~aslak]
Let me explain.
We want to do this:
{code}
@RunWith(Arquillian.class)
@RunAsClient
public class TestCase
{
@Test
@Jira("ARQ-1")
public void test() {
// this test method will be executed
// because Aslak created EJB Jar archive (JIRA status = done)
}
@Test
@Jira("ARQ-xyz")
public void test() {
// this methods will NOT be executed (will be skipped)
// becase lets say that its status is "open / unresolved"
}
}
{/code}
While looking into the code, it seems these classes are most important (1), (2).
So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider on class path in custom extension.
(1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
(2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
> Provide SPI for conditional execution of test methods
> -----------------------------------------------------
>
> Key: ARQ-1902
> URL: https://issues.jboss.org/browse/ARQ-1902
> Project: Arquillian
> Issue Type: Feature Request
> Components: Base Implementation
> Affects Versions: 1.1.5.Final
> Reporter: Stefan Miklosovic
>
> [~aslak]
> Let me explain.
> We want to do this:
> {code}
> @RunWith(Arquillian.class)
> @RunAsClient
> public class TestCase
> {
> @Test
> @Jira("ARQ-1")
> public void test() {
> // this test method will be executed
> // because Aslak created EJB Jar archive (JIRA status = done)
> }
> @Test
> @Jira("ARQ-xyz")
> public void test() {
> // this methods will NOT be executed (will be skipped)
> // becase lets say that its status is "open / unresolved"
> }
> }
> {code}
> While looking into the code, it seems these classes are most important (1), (2).
> So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
> In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
> Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider on class path in custom extension.
> (1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
> (2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ARQ-1902) Provide SPI for conditional execution of test methods
by Stefan Miklosovic (JIRA)
Stefan Miklosovic created ARQ-1902:
--------------------------------------
Summary: Provide SPI for conditional execution of test methods
Key: ARQ-1902
URL: https://issues.jboss.org/browse/ARQ-1902
Project: Arquillian
Issue Type: Feature Request
Components: Base Implementation
Affects Versions: 1.1.5.Final
Reporter: Stefan Miklosovic
[~aslak]
Let me explain.
We want to do this:
{code}
@RunWith(Arquillian.class)
@RunAsClient
public class TestCase
{
@Test
@Jira("ARQ-1")
public void test() {
// this test method will be executed
// because Aslak created EJB Jar archive (JIRA status = done)
}
@Test
@Jira("ARQ-xyz")
public void test() {
// this methods will NOT be executed (will be skipped)
// becase lets say that its status is "open / unresolved"
}
}
{/code}
While looking into the code, it seems these classes are most important (1), (2).
So my initial approach was that I wanted to kind of "hook" into that execution and dynamically resolve if that test method is going to be executed or not but I am failing to do so since there is not any SPI which would load my test-method-execution-decider which would tell if that method is going to be executed or if it will be marked as skipped.
In that decider, I would dynamically log in to jira and read if that jira is resolved or nor and behave accordingly.
Is there any will to push this to upstream once implemented? Default decider would indeed execute that method every time and I would just put my own decider on class path in custom extension.
(1) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
(2) https://github.com/arquillian/arquillian-core/blob/master/container/test-...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months