Skip to content

Brainstorma/Fix_My_Code_Challenge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 

Repository files navigation

Fix My Code Challenge

Welcome to the Fix My Code Challenge, a series of coding challenges designed to test your understanding of programming concepts and software engineering best practices.

The challenges in this repository are intended to simulate real-world scenarios where you might be given a codebase to troubleshoot and debug. Each challenge consists of a broken codebase with a set of specific issues that need to be fixed.

Repository Structure

./
├── challenge_0/
│   ├── main.py
│   ├── tests/
│   │   └── test_main.py
│   └── README.md
├── challenge_1/
│   ├── main.py
│   ├── tests/
│   │   └── test_main.py
│   └── README.md
├── challenge_2/
│   ├── main.py
│   ├── tests/
│   │   └── test_main.py
│   └── README.md
├── challenge_3/
│   ├── main.py
│   ├── tests/
│   │   └── test_main.py
│   └── README.md
└── challenge_4/
    ├── main.py
    ├── tests/
    │   └── test_main.py
    └── README.md

This repository contains five directories, one for each challenge. Each challenge directory contains a broken codebase, a set of test cases to validate the code, and a README file with instructions on how to complete the challenge.

Getting Started

To begin, select a challenge directory and follow the instructions in the README file to fix the codebase. For each challenge, you will be given a set of test cases to validate your solution. These test cases are located in the tests directory and can be run using Python's unittest framework.

To run the tests for a specific challenge, navigate to the challenge directory and run the following command:

python -m unittest discover -v

This will run all the tests in the tests directory and provide verbose output.

Contributing

If you would like to contribute to this repository, please submit a pull request. Before submitting a pull request, please ensure that your code follows the coding style guidelines and passes all the existing test cases.

Code Style Guidelines

  • Use PEP 8 style guidelines.
  • Use meaningful variable names.
  • Use spaces instead of tabs for indentation.
  • Keep lines less than 80 characters long.
  • Write docstrings for functions and modules.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Challenges

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published