# RM31286, in this testcase we are creating/dropping dbms_scheduler extension
# thus better run this before running setup script
test: edb-core/contrib/dbms_scheduler/RM31286_create_extension_and_search_path

# need to keep pg_dump test at the start because while resorting the database
# it does do setval for the pgAgent sequences. this sequence number do get
# change with any other job submitted, so make is consistent every run keep
# pg_dump test at start.
test: edb-core/contrib/dbms_scheduler/setup
test: edb-core/contrib/dbms_scheduler/ds_pg_dump_restore
test: edb-core/contrib/dbms_scheduler/basic_checks
test: edb-core/contrib/dbms_scheduler/program_type_stored_procedure_check
test: edb-core/contrib/dbms_scheduler/create_schedule
test: edb-core/contrib/dbms_scheduler/evaluate_calender_string
test: edb-core/contrib/dbms_scheduler/scheduler_sanity_check_test
test: edb-core/contrib/dbms_scheduler/rm30838
test: edb-core/contrib/dbms_scheduler/scheduler_views
test: edb-core/contrib/dbms_scheduler/scheduler_RM_testcases
test: edb-core/contrib/dbms_scheduler/dbms_scheduler_program_api
test: edb-core/contrib/dbms_scheduler/dbms_scheduler_schedule_api
test: edb-core/contrib/dbms_scheduler/dbms_scheduler_job_api
test: edb-core/contrib/dbms_scheduler/multiple_user_permission
test: edb-core/contrib/dbms_scheduler/program_action_with_commit
test: edb-core/contrib/dbms_scheduler/cleanup
