From 9c9d817250c5c64e69feef8004980878f7a328a8 Mon Sep 17 00:00:00 2001 From: likechrisss Date: Sun, 29 Dec 2024 14:23:40 -0500 Subject: [PATCH] Fixed the structure --- solutions/tests/challenge_2/README.md | 59 --------------------------- 1 file changed, 59 deletions(-) delete mode 100644 solutions/tests/challenge_2/README.md diff --git a/solutions/tests/challenge_2/README.md b/solutions/tests/challenge_2/README.md deleted file mode 100644 index b6eefe12e..000000000 --- a/solutions/tests/challenge_2/README.md +++ /dev/null @@ -1,59 +0,0 @@ -# Tests - -This directory contains the unit tests for the project. -The tests are written using the `unittest` framework. - -## Running Tests - -To run the tests, use the following command: - -```sh -python -m unittest -``` - -This command will automatically discover and run all the test cases in this directory. - -## Directory Structure - -The tests are organized as follows: - -```md -solutions/ - tests/ - __init__.py - test_example.py -``` - -- `__init__.py`: This file makes the directory a Python package. -- `test_example.py`: This file contains example test cases. - -## Writing Tests - -To add new tests, create a new file in the `tests` directory -and define your test cases using the `unittest` framework. - -Here is an example of a simple test case: - -```python -import unittest - -class TestExample(unittest.TestCase): - def test_addition(self): - self.assertEqual(1 + 1, 2) - -``` - -## Test Coverage - -Ensure that your tests cover all the critical parts of your codebase. -Aim for high test coverage to catch potential issues early. - -## Contributing - -If you would like to contribute to the tests, please follow these guidelines: - -1. Write clear and concise test cases. -2. Ensure that your tests pass before submitting a pull request. -3. Follow the existing code style and conventions. - -Let's maintain a high-quality codebase! 👩‍💻✨🚀