title: Python unittest module invoking wrong class?
body: <p>I am working on a Django project and some unittests seemed to be failing seemingly unexpectedly.  I was able to track down the failures to how it seems the VSCode/unittest testing framework is calling the test cases.  I was able to reproduce the behavior with the simple setup below. </p>
  
  <pre class="lang-py prettyprint-override"><code>import unittest
  
  class USER_STORY_1_8_1(unittest.TestCase):
  
      def setUp(self):
          print('USER_STORY_1_8_1:setUp')
  
      def tearDown(self):
          print('USER_STORY_1_8_1:tearDown')
  
      def test_run(self):
          print('USER_STORY_1_8_1:test_run')
  
  class USER_STORY_1_8_10(unittest.TestCase):
  
      def setUp(self):
          print('USER_STORY_1_8_10:setUp')
  
      def tearDown(self):
          print('USER_STORY_1_8_10:tearDown')
  
      def test_run(self):
          print('USER_STORY_1_8_10:test_run')
  
  class USER_STORY_1_8_11(unittest.TestCase):
  
      def setUp(self):
          print('USER_STORY_1_8_11:setUp')
  
      def tearDown(self):
          print('USER_STORY_1_8_11:tearDown')
  
      def test_run(self):
          print('USER_STORY_1_8_11:test_run')
  </code></pre>
  
  <p><a href="https://i.stack.imgur.com/HPvWO.png" rel="nofollow noreferrer">Screen Capture of VSCode project Here</a></p>
  
  <p>It seems that for similarly named test cases like these:</p>
  
  <pre class="lang-py prettyprint-override"><code>class USER_STORY_1_8_1(unittest.TestCase)
  class USER_STORY_1_8_10(unittest.TestCase)
  class USER_STORY_1_8_11(unittest.TestCase)
  </code></pre>
  
  <p>instead of calling each one in an exact-match type of way, it's doing some kind of 'USER_STORY_1_8_1.*' ordered resolution so that a call to USER_STORY_1_8_1 actually calls into the setUp() for USER_STORY_1_8_11.  If USER_STORY_1_8_11 is unavailable (e.g. commented out), then i resolves to USER_STORY_1_8_10. And if neither is available, only then it calls the correct USER_STORY_1_8_1.</p>
  
  <p>Is there anyway to override this behavior?</p>