Check individual requirements

[hnformentin]

• VSC: terminal type "code" and VSC should open (you can use other tools like Pycharm, but demos are planned in VSC)
• python --version or python3 --version
• git --version
• a virtual environment (recommended)
  python -m venv tdd_venv or python3 -m venv tdd_venv
.\tdd_venv\Scripts\activate (Windows) or source tdd_venv/bin/activate (unix)
  Tip: create a folder for virtual environments outside the project folders
• check that the formatting tool black is installed black --version
• ssh-key connected: Check if you have it connected or Connecting to Github with ssh
• github: fork repository
• git clone repository locally
  git clone git@github.com:equinor/tdd_workshop.git
• install development requirements pip install -r dev-requirements.txt
• install tdd_workshop package pip install -e .
• VSC configured to tests: Configure test with VSC (TDD_workshop folder, ctrl+shift+P, Python: Configure tests)
• type pytest in the terminal and you should be able to run and debug some tests simple locally
• check if debug mode works:
  

• some may find helpful:
  Github/git cheat-sheet

• Debugging experience:
  -- Issues while discovering tests:
  Unable to debug Python tests (duplicate entries in "env") microsoft/vscode-python#10847
  -- Open and close VSC after adding a test

[GodVenn]

In the "git clone"-step, are we supposed to clone our fork, not the original repo?

[hnformentin]

@GodVenn good question! Ideally you would get to two remotes available: git remote –v

origin git@github.com:hnformentin/tdd_workshop.git (fetch)
origin git@github.com:hnformentin/tdd_workshop.git (push)
upstream       git@github.com:equinor/tdd_workshop.git (fetch)
upstream       git@github.com:equinor/tdd_workshop.git (push)

So you can clone equinor's one, rename it to upstream, and add your fork as a remote named origin.
We can discuss during the workshop pros and cons of having this configuration.

[hnformentin]

This issue is outdated since we are using Codespaces from now on for the course.