[JBoss JIRA] (SWSQE-879) Increase code coverage above 80% (UI tests)
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-879?page=com.atlassian.jira.plugin.... ]
Filip Brychta updated SWSQE-879:
--------------------------------
Description:
There will be sub task for each package which is not covered at least by 80%
For each sub task you can:
* add new tests to increase coverage above 80%
* add new tests to increase coverage below 80% with comment why it's not possible to achieve 80%
* close the sub task with comment why it's not possible to cover it by tests so it should be excluded from the coverage report
See chapter How to get the latest code coverage in https://docs.jboss.org/display/SWSQE/Code+coverage+for+system+tests to generate the latest code coverage.
> Increase code coverage above 80% (UI tests)
> -------------------------------------------
>
> Key: SWSQE-879
> URL: https://issues.jboss.org/browse/SWSQE-879
> Project: Kiali QE
> Issue Type: Story
> Reporter: Filip Brychta
> Priority: Major
> Labels: automation
>
> There will be sub task for each package which is not covered at least by 80%
> For each sub task you can:
> * add new tests to increase coverage above 80%
> * add new tests to increase coverage below 80% with comment why it's not possible to achieve 80%
> * close the sub task with comment why it's not possible to cover it by tests so it should be excluded from the coverage report
> See chapter How to get the latest code coverage in https://docs.jboss.org/display/SWSQE/Code+coverage+for+system+tests to generate the latest code coverage.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 4 months
[JBoss JIRA] (WFWIP-167) EAP Operator handling ConfigMap internally
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-167?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFWIP-167:
------------------------------------
User Scenario: User change external standalone.xml and want to apply changes.
Does operator provide support for applying changes without service outage? E.g restart pods one by one?
> EAP Operator handling ConfigMap internally
> ------------------------------------------
>
> Key: WFWIP-167
> URL: https://issues.jboss.org/browse/WFWIP-167
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> If I understand description in [1] correctly. To specify custom standalone.xml I have to create ConfigMap with standalone.xml first and afterwards link operator to this ConfigMap.
> Is it possible to handle creation of ConfigMap and storing standalone.xml for me? Ideally I just specify file URI where custom standalone.xml is located. This location have to be accessible from operator pod. In this way we can look at it as hiding internals (implementation details) from users.
> Currently when user wants to change standalone.xml he does in ConfigMap, not operator. When changing standalone.xml through config map, I assume pod have to be restarted manually. Operator could do that for me.
> However this can be triggered by storing newer version of standalone.xml under another key, eg `standalone.xml.v2` and changing `StandaloneConfigMapSpec.key` in operator.
> What do you think? Have you considered this approach?
> [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#sta...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 4 months