Change naming of challenge class filename

Change the pathname pattern from:

MyChallenge/MyChallenge.py
MyChallenge/MyChallengeTestCase.py

to:

MyChallenge/challenge.py
MyChallenge/testcase.py

The old convention led to minor issues with library resolution. The
new convention works much better with IDE.

Implement this in name resolution, scaffolding and documentation.

Author: elmar-hinz

HelloWorld/HelloWorld.py renamed to HelloWorld/challenge.py

@@ -1,6 +1,6 @@
 import unittest
 
-from .HelloWorld import HelloWorld
+from .challenge import HelloWorld
 
 
 class HelloWorldTestCase(unittest.TestCase):

HelloWorld/HelloWorldTestCase.py renamed to HelloWorld/testcase.py

@@ -70,10 +70,10 @@ The Layout of Your Directory Looks Like This
 .. code-block:: bash
 
     myChallenges/
-        Challenge1/Challenge1.py
-        Challenge1/Challenge1TestCase.py
-        Challenge2/Challenge2.py
-        Challenge2/Challenge2TestCase.py
+        Challenge1/challenge.py
+        Challenge1/testcase.py
+        Challenge2/challenge.py
+        Challenge2/testcase.py
         ... more challenges ...
 
 The names `Challenge1` and `Challenge2` are just placeholders for the names you choose during scaffolding.
@@ -107,8 +107,9 @@ You now find the files:
 .. code-block:: bash
 
     myChallenges/
-        Challenge3/Challenge3.py
-        Challenge3/Challenge3TestCase.py
+        Challenge3/challenge.py
+        Challenge3/testcase.py
+        Challenge3/__init__.py
 
 Check it's working by running the unit test case.
 
@@ -190,28 +191,38 @@ There are two deliberate exceptions:
 
 1. Challenge module names are **CamelCase**:
 
-    In contradiction to the style guide directory and class file of the challenges are not all lowercase. Especially the
+    In contradiction to the style guide directories of the challenges are not all lowercase. Especially the
     first character must be uppercase. This is used to find and list the challenge directories between other modules.
-    Even more, the directory, the class file and the class name must all use the same word, with the `.py` extension for
-    the file.
+    The directory and the class name must use the same word, with the `.py` extension for the file.
 
 2. Inherited class attributes and methods don't have a leading underscore:
 
     The inherited functions and methods of the challenge are not a public API and the style guides recommends leading
     underscores. As inheritance is a core concept of the challenge class, this would lead to a hell of leading
     underscores. For this reason we don't follow the style guide in this recommendation.
 
+.. tip::
+
+    On useful advantage of naming the directory just like your challenge class is, that you can use the path expansion
+    mechanism of the shell. Write the first characters of the class/directory name and hit <TAB>. Now you can use the
+    directory name as name of the challenge. A trailing slash is discarded. The following two inputs are equivalent.
+
+    .. code-block:: bash
+
+        prompt> challenge -k HelloWorld
+        prompt> challenge -k HelloWorld/
+
 Installation
 ============
 
 .. important::
 
-    This solftware requieres Python 3.
+    This software requires Python 3.
 
 Clone from Github
 -----------------
 
-You can clone (or download) the Challenges project directly from Github. In this case the scripts and pathes are not
+You can clone (or download) the Challenges project directly from Github. In this case the scripts and paths are not
 configured globally. Either you configure it globally or you place your challenges immediately into the projects folder
 so that the paths are detected relatively.
 

README.rst

@@ -42,6 +42,8 @@ def parse_arguments(self):
         if len(sys.argv) == 1:
             self.print_help()
         self.args = self.parser.parse_args()
+        if self.args.challenge[-1:] == '/':
+            self.args.challenge = self.args.challenge[0:-1]
 
     def print_help(self):
         self.parser.print_help()
@@ -52,11 +54,11 @@ def get_challenge_dir(self):
 
     def get_challenge_file(self):
         challenge = self.args.challenge
-        return self.root + '/' + challenge + '/' + challenge + '.py'
+        return self.root + '/' + challenge + '/challenge.py'
 
     def get_unittest_file(self):
         challenge = self.args.challenge
-        return self.root + '/' + challenge + '/' + challenge + 'TestCase.py'
+        return self.root + '/' + challenge + '/testcase.py'
 
     def get_input_file(self):
         return os.path.realpath(self.args.file)
@@ -85,12 +87,11 @@ def get_challenge_class(self):
 
     def get_full_qualified_challenge_class(self):
         challenge = self.args.challenge
-        return challenge + '.' + challenge + '.' + challenge
+        return challenge + '.challenge.' + challenge
 
     def get_full_qualified_unittest_class(self):
         challenge = self.args.challenge
-        return (challenge + '.' + challenge + 'TestCase.' + challenge +
-                'TestCase')
+        return (challenge + '.testcase.' + challenge + 'TestCase')
 
     def get_challenge(self):
         return self.get_class(self.get_full_qualified_challenge_class())()

challenges/conf.py

@@ -53,16 +53,17 @@ def calc(self):
     def get_unittest_content(self):
         text = '''
 import unittest
-from {}.{} import {}
+from {}.challenge import {}
 
 class {}TestCase(unittest.TestCase):
 
     def setUp(self):
         self.challenge = {}()
+        self.challenge.read()
 
     def test__init__(self):
         self.assertIsInstance(self.challenge, {})
 
 '''
         c = self.conf.get_challenge_class()
-        return text.strip().format(c, c, c, c, c, c)
+        return text.strip().format(c, c, c, c, c)