-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[14.0][ADD] project_forecast_line_deadline #13
Conversation
08df2f4
to
9f4bde8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM
3bce03a
to
6817b01
Compare
# Set forecast_date_deadline manually | ||
task.forecast_date_planned_end = "2022-02-01" | ||
# Dates are not the same anymore | ||
self.assertNotEqual(task.forecast_date_planned_end, task.date_deadline) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, "not the same anymore" could also mean that None was written to the field. Could we, aside from this, also explicitly check for the date that was written?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically we give a value directly on the field in line 23.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...yes, but we then don't check for that same value. So, we don't test whether the inverse function actually writes that value - we just test whether the result is a different value. (It's nitpicking, I know)
6817b01
to
5517f64
Compare
5517f64
to
dff7328
Compare
No description provided.