[
https://issues.redhat.com/browse/DROOLS-5729?page=com.atlassian.jira.plug...
]
Kris Verlaenen updated DROOLS-5729:
-----------------------------------
Sprint: 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51
(from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25) (was: 2020
Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30),
2020 Week 52-03 (from Dec 21))
Reorganize drools unit tests
----------------------------
Key: DROOLS-5729
URL:
https://issues.redhat.com/browse/DROOLS-5729
Project: Drools
Issue Type: Story
Components: core engine
Affects Versions: 7.44.0.Final
Reporter: Toshiya Kobayashi
Assignee: Toshiya Kobayashi
Priority: Major
Motivation: The motivation is to increase test coverage. For example, unit tests which
exist under drools-mvel are not tested against executable-model. "Which module is
suitable for the unit test?" depends on each test so we may occasionally need to
discuss. But basically drools-test-coverage is a good place for DRL based tests because
drools-test-coverage may have all dependencies so is flexible to test with any
configurations (e.g. alpha compiler network).
Goals: Increase test coverage. More stable product.
Impact: During this work, we may find new bugs (because of increased tests). Will need to
fix them one-by-one as separated JIRAs.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)