[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by Amanda Han (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
Amanda Han updated DROOLS-3674:
-------------------------------
Attachment: Error reporting after test run-different kinds.png
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by Amanda Han (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
Amanda Han updated DROOLS-3674:
-------------------------------
Attachment: (was: Error reporting after test run-different kinds2.png)
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by Amanda Han (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
Amanda Han updated DROOLS-3674:
-------------------------------
Attachment: (was: Error reporting after test run-different kinds.png)
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by Amanda Han (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
Amanda Han updated DROOLS-3674:
-------------------------------
Comment: was deleted
(was: Hello [~danielezonca] there are two candidated plans for error reporting after run.
The first one provides options"replace" or "keep" to go further steps to deal with error, or you can just have a look about the problem instruction and "cancel" to close the popover. !Error reporting after test run-different kinds.png|thumbnail!
Another one is made for complicated problems that may need with more words to explain. We show the core bug in a short sentence, if users want to know the details, click "show more details" to know the detailed problem.
!Error reporting after test run-different kinds2.png|thumbnail!
WDYT??:D)
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11778) Missing ejb3 transformer tests
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11778?page=com.atlassian.jira.plugin... ]
Cheng Fang reassigned WFLY-11778:
---------------------------------
Assignee: Cheng Fang
> Missing ejb3 transformer tests
> ------------------------------
>
> Key: WFLY-11778
> URL: https://issues.jboss.org/browse/WFLY-11778
> Project: WildFly
> Issue Type: Task
> Components: EJB
> Affects Versions: 16.0.0.Beta1
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
>
> Per Kabir's email to wildfly-dev list, need to add transformer tests for ejb3 subsystem. For details see http://lists.jboss.org/pipermail/wildfly-dev/2019-February/006772.html
> {quote}
> TL;DR: It looks like we may be missing transformer tests in the following
> subsystems: ejb3, infinispan, jca, logging, undertow. I've not dug in
> beyond that.
> Full:
> We have been using ModelTestControllerVersion.EAP_7_2_0_TEMP (containing
> WF14) for transformer testing until EAP 7.2.0 was released. [1] renames
> this to be EAP_7_2_0 and points to EAP 7.2.0.
> In addition I have some WIP to update the full mixed domain and subsystem
> tests to do the same. When doing this I noticed that the only subsystem
> that had transformer tests referencing EAP_7_2_0_TEMP was modcluster. I
> knew messaging-activemq had some changes, which Emmanuel is looking at.
> I've run the model comparison tool against master/7.2.0: and see changes
> which might be significant:
> ====== Resource root address: ["subsystem" => "ejb3"] - Current version:
> 0.0.0; legacy version: 5.0.0 =======
> --- Problems for relative address to root ["passivation-store" => "*"]:
> Different 'access-type' for attribute 'bean-cache'. Current: "read-write";
> legacy: "read-only"
> Different 'access-type' for attribute 'cache-container'. Current:
> "read-write"; legacy: "read-only"
> ...
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11778) Missing ejb3 transformer tests
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11778?page=com.atlassian.jira.plugin... ]
Cheng Fang updated WFLY-11778:
------------------------------
Description:
Per Kabir's email to wildfly-dev list, need to add transformer tests for ejb3 subsystem. For details see http://lists.jboss.org/pipermail/wildfly-dev/2019-February/006772.html
{quote}
TL;DR: It looks like we may be missing transformer tests in the following
subsystems: ejb3, infinispan, jca, logging, undertow. I've not dug in
beyond that.
Full:
We have been using ModelTestControllerVersion.EAP_7_2_0_TEMP (containing
WF14) for transformer testing until EAP 7.2.0 was released. [1] renames
this to be EAP_7_2_0 and points to EAP 7.2.0.
In addition I have some WIP to update the full mixed domain and subsystem
tests to do the same. When doing this I noticed that the only subsystem
that had transformer tests referencing EAP_7_2_0_TEMP was modcluster. I
knew messaging-activemq had some changes, which Emmanuel is looking at.
I've run the model comparison tool against master/7.2.0: and see changes
which might be significant:
====== Resource root address: ["subsystem" => "ejb3"] - Current version:
0.0.0; legacy version: 5.0.0 =======
--- Problems for relative address to root ["passivation-store" => "*"]:
Different 'access-type' for attribute 'bean-cache'. Current: "read-write";
legacy: "read-only"
Different 'access-type' for attribute 'cache-container'. Current:
"read-write"; legacy: "read-only"
...
{quote}
was:Per Kabir's email to wildfly-dev list, need to add transformer tests for ejb3 subsystem. For details see http://lists.jboss.org/pipermail/wildfly-dev/2019-February/006772.html
> Missing ejb3 transformer tests
> ------------------------------
>
> Key: WFLY-11778
> URL: https://issues.jboss.org/browse/WFLY-11778
> Project: WildFly
> Issue Type: Task
> Components: EJB
> Affects Versions: 16.0.0.Beta1
> Reporter: Cheng Fang
> Priority: Major
>
> Per Kabir's email to wildfly-dev list, need to add transformer tests for ejb3 subsystem. For details see http://lists.jboss.org/pipermail/wildfly-dev/2019-February/006772.html
> {quote}
> TL;DR: It looks like we may be missing transformer tests in the following
> subsystems: ejb3, infinispan, jca, logging, undertow. I've not dug in
> beyond that.
> Full:
> We have been using ModelTestControllerVersion.EAP_7_2_0_TEMP (containing
> WF14) for transformer testing until EAP 7.2.0 was released. [1] renames
> this to be EAP_7_2_0 and points to EAP 7.2.0.
> In addition I have some WIP to update the full mixed domain and subsystem
> tests to do the same. When doing this I noticed that the only subsystem
> that had transformer tests referencing EAP_7_2_0_TEMP was modcluster. I
> knew messaging-activemq had some changes, which Emmanuel is looking at.
> I've run the model comparison tool against master/7.2.0: and see changes
> which might be significant:
> ====== Resource root address: ["subsystem" => "ejb3"] - Current version:
> 0.0.0; legacy version: 5.0.0 =======
> --- Problems for relative address to root ["passivation-store" => "*"]:
> Different 'access-type' for attribute 'bean-cache'. Current: "read-write";
> legacy: "read-only"
> Different 'access-type' for attribute 'cache-container'. Current:
> "read-write"; legacy: "read-only"
> ...
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by Amanda Han (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
Amanda Han commented on DROOLS-3674:
------------------------------------
Hello [~danielezonca] there are two candidated plans for error reporting after run.
The first one provides options"replace" or "keep" to go further steps to deal with error, or you can just have a look about the problem instruction and "cancel" to close the popover. !Error reporting after test run-different kinds.png|thumbnail!
Another one is made for complicated problems that may need with more words to explain. We show the core bug in a short sentence, if users want to know the details, click "show more details" to know the detailed problem.
!Error reporting after test run-different kinds2.png|thumbnail!
WDYT??:D
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by Amanda Han (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
Amanda Han updated DROOLS-3674:
-------------------------------
Attachment: Error reporting after test run-different kinds2.png
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months