how to make a python test driven development environment on Windows without Windows Subsystem Linux¶

This is one way to make a Python Test Driven Development environment on a Windows Computer that does NOT have Windows Subsystem Linux

requirements¶

download and install Python
get an Integrated Development Environment (IDE). Here are a few options

how to manually make a python test driven development environment on Windows without Windows Subsystem Linux¶

Imagine I have to work on a project called magic. I open a terminal in the Integrated Development Environment (IDE) and use mkdir to make a folder/directory for the project
```
mkdir magic
```
then change directory to the project with the cd program
```
cd magic
```
this is where all code for the project will stay
I make a child folder for the source code
```
mkdir src
```
then add an empty file for the source code (the actual program)
```
New-Item src/magic.py
```
New-Item makes an empty file when given a name
I make a child directory for the tests
```
mkdir tests
```
then an empty file called __init__.py in the tests folder to tell Python that it is a python package, this will help it find the tests later

Note

make sure to use 2 underscores (__) for __init__.py
```
New-Item tests/__init__.py
```
I add one more empty file in the tests directory for the actual test
```
New-Item tests/test_magic.py
```
I can use any name as long as it starts with test_

these are the folders/directories and files in the project

magic
  ╰──src
  |  ╰──magic.py
  ╰──tests
     ╰──__init__.py
     ╰──test_magic.py

py at the end of a file name shows it is a Python module

test_failure¶

The Test Driven Development cycle is RED GREEN REFACTOR

RED: make it fail - write a failing test to make sure the test works
GREEN: make it pass - write only what is needed to make the failing test pass
REFACTOR: make it better - remove duplication

red: make it fail¶

I open magic/tests/test_magic.py in the Integrated Development Environment (IDE) and type the following

Note

the line numbers below are a guide, you do not need to copy them
```
1import unittest
2
3
4class TestMagic(unittest.TestCase):
5
6    def test_failure(self):
7        self.assertFalse(True)
```
Here is an explanation of the code in the file
- import unittest imports the unittest module from the python standard library, it is used for testing
- class TestMagic
  - class is the Python keyword for making classes, which are a collection of attributes and methods for a purpose
  - TestMagic is the name of this class and will hold the test. I can use any name as long as it starts with Test
  - unittest.TestCase is a class defined in the unittest module which has methods for testing
  - class TestMagic(unittest.TestCase) defines that TestMagic inherits from unittest.TestCase which allows me use its methods
- def test_failure
  - def is the Python keyword for making methods (functions)
  - test_failure is the name of this method, I can use any name as long as it starts with test_
  - self is used to access attributes and methods of the TestMagic class and by extension the unittest.TestCase class instead of using TestMagic(). or unittest.TestCase().
  - self.assertFalse(True) is an assertion
    - assertFalse is a method in the unittest.TestCase class that checks if its input is False
    - True is given as the input
    - I expect this line to fail because True is not False, there is a problem if it does not fail
I turn on the Auto Save feature in the Integrated Development Environment (IDE) to automatically save files when I make a change so I do not repeat myself by manually saving every time there is a change

then I type this in the terminal to run the test

python -m unittest

and it shows a failure

F
=============================================================
FAIL: test_failure (tests.test_magic.TestMagic.test_failure)
-------------------------------------------------------------
Traceback (most recent call last):
File ".../magic/tests/test_magic.py", line 7, in test_failure
    self.assertFalse(True)
AssertionError: True is not false

-------------------------------------------------------------
Ran 1 test in A.XYZs

FAILED (failures=1)

If you are typing along, CONGRATULATIONS! You just wrote a test.

This is the RED part of the Test Driven Development cycle. The message in the terminal is about the failure, here is an explanation from the bottom up

FAILED (failures=1) the number of failures
Ran 1 test in A.XYZs the number of tests run and how long it took
AssertionError: True is not false the Exception raised and its message, in this case AssertionError is raised because True is not False
self.assertFalse(True) the line of code that caused the failure
File ".../magic/tests/test_magic.py", line 7, in test_failure the line number and location of the file where the failure happened

Tip

Hold ctrl (windows/linux) or option (mac) on the keyboard and use the mouse to click on File ".../magic/tests/test_magic.py", line 7 in the terminal, and the Integrated Development Environment (IDE) will open the file in the editor with the cursor at the line where the failure happened
Traceback (most recent call last): all the information shown after this line that is indented to the right shows the calls that led to the failure
FAIL: test_failure (tests.test_magic.TestMagic.test_failure) is a header with information in dot notation about the failing test method
- tests.test_magic.TestMagic.test_failure is the location of the failing test
- tests is the tests folder
- test_magic is the test_magic.py file
- TestMagic is the class defined on line 4
- test_failure is the method defined on line 6
F shows a failure
python -m unittest is the command to run tests with the unittest module
- python is the major version of Python being used
- -m is an option passed to Python to run the module given after the option

