[JBoss JIRA] (JBWS-4185) Ignore rules make false positives
by Jan Blizňák (Jira)
Jan Blizňák created JBWS-4185:
---------------------------------
Summary: Ignore rules make false positives
Key: JBWS-4185
URL: https://issues.jboss.org/browse/JBWS-4185
Project: JBoss Web Services
Issue Type: Bug
Affects Versions: jbossws-cxf-5.3.0.Final
Reporter: Jan Blizňák
Assignee: Jan Blizňák
Current implementations of Ignore* test rules can only skip the test when theirs assume fails. However, when assume passes it will mark test as passed no matter what the real outcome would be.
The problem is the rule does not call the base {{Statement}} it is wrapped around so it effectively stops the execution of the test.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years, 3 months
[JBoss JIRA] (JBWS-4183) Extend travis testing with elytron profile
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/JBWS-4183?page=com.atlassian.jira.plugin.... ]
Jan Blizňák updated JBWS-4183:
------------------------------
Description:
Currently the travis for jbossws-cxf is configured to test 3 most recent server integration with two jdks, also in combination with security manager enabled or not
(jdk8|jdk11) x (secmgr on|secmgr off) x (wildfly1600|wildfly1700|wildfly1800)
The problem is we are lacking test run with elytron security configuration which already caused we missed a regression JBWS-4180.
The other issue is that the security manager scenario as executed in travis is no different from standard run except one skipped test, causing half of running configuration to be redundant, this must be revisited if the test scenario is still desired.
was:
Currently the travis for jbossws-cxf is configured to test 4 most recent server integration with two jdks, also in combination with security manager enabled or not
(jdk8|jdk11) x (secmgr on|secmgr off) x (wildfly1500|wildfly1600|wildfly1700|wildfly1800)
The problem is we are lacking test run with elytron security configuration which already caused we missed a regression JBWS-4180.
The other issue is that the security manager scenario as executed in travis is no different from standard run except one skipped test, causing half of running configuration to be redundant, this must be revisited if the test scenario is still desired.
> Extend travis testing with elytron profile
> ------------------------------------------
>
> Key: JBWS-4183
> URL: https://issues.jboss.org/browse/JBWS-4183
> Project: JBoss Web Services
> Issue Type: Task
> Reporter: Jan Blizňák
> Assignee: Jan Blizňák
> Priority: Major
>
> Currently the travis for jbossws-cxf is configured to test 3 most recent server integration with two jdks, also in combination with security manager enabled or not
> (jdk8|jdk11) x (secmgr on|secmgr off) x (wildfly1600|wildfly1700|wildfly1800)
> The problem is we are lacking test run with elytron security configuration which already caused we missed a regression JBWS-4180.
> The other issue is that the security manager scenario as executed in travis is no different from standard run except one skipped test, causing half of running configuration to be redundant, this must be revisited if the test scenario is still desired.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBWS-4184) Revisit test execution with security manager enabled
by Jan Blizňák (Jira)
Jan Blizňák created JBWS-4184:
---------------------------------
Summary: Revisit test execution with security manager enabled
Key: JBWS-4184
URL: https://issues.jboss.org/browse/JBWS-4184
Project: JBoss Web Services
Issue Type: Task
Reporter: Jan Blizňák
This is a follow up of JBWS-4183 where redundant travis matrix configuration were removed.
The security manager testing was executed with {{mvn -Psecmgr -DSECMGR=true ...}} which only caused to activate secmgr profile (making particular test skip) but nothing more. SECMGR system property is used nowhere.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBWS-4183) Extend travis testing with elytron profile
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/JBWS-4183?page=com.atlassian.jira.plugin.... ]
Jan Blizňák commented on JBWS-4183:
-----------------------------------
There is also an error that wildfly is build also for wildfly1700 profile but these artifacts is further unused in such execution.
> Extend travis testing with elytron profile
> ------------------------------------------
>
> Key: JBWS-4183
> URL: https://issues.jboss.org/browse/JBWS-4183
> Project: JBoss Web Services
> Issue Type: Task
> Reporter: Jan Blizňák
> Assignee: Jan Blizňák
> Priority: Major
>
> Currently the travis for jbossws-cxf is configured to test 4 most recent server integration with two jdks, also in combination with security manager enabled or not
> (jdk8|jdk11) x (secmgr on|secmgr off) x (wildfly1500|wildfly1600|wildfly1700|wildfly1800)
> The problem is we are lacking test run with elytron security configuration which already caused we missed a regression JBWS-4180.
> The other issue is that the security manager scenario as executed in travis is no different from standard run except one skipped test, causing half of running configuration to be redundant, this must be revisited if the test scenario is still desired.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBWS-4183) Extend travis testing with elytron profile
by Jan Blizňák (Jira)
Jan Blizňák created JBWS-4183:
---------------------------------
Summary: Extend travis testing with elytron profile
Key: JBWS-4183
URL: https://issues.jboss.org/browse/JBWS-4183
Project: JBoss Web Services
Issue Type: Task
Reporter: Jan Blizňák
Assignee: Jan Blizňák
Currently the travis for jbossws-cxf is configured to test 4 most recent server integration with two jdks, also in combination with security manager enabled or not
(jdk8|jdk11) x (secmgr on|secmgr off) x (wildfly1500|wildfly1600|wildfly1700|wildfly1800)
The problem is we are lacking test run with elytron security configuration which already caused we missed a regression JBWS-4180.
The other issue is that the security manager scenario as executed in travis is no different from standard run except one skipped test, causing half of running configuration to be redundant, this must be revisited if the test scenario is still desired.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBWS-4182) Convenient enhancements to TS
by Jan Blizňák (Jira)
Jan Blizňák created JBWS-4182:
---------------------------------
Summary: Convenient enhancements to TS
Key: JBWS-4182
URL: https://issues.jboss.org/browse/JBWS-4182
Project: JBoss Web Services
Issue Type: Task
Reporter: Jan Blizňák
Assignee: Jan Blizňák
To make testing at various environments and with various containers more convinient, let's add two options to TS execution:
* ability to skip WS-Discovery tests at environment with network not set for it
* ability to run tests directly from testsuite module by ignoring jbossws-cxf-dist dependency
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months