Skip to content

Expand test suite to test all possible kwargs to Schedule #34

Open
@joshuadavidthomas

Description

@joshuadavidthomas

Re: #30, this would have been caught had there been tests that exercise all the different options a Schedule can take.

Doc references:

func (str) – the function to schedule. Dotted strings only.

args – arguments for the scheduled function.

name (str) – An optional name for your schedule.

hook (str) – optional result hook function. Dotted strings only.

schedule_type (str) – (O)nce, M(I)nutes, (H)ourly, (D)aily, (W)eekly, (M)onthly, (Q)uarterly, (Y)early or (C)ron Schedule.TYPE

minutes (int) – Number of minutes for the Minutes type.

cron (str) – Cron expression for the Cron type.

repeats (int) – Number of times to repeat schedule. -1=Always, 0=Never, n =n.

next_run (datetime) – Next or first scheduled execution datetime.

cluster (str) – optional cluster name. Task will be executed only on a cluster with a matching name.

intended_date_kwarg (str) – optional identifier to pass intended schedule date.

q_options (dict) – options passed to async_task for this schedule

kwargs – optional keyword arguments for the scheduled function.

Metadata

Metadata

Assignees

No one assigned

    Labels

    👶 good first issueGood for newcomers🧪 testsIssues or tasks related to writing or improving tests

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions