[ https://issues.apache.org/jira/browse/IGNITE-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Korotkov updated IGNITE-16569: ------------------------------------- Summary: Add ability to customize the test context for ducktest (was: Fix several ducktests) > Add ability to customize the test context for ducktest > ------------------------------------------------------ > > Key: IGNITE-16569 > URL: https://issues.apache.org/jira/browse/IGNITE-16569 > Project: Ignite > Issue Type: Bug > Reporter: Sergey Korotkov > Assignee: Sergey Korotkov > Priority: Minor > Labels: ducktests > Time Spent: 50m > Remaining Estimate: 0h > > There are several problems in ducktest which should be fixed to let them run > in different configurations: > # The *PersistenceUpgradeTest* fails if SSL is enabled via the --globals > options. The immediate reason is that control.sh doesn't support the SSL > options (like key_store_path) in the 2.7.6 version which is the starting > point for the test incremental migrations of the PDS. Solution is to ignore > test if SSL is enabled. > # The *AuthenticationTests* uses the hardcoded username and password and > ignores ones passed via the globals. -- This message was sent by Atlassian Jira (v8.20.1#820001)