[JBoss JIRA] (WFLY-634) TS: Pass the path to docs/examples to the tests.
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/WFLY-634?page=com.atlassian.jira.plugin.s... ]
Ondrej Zizka reassigned WFLY-634:
---------------------------------
Assignee: (was: Ondrej Zizka)
> TS: Pass the path to docs/examples to the tests.
> ------------------------------------------------
>
> Key: WFLY-634
> URL: https://issues.jboss.org/browse/WFLY-634
> Project: WildFly
> Issue Type: Sub-task
> Components: Test Suite
> Reporter: Ondrej Zizka
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In AS7, the path to the config file, passed in a system property, is only allowed to be a relative path.
> In the testsuite, we would make use of absolute paths.
> The reason is that we reuse the configs from docs/examples, and they change quite often, so having them in resources would be hardly maintainable.
> However, docs/examples is not guaranteed to be always in the same place: E.g. for EAP, or for RPM-based installation of EAP it might end up in /var/docs or such.
> I would like to pass some property from maven to the tests, but that results in absolute path.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (WFLY-902) Test framework for CLI-based tests can be very slow
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/WFLY-902?page=com.atlassian.jira.plugin.s... ]
Ondrej Zizka reassigned WFLY-902:
---------------------------------
Assignee: (was: Ondrej Zizka)
> Test framework for CLI-based tests can be very slow
> ---------------------------------------------------
>
> Key: WFLY-902
> URL: https://issues.jboss.org/browse/WFLY-902
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: David Bosschaert
> Priority: Minor
>
> The org.jboss.as.test.integration.management.base.AbstractCliTestBase provides a suitable API for testing CLI-based operations. However, running tests with a relatively large number of CLI operations can take a *long* time, seemingly much longer than necessary. This is probably related to the fact that CLIWrapper.readAllAsOpResult() method always seems to wait until the lineTimeout has expired.
> Typically the WAIT_LINETIMEOUT value is used for this argument. Shortening the timeout is not an option as I have seen cases where a test would fail when run on a slow machine, but this only happens occasionally.
> It would be *much* better if a timeout was not needed for this and the test would wait until a certain operation was finished.
> This can be observed in org.jboss.as.test.integration.management.cli.JmsTestCase and I also experienced it when writing the org.jboss.as.test.integration.osgi.management.OSGiManagementTestCase.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (WFLY-1357) XSLT scripts for integration tests failing silently
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/WFLY-1357?page=com.atlassian.jira.plugin.... ]
Ondrej Zizka reassigned WFLY-1357:
----------------------------------
Assignee: (was: Ondrej Zizka)
> XSLT scripts for integration tests failing silently
> ---------------------------------------------------
>
> Key: WFLY-1357
> URL: https://issues.jboss.org/browse/WFLY-1357
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.0.0.Alpha1
> Environment: Wildfly integration tests
> Reporter: Richard Achmatowicz
>
> We use XSLT scripts to build custom Wildfly distributions for testing.
> Hard-coding of Wildfly subsystem namespace versions with no corresponding update to the scripts when schema versions change is causing XSLT scripts to be executed but silently not carry out the intended changes, resulting in broken test cases, of which no one is aware.
> For example:
> <xsl:stylesheet xmlns:jgroups="urn:jboss:domain:jgroups:1.1"
> <xsl:template match="//jgroups:subsystem">
> // do something
> </xsl:template>
> <xsl:stylesheet>
> will do nothing when executed against a 2.0 jgroups schema.
> We need to have a general mechanism in place to work around the need to hardcode namespace versions when the namespace version is general and not specific. This needs to be applied to most XSLT scripts.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months