Work around brittle timestamp comparisons in tests #112

Closed
opened 4 years ago by jking · 0 comments
jking commented 4 years ago
Owner

Feed and database tests can sometimes fail because timestamps being compared against expectations are off by one second. I'm not certain how this can be worked around for PHPUnit database tests (see issue #111), but for non-database tests, we can and should fudge the date: second precision is not required for any tests, and likely will never be.

Feed and database tests can sometimes fail because timestamps being compared against expectations are off by one second. I'm not certain how this can be worked around for PHPUnit database tests (see issue #111), but for non-database tests, we can and should fudge the date: second precision is not required for any tests, and likely will never be.
jking added this to the Future milestone 4 years ago
jking added the
bug
testing
labels 4 years ago
jking closed this issue 4 years ago
jking modified the milestone from Future to 0.3.0 4 years ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

0000-12-31 Overdue

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.