assert_enqueued/2 fails to match a job by state=available and scheduled_at about oban HOT 2 CLOSED

You're correct; the tests are generating an invalid query. There's not much of a reason to assert the scheduled time for something currently available, but I think we can still make it work.

from oban.

So I've found out that using both state and scheduled_at options forces assert_enqueued/2 to generate the following query:

#Ecto.Query<from j0 in Oban.Job, where: j0.state in ["available", "scheduled"],
 where: fragment(
  "? BETWEEN ? AND ?",
  j0.scheduled_at,
  ^~U[2023-03-22 21:36:32.819404Z],
  ^~U[2023-03-22 21:36:42.819404Z]
),
 where: j0.state == ^"scheduled", where: j0.worker == ^"Worker",
 order_by: [desc: j0.id]>

with an invalid condition state == ^"scheduled". This happens because assert_enqueued/2 builds a Job changeset to process/normalize opts, which in turn would set the scheduled state if opts contain :scheduled_at, effectively overriding the state value given in opts.

from oban.