-
Task
-
Resolution: Done
-
L3 - Default
-
7.13.0
-
None
User story
As a Java developer, I can write JUnit 4 tests in all of the existing Process Engine Test classes.
Background
The Process Engine test suite currently uses both JUnit 3 and JUnit 4 tests. This causes several limitations:
- JUnit 3 tests extend base classes that are located in runtime code. This prevents us from applying changes that might break/impact external usage of these classes.
- Using JUnit 3 tests makes it harder to upgrade to newer JUnit versions and use new features and improvements of the JUnit framework.
- Code is duplicated among the JUnit 3 and JUnit 4 base classes/rules and needs to be doubly maintained.
AC
- Process Engine Test classes use JUnit 4 rules, or extend a base class that uses JUnit 4 rules.
- Base classes are always located in test code (and not Runtime code). E.g. PluggableProcessEngineRule.
- Existing JUnit 3 base classes (e.g. AbstractProcessEngineTestCase, PluggableProcessEngineTestCase, CmmnProcessEngineTestCase,ResourceProcessEngineTestCase) are never extended in tests.
This is the controller panel for Smart Panels app
Process Engine test suite uses JUnit 4 in all test classes
-
-
Resolution: Done
-
L3 - Default
-
7.13.0
-
None
User story
As a Java developer, I can write JUnit 4 tests in all of the existing Process Engine Test classes.
Background
The Process Engine test suite currently uses both JUnit 3 and JUnit 4 tests. This causes several limitations:
- JUnit 3 tests extend base classes that are located in runtime code. This prevents us from applying changes that might break/impact external usage of these classes.
- Using JUnit 3 tests makes it harder to upgrade to newer JUnit versions and use new features and improvements of the JUnit framework.
- Code is duplicated among the JUnit 3 and JUnit 4 base classes/rules and needs to be doubly maintained.
AC
- Process Engine Test classes use JUnit 4 rules, or extend a base class that uses JUnit 4 rules.
- Base classes are always located in test code (and not Runtime code). E.g. PluggableProcessEngineRule.
- Existing JUnit 3 base classes (e.g. AbstractProcessEngineTestCase, PluggableProcessEngineTestCase, CmmnProcessEngineTestCase,ResourceProcessEngineTestCase) are never extended in tests.
This is the controller panel for Smart Panels app
-
Nikola Koevski
-
- Votes:
-
0 Vote for this issue
- Watchers:
-
0 Start watching this issue
- Created:
- Updated:
- Resolved: