René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"App Engine testrunner doesn't behave like docs suggest","articleBody":"This is relatively minor - just something I noticed relating to [/appengine/standard/localtesting/runner.py](https://github.com/GoogleCloudPlatform/python-docs-samples/blob/master/appengine/standard/localtesting/runner.py)\n\nThe App Engine [Setting up a testing framework](https://cloud.google.com/appengine/docs/python/tools/localunittesting#Python_Setting_up_a_testing_framework) documentation states: \"Test files follow the convention of having **test** prefixed to their name.\"\n\nHowever, 1fe6ae4 changed the behaviour to look for files **ending** with **_test.py**\n\nThis makes sense if you're trying to run the sample tests, but not if you've used the testrunner on another project and named your test modules according to what has up until now been the default expectation, being test files with test **prefixed**. If you were to update your testrunner code to the latest and greatest you'll now find none of your tests being run. That is **if** you notice - assuming most people don't set up their builds to fail on:\n\n```\n----------------------------------------------------------------------\nRan 0 tests in 0.000s\n\nOK\n```\n\nSo, I would argue that it would be better to stick with the default (discover test files prefixed with test) and instead rename the sample tests.\n\nTL;DR;\nminor mismatch with documentation, has potential to cause havoc for people that have used the testrunner and who update it\n","author":{"url":"https://github.com/maltem-za","@type":"Person","name":"maltem-za"},"datePublished":"2016-09-06T15:27:12.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/500/python-docs-samples/issues/500"}