Snowbug

Goal

There are 5 bugs in this implementation of snowman. Practice using your debugging skills to locate, diagnose, and fix the bugs. For each bug note:

1. In which function it was found
2. The line (or lines) causing the problem
3. What about the line was causing the problem
4. What needed to be done to fix the problem
5. How you located the bug

Activity Setup

1. Navigate to the folder where you wish to save activities. This could be your projects folder, or you may want to create a new folder for all of your activities.

   If you followed Ada's recommended file system structure from the Intro to Dev Environment lesson in Learn, you can navigate to your projects folder with the following command:

   $ cd ~/Developer/projects

   Or, if you want to create a new folder for all of your activities:

   $ cd ~/Developer
   $ mkdir activities
   $ cd activities

   If you've already created an activities directory, you can navigate to it with the following command:

   $ cd ~/Developer/activities

2. In Github click on the "Fork" button to fork the repository to your Github account. This will make a copy of the activity in your Github account.

3. "Clone" the activity into your working folder. This command makes a new folder named for the activity repository, and then puts the activity into this new folder.

   $ git clone <clone_url_for_the_activity>

   The <> syntax indicates a placeholder. You should replace <clone_url_for_the_activity> with the actual URL you'd use to clone this repository. If you click the green "Code" button on the GitHub page for this repository, you'll see a URL that you can copy to your clipboard.

   Use ls to confirm there's a new activity folder

4. Move your location into this activity folder

   $ cd <repository_directory>

   The <repository_directory> placeholder should be replaced with the name of the activity folder. If you're not sure what the folder is named, remember that you can use ls to list the contents of your current location.

5. Create a virtual environment named venv for this activity:

   $ python3 -m venv venv

6. Activate this environment:

   $ source venv/bin/activate

   Verify that you're in a python3 virtual environment by running:

   • $ python --version should output a Python 3 version
   • $ pip --version should output that it is working with Python 3

7. Install dependencies once at the beginning of this activity with

   # Must be in activated virtual environment
   $ pip install -r requirements.txt

   Not all activities will have dependencies, but there will still be an included requirements.txt file.

Summary of one-time activity setup:

• Fork the activity repository
• cd into your working folder, such as your projects or activities folder
• Clone the activity onto your machine
• cd into the folder for the activity
• Create the virtual environment venv
• Activate the virtual environment venv
• Install the dependencies with pip

Activity Workflow

1. When working on this activity, always ensure that your virtual environment is activated:

   $ source venv/bin/activate

2. If you want to work on another project from the same terminal window, you should deactivate the virtual environment when you are done working on the activity:

   $ deactivate

Getting Started

1. While in the activity directory, launch VS Code.

   $ code .

2. Perform test configuration by going to the Testing panel (shaped like a beaker) and clicking Configure Python Tests. Select pytest as the framework and tests as the location of the tests.

3. Run the tests using the VS Code testing tools.

4. Focus on the top test failure. Read through the test failure, and understand why the failure is happening.

5. Make a plan to fix the test failure.

6. Write code to fix the test failure.

7. Re-run the tests.

8. Continue running tests until all bugs have been fixed.

Activity Completion

Make note of your investigation, especially the 5 questions in the goal, and be prepared to share your findings with your classmates!