e074a90222
Used new builder to create classifications. Instead of working with a clean database for each test, we create a scenario. In that scenario we use ClassificationCustomField#CUSTOM_1 to filter out all the other created Classifications. Therefore, all tests regarding ClassificationCustomFields are executed first. The alternative is to create a "big" scenario as a test setup. But that would result to the same issues we have with the sql file. Corrected assertion for should_FindClassifications_When_QueryingForListValueField():167. The databases (H2, POSTGRES) have different interpretations for boolean values. getCustomAttribute got deprecated, now getCustomField is being used. Move test to taskana-core-test according to new project structure. Separated QueryClassificationsAccTest to filtering and sorting class. ClassificationQueryAccTest resolved to QueryClassifications classes. TSK-1816: X |
||
|---|---|---|
| .. | ||
| archunit_store | ||
| src/test | ||
| pom.xml | ||