Question’s pub_date field is in the future (which certainly isn’t). To check if the bug really exists, using the Admin create a question whose date lies in the future and check the method using the shell: instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. Create a test to expose the bug What we’ve just done in the shell to test for the problem is exactly what we can do in an

Question’s pub_date field is in the future (which certainly isn’t). To check if the bug really exists, using the Admin create a question whose date lies in the future and check the method using the shell: instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. Create a test to expose the bug What we’ve just done in the shell to test for the problem is exactly what we can do in an

Question’s pub_date field is in the future (which certainly isn’t). To check if the bug really exists, using the Admin create a question whose date lies in the future and check the method using the shell: instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. Create a test to expose the bug What we’ve just done in the shell to test for the problem is exactly what we can do in an

Question’s pub_date field is in the future (which certainly isn’t). To check if the bug really exists, using the Admin create a question whose date lies in the future and check the method using the shell: instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. Create a test to expose the bug What we’ve just done in the shell to test for the problem is exactly what we can do in an

also if the Question’s pub_date field is in the future (which certainly isn’t). You can see this in the Admin; create a question whose date lies in the future; you’ll see that the Question change list claims instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. Create a test to expose the bug What we’ve just done in the shell to test for the problem is exactly what we can do in an

also if the Question’s pub_date field is in the future (which certainly isn’t). You can see this in the Admin; create a question whose date lies in the future; you’ll see that the Question change list claims instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. Create a test to expose the bug What we’ve just done in the shell to test for the problem is exactly what we can do in an

Question’s pub_date field is in the future (which certainly isn’t). Confirm the bug by using the shell to check the method on a question whose date lies in the future: $ python manage.py shell >>> import instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. Create a test to expose the bug What we’ve just done in the shell to test for the problem is exactly what we can do in an

Question’s pub_date field is in the future (which certainly isn’t). Confirm the bug by using the shell to check the method on a question whose date lies in the future: $ python manage.py shell >>> import instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. Create a test to expose the bug What we’ve just done in the shell to test for the problem is exactly what we can do in an

Question’s pub_date field is in the future (which certainly isn’t). Confirm the bug by using the shell to check the method on a question whose date lies in the future: $ python manage.py shell >>> import instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. Create a test to expose the bug What we’ve just done in the shell to test for the problem is exactly what we can do in an

Question’s pub_date field is in the future (which certainly isn’t). To check if the bug really exists, using the Admin create a question whose date lies in the future and check the method using the shell: instance with pub_date 30 days in the future >>> future_question = Question(pub_date=timezone.now() + datetime.timedelta(days=30)) >>> # was it published recently? >>> future_question.was_published_recently() () True Since things in the future are not ‘recent’, this is clearly wrong. 2.7. Writing your first Django app, part 5 43 Django Documentation, Release 2.0.14.dev20190701080343 Create a test to expose