I recommend you keep a list of Exceptions you meet to become familiar with them, it helps when you run into failures later. Time to add AssertionError to the list

import unittest


class TestMagic(unittest.TestCase):

    def test_failure(self):
        self.assertFalse(True)

# Exceptions Encountered
# AssertionError

green: make it pass¶

I change the input on line 7 from True to False

self.assertFalse(False)

then run the test again in the terminal

python -m unittest

and it shows a passing test

.
------------------------------------------------------
Ran 1 test in A.XYZs

OK

cue CELEBRATION MUSIC AND DANCE! I am GREEN.

refactor: make it better¶

I ran python -m unittest to see the test fail, ran it again to see the test pass. I will have to run it again when I make a code change, to make sure tests that were passing are not failing and the new code does what I expect. This means it is run for each part of the Test Driven Development cycle or any time there is a code change. I do not want to type python -m unittest again, it is better for a program to run the tests so I do not repeat myself.

how to automatically run tests on Windows without Windows Subsystem Linux¶

how to make a virtual environment¶

I make a virtual environment with the venv module
```
python -m venv .venv
```
- python is the major version of Python being used
- -m is an option passed to Python to run the module given after the option as a script
- venv is a module from the python standard library, it is used to make a virtual environment with a given name. A virtual environment is a separate folder where python packages needed by the project will be installed
- .venv is the name given, I can use any name
I run PowerShell in Administrator mode and set the Execution Policy for the activation script to work
```
Set-ExecutionPolicy RemoteSigned
```
the terminal may show the following message if you have never run this command before
```
The execution policy helps protect you from scripts that you do not trust.
Changing the execution policy might expose you to the security risks
described in the about_Execution_Policies help topic at
https:/go.microsoft.com/fwlink/?LinkID=135170.
Do you want to change the execution policy?

[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"):
```
Type Y to accept the change and it will enable scripts that have been signed by a verified publisher to run on your computer, you can read more at Set-ExecutionPolicy

To activate the virtual environment, go back to the terminal you were working in before the Execution Policy change and type
```
.venv/scripts/activate
```
or
```
.venv/scripts/activate.ps1
```
the (.venv) on the far left of the command line in the terminal shows that I am in the virtual environment, for example
```
(.venv) .../magic $
```
I upgrade pip the python package manager to the latest version
```
python -m pip install --upgrade pip
```
- pip is a module from the python standard library, it is used to install python packages
- install is an argument given to pip to install a given package name
- --upgrade is an option given to the install argument for pip to upgrade the version of the python package given
- pip is the package name given for pip to install, in this case it upgrades itself
I can use pip to see what packages are installed in the virtual environment
```
pip list
```
the terminal shows
```
Package Version
------- -------
pip     x.y
```
I make a file in the magic directory with pytest-watch as its text
```
"pytest-watch" | Out-File requirements.txt -Encoding UTF8
```
- | is an operator that is used to send output from the left as input to the right
- Out-File writes input text to a given file
- pytest-watch is a Python program that automatically runs pytest when a Python file in the folder changes
- pytest is a python package like unittest that is used for testing
- requirements.txt is the name of a file where I can list python packages for pip to install, I can use any name
I install pytest-watch and its dependencies
```
pip install --requirement requirements.txt
```
- --requirement is another option that can be passed to the install argument for python packages in a given file
- requirements.txt is the name of the file given

I use pip to see the packages that are now installed in the virtual environment

pip list

the terminal shows

Package      Version
------------ -------
colorama     x.y.z
docopt       x.y.z
iniconfig    x.y.z
packaging    x.y
pip          x.y
pluggy       x.y.z
pytest       x.y.z
pytest-watch x.y.z
watchdog     x.y.z

The folder/directory structure now looks like this

magic
  ╰──.venv
  ╰──src
  | ╰──magic.py
  ╰──tests
  |  ╰──__pycache__
  |  ╰──__init__.py
  |  ╰──test_magic.py
  ╰──requirements.txt

I run the tests from the terminal

pytest-watch

and it shows results without going back to the command line

[TODAYS_DATE] Running: py.test
================== test session starts===================
...
rootdir: .../magic
collected 1 item

tests/test_magic.py .                              [100%]

=============== 1 passed in X.YZs =======================

when I change the input on line 7 in test_magic.py from False to True it shows AssertionError

====================================== FAILURES =======================================
_______________________________ TestMagic.test_failure ________________________________

self = <tests.test_magic.TestMagic testMethod=test_failure>

    def test_failure(self):
>       self.assertFalse(True)
E       AssertionError: True is not false

tests/test_magic.py:7: AssertionError
============================== short test summary info ================================
FAILED tests/test_magic.py::TestMagic::test_failure - AssertionError: True is not false
================================= 1 failed in X.YZs ===================================

then I change it back to False to make it pass and can write the rest of the code for the project while the tests run automatically

Note

press ctrl + c on the keyboard in the terminal to stop the tests at anytime

how to deactivate a virtual environment¶

type this in a terminal with an active virtual environment

deactivate

how to activate a virtual environment¶

Make sure you are in the folder/directory that has the virtual environment for example magic, and type this in the terminal

.venv/scripts/activate

.venv/scripts/activate.ps1

the (.venv) on the far left of the command line in the terminal shows that I am in the virtual environment

(.venv) .../magic $

how to automatically make a python test driven development environment on Windows without Windows Subsystem Linux¶

You made it this far and have become the greatest programmer in the world. To follow The Do Not Repeat Yourself (DRY) Principle, I would write a program that has all the commands it took to get here, then I can use it to make a Test Driven Development Environment anytime I want and not have to remember each step of the process

I exit the tests in the terminal by pressing ctrl + c on the keyboard
and leave the virtual environment
```
deactivate
```
then change directory to the parent of magic
```
cd ..
```
and make an empty file with a name that describes what the program does so it is easy to remember later, for example makePythonTdd.ps1
```
New-Item makePythonTdd.ps1
```
I use the history program to list the commands I typed and use them as an example for the program
```
history
```

I click on the file to open it in the Integrated Development Environment (IDE), then type the commands I need to make a Test Driven Development Environment in the file

#!/bin/bash
mkdir magic
cd magic
mkdir src
New-Item src/magic.py
mkdir tests
New-Item tests/__init__.py
New-Item tests/test_magic.py
python -m venv .venv
.venv/scripts/activate.ps1
python -m pip install --upgrade pip
"pytest-watch" | Out-File requirements.txt -Encoding UTF8
python -m pip install --requirement requirements.txt
pytest-watch

This program will always make a project called magic. I add a variable to replace magic so I can use it to make any project I want by giving it the name of the project

#!/bin/bash
$PROJECT_NAME=$args[0]
mkdir $PROJECT_NAME
cd $PROJECT_NAME
mkdir src
New-Item "src/$PROJECT_NAME.py"
mkdir tests
New-Item tests/__init__.py
New-Item tests/test_magic.py
python -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
"pytest-watch" | Out-File requirements.txt -Encoding UTF8
python -m pip install --requirement requirements.txt
pytest-watch

$args[0] is the first argument given when the program is called. I can use it in place of $PROJECT_NAME

I use the Out-File program to add text for the first failing test to test_$PROJECT_NAME.py

Note

the line numbers below are a guide, you do not need to copy them

$PROJECT_NAME=$args[0]
mkdir $PROJECT_NAME
cd $PROJECT_NAME
mkdir src
New-Item "src/$PROJECT_NAME.py"
mkdir tests
New-Item tests/__init__.py

"import unittest


class Test$($PROJECT_NAME)(unittest.TestCase):

    def test_failure(self):
        self.assertFalse(True)


# Exceptions Encountered
# AssertionError
" | Out-File "tests/test_$PROJECT_NAME.py" -Encoding UTF8

python -m venv .venv
.venv/scripts/activate.ps1
python -m pip install --upgrade pip
"pytest-watch" | Out-File requirements.txt -Encoding UTF8
python -m pip install --requirement requirements.txt
pytest-watch

I can make a Test Driven Development environment when I call the program with a name for the $PROJECT_NAME variable. For example, when I type the following in the terminal in the directory where makePythonTdd.ps1 is saved
```
./makePythonTdd.ps1 calculator
```
the computer will make a Test Driven Development environment for a project called calculator, you can continue this in how to make a calculator

review¶

One of the advantages of programming is that I can take some steps and make them a one line command for the computer to do for me.

You have seen a way to make a Python Test Driven Development Environment, and have a program to do it for you on any Windows computers without having to install Windows Subsystem Linux.

Would you like to test making a calculator?

makePythonTdd.ps1