From 7cc5253f7180c80205a263b5cfc725806a9c58f6 Mon Sep 17 00:00:00 2001 From: saeed-emad Date: Sun, 12 Jan 2025 00:51:29 +0200 Subject: [PATCH] update style of our group across all MD --- collaboration/README.md | 118 ++++++++++++++++---------------- collaboration/communication.md | 43 ++++++------ collaboration/constraints.md | 70 ++++++++++--------- collaboration/retrospective.md | 120 +++++++++++++++++++-------------- solutions/tests/README.md | 114 ++++++++++++------------------- 5 files changed, 232 insertions(+), 233 deletions(-) diff --git a/collaboration/README.md b/collaboration/README.md index 75ea03812..0dca88033 100644 --- a/collaboration/README.md +++ b/collaboration/README.md @@ -1,85 +1,81 @@ -# Collaboration +# ๐Ÿค Collaboration -## Group Norms Summary +## ๐ŸŒŸ Group Norms Summary -Our team prioritizes productivity through clear communication, timely task - delivery, and collaborative problem-solving. We hold efficient, purposeful - meetings and make decisions democratically. By fostering a supportive - environment, we ensure every member's contributions drive - progress toward our shared goals. +Our team prioritizes productivity through: +๐Ÿ“ฃ Clear communication +โฐ Timely task delivery +๐Ÿค” Collaborative problem-solving +We hold efficient, purposeful meetings ๐Ÿ—“๏ธ and make decisions democratically. +By fostering a supportive environment ๐Ÿซ‚, we ensure every member's contributions +drive progress toward our shared goals. -## Group Norms for Effective Collaboration +## ๐Ÿš€ Group Norms for Effective Collaboration -### 1. Building Trust +### 1. ๐Ÿค Building Trust -- Trust is built through action: deliver tasks on - time, with quality, and clarity. -- Foster trust by assuming good intentions and maintaining - honesty and transparency. -- Acknowledge each member's contributions regularly and openly. -- Clearly define tasks, deadlines, and expectations to avoid misunderstandings. -- Respect othersโ€™ time and schedules, and ask for help when needed. +- โœ… Deliver tasks on time, with quality and clarity. +- ๐Ÿ›ก๏ธ Foster trust through honesty and transparency. +- ๐ŸŽ‰ Acknowledge contributions regularly and openly. +- ๐Ÿ“Œ Define tasks, deadlines, and expectations clearly. +- ๐Ÿ•’ Respect othersโ€™ time and ask for help when needed. -### 2. Strengthening Relationships +### 2. ๐Ÿค— Strengthening Relationships -- Listen actively during discussions, ensuring everyone feels heard. -- Avoid interrupting or dismissing othersโ€™ ideas. -- Avoid personalizing conflicts and focus on solutions. -- Show appreciation for teammates' efforts and celebrate collective successes. -- Use constructive feedback to resolve disagreements, offering - solutions rather than criticism. +- ๐Ÿ›‘ Avoid interrupting or dismissing othersโ€™ ideas. +- ๐Ÿ‘‚ Listen actively to ensure everyone feels heard. +- ๐Ÿ› ๏ธ Focus on solutions, not personalizing conflicts. +- ๐Ÿ™Œ Show appreciation and celebrate successes. +- โœ๏ธ Use constructive feedback to resolve disagreements. -### 3. Communication Practices +### 3. ๐Ÿ’ฌ Communication Practices -- Use Google Meet for major decisions and updates. -- Slack or WhatsApp is preferred for detailed discussions and quick questions. -- Keep dedicated project files organized and accessible to everyone. -- Share meeting notes, updates, and agendas on Slack for transparency. +- ๐Ÿ“ž Use Google Meet for major updates and decisions. +- ๐Ÿ’ป Use Slack or WhatsApp for quick questions and discussions. +- ๐Ÿ“‚ Keep files organized and accessible to all. +- ๐Ÿ“ Share meeting notes and updates on Slack for transparency. -### 4. Meetings and Coordination +### 4. ๐Ÿ—“๏ธ Meetings and Coordination -- Plan meetings using Slack polls and finalize times with Google Calendar. -- Assign roles for smooth coordination: - - **Coordinator**: Manage meetings and oversee organization. - - **Vice-Coordinator**: Record outcomes and handle updates. - - **Technical Supervisor**: Oversee project technicalities and support the team. -- Meetings should only be held when they add value. -- Set the agenda for each meeting during the previous one to ensure preparedness. -- Wait a maximum of 5 minutes for late members before proceeding. -- Start and end meetings on time, adhering to a clear agenda. -- Promote open communication about scheduling preferences and potential conflicts. +- ๐Ÿ—ณ๏ธ Plan meetings with Slack polls, finalize times on Google Calendar. +- ๐ŸŽฏ Assign roles for smooth coordination: + - **Coordinator**: Manages meetings and organization. + - **Vice-Coordinator**: Records outcomes and updates. + - **Technical Supervisor**: Oversees technical aspects. +- ๐Ÿ•” Wait a max of 5 minutes for late members before proceeding. +- โฑ๏ธ Start and end meetings on time with a clear agenda. -### 5. Balancing Discussions and Debates +### 5. โš–๏ธ Balancing Discussions and Debates -- Prioritize discussions over debates in most cases. -- Engage in discussions to explore ideas and seek consensus. -- Reserve debates for situations with well-formed differing opinions. -- Define the purpose of each debate, avoid redundancy, and listen to diverse perspectives. +- ๐Ÿ’ก Prioritize discussions over debates for most decisions. +- ๐Ÿค Seek consensus during discussions. +- ๐Ÿ”„ Reserve debates for clear, differing opinions. +- ๐ŸŽฏ Focus debates on specific purposes and diverse perspectives. -### 6. Decision-Making and Conflict Resolution +### 6. ๐Ÿ—ณ๏ธ Decision-Making and Conflict Resolution -- Discuss disagreements calmly in dedicated meetings. -- Use a democratic approach: - - In meetings: Quick voting, with the majority deciding. - - Online: Slack or WhatsApp polls with a 12-hour response window. +- ๐Ÿค” Discuss disagreements calmly in meetings. +- ๐Ÿ—ณ๏ธ Use democratic voting: + - **Meetings**: Majority vote. + - **Online**: Slack or WhatsApp polls (12-hour response). -### 7. Rebuilding Trust When Broken +### 7. ๐Ÿ”„ Rebuilding Trust When Broken -- Address concerns openly and focus on solutions rather than assigning blame. -- Take responsibility for mistakes and commit to improvement. -- Reset expectations and work collaboratively to rebuild confidence. +- ๐Ÿค— Address concerns openly and focus on solutions. +- ๐Ÿค Take responsibility for mistakes and commit to improving. +- ๐Ÿ“… Reset expectations and rebuild confidence together. -### 8. Respectful Collaboration +### 8. ๐Ÿค Respectful Collaboration -- Respect is shown by acknowledging ideas, even if theyโ€™re not adopted. -- Constructive disagreements involve proposing alternatives or seeking solutions. -- Avoid ignoring deadlines, input, or contributions from team members. +- ๐Ÿค— Acknowledge ideas, even if not adopted. +- โœ๏ธ Propose alternatives when disagreeing constructively. +- ๐Ÿšซ Avoid ignoring deadlines or team contributions. -### 9. Fostering Positivity and Inclusion +### 9. ๐ŸŒŸ Fostering Positivity and Inclusion -- Use emoji codes for quick replies and a "compliments jar" in Slack - to recognize contributions. -- During challenging discussions, pause to ensure everyone feels heard. +- ๐Ÿ˜„ Use emoji codes for quick responses. +- ๐ŸŽ Keep a "compliments jar" in Slack to recognize contributions. +- ๐Ÿ™‹ Pause during challenging discussions to ensure everyone is heard. diff --git a/collaboration/communication.md b/collaboration/communication.md index 0ac9fdfa0..d36a74bb1 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -4,50 +4,50 @@ everything you write here will be public so share only what you are comfortable sharing online you can share the rest in confidence with you group by another channel --> -# Communication +# ๐Ÿ“ก Communication --- -## Communication Guidelines +## ๐Ÿ“ Communication Guidelines This document outlines our team's communication practices and expectations. ### **General Principles** -- Communicate clearly and respectfully. -- Keep discussions focused on tasks, challenges, and solutions. -- Use the appropriate channel for each type of communication to maintain efficiency. +- ๐Ÿ—ฃ๏ธ Communicate clearly and respectfully. +- ๐ŸŽฏ Keep discussions focused on tasks, challenges, and solutions. +- ๐Ÿ”„ Use the appropriate channel for each type of communication to maintain efficiency. --- -## Communication Channels +## ๐Ÿ“ฌ Communication Channels Here is how weโ€™ll use our channels: -- **GitHub Issues**: +- **๐Ÿ“Œ GitHub Issues**: - Use issues to track tasks and share updates on progress. - Provide clear, actionable comments when discussing challenges or asking for clarification. -- **Pull Requests (PRs)**: +- **๐Ÿ”„ Pull Requests (PRs)**: - Use PRs to propose changes and review code collaboratively. - Include detailed descriptions of what the PR addresses. - Follow the PR review process: reviewers provide constructive feedback, and authors respond promptly. -- **Slack/WhatsApp**: +- **๐Ÿ’ฌ Slack/WhatsApp**: - Use for quick updates, scheduling calls, or informal discussions. - Use designated threads. -- **Video Calls (Google Meet)**: - - Reserved for in-depth discussions, presentations, or team retrospectives. - - Ensure the agenda is shared as an issue beforehand to make the most - of everyone's time, and share the MoM after the meeting +- **๐ŸŽฅ Video Calls (Google Meet)**: + - Reserved for deep dives, presentations, or retrospectives. + - Share the agenda in advance to respect everyoneโ€™s time. + - Share the ๐Ÿ“ MoM (Minutes of Meeting) afterward --- -## Availability +## โฐ Availability -### **Calling and Messaging Availability** +### **๐Ÿ“ž Calling and Messaging Availability** ### **Team Availability Schedule** @@ -67,6 +67,8 @@ Here is how weโ€™ll use our channels: `โœ“` = Available `โœ˜` = Unavailable +## ๐Ÿ“Š Team Commitment + ### How many hours everyone has per day 1. WuorBhang: _5h_; @@ -79,12 +81,15 @@ Here is how weโ€™ll use our channels: 8. Ibrahim Elmisbah: _2h_; 9. Nahom Tekle: _4h_; -## Asking for Help +## ๐Ÿ™‹ Asking for Help There's a fine line between confidently learning from your mistakes, and stubbornly getting nowhere. Here is a general guide for when to ask for help based on how long you've been stuck on the same problem: -1. _0 -> 60 min_: Try on your own -2. _60 -> 120 min_: Ask your group for help -3. _120+ min_: Tag your coaches in Slack or GitHub +1. ๐Ÿง  **0 -> 60 min**: Try it yourself. You got this! ๐Ÿ’ช +2. ๐Ÿ’ฌ **60 -> 120 min**: Ask your group for guidance. + Teamwork makes the dream work! โœจ +3. ๐Ÿšจ **120+ min**: Tag your coaches on Slack or GitHub. Donโ€™t hesitate! ๐Ÿ‘ฉโ€๐Ÿซ๐Ÿ‘จโ€๐Ÿซ + +Letโ€™s communicate, collaborate, and conquer! ๐Ÿš€ diff --git a/collaboration/constraints.md b/collaboration/constraints.md index af7919554..0416aff0a 100644 --- a/collaboration/constraints.md +++ b/collaboration/constraints.md @@ -1,11 +1,13 @@ -# Constraints +# ๐Ÿšง Constraints -Some boundaries around our project are here now live. +Some boundaries around our project are now live and in action! ๐ŸŽฏ +Letโ€™s stay on track and deliver with focus. ๐Ÿ’ช -## External +--- +## ๐ŸŒ External Constraints +These are the non-negotiables, folks. Letโ€™s roll with them: -**1. Deadline:** Ensure the project is completed and tested before 10th/Jan/2025. +**1. Deadline:** ๐Ÿ•’ Complete and test the project by **12th/Jan/2025**. ๐Ÿ—“๏ธ -**2. Code Review:** The code must pass at least 4 unit tests to be considered complete. +**2. Code Review:** โœ… Code must pass at least **4 unit tests** to be considered complete. -**3. Libraries:** Use only standard Python libraries and `pytest` for testing. +**3. Libraries:** ๐Ÿ“š Use only **standard Python libraries** and `pytest` for testing. -**4. Version Control:** Use Git and GitHub for collaboration. Main branch - protection enabled. +**4. Version Control:** ๐Ÿ”— Collaboration is through **Git** and **GitHub**, with + main branch protection enabled. -**5. Packaging:** Ensure the module is packaged for installation using `setup.py`. +**5. Packaging:** ๐Ÿ“ฆ Ensure the module is packaged for installation using `setup.py`. -## Internal: Involuntary +## ๐Ÿ  Internal: Involuntary Constraints -**1. Daily Time Commitment:** Each team member commits at least 2 hours per day - to work on his/her own project. +1. โณ **Daily Time Commitment**: Each team member dedicates at least + **2 hours/day** to their project. -**2. Hardware:** All team members must use devices capable of running - Python 3.10.0 or higher. +2. ๐Ÿ’ป **Hardware**: All team members must use devices capable of running +**Python 3.10.0+**. -## Internal: Voluntary +## ๐Ÿค Internal: Voluntary Constraints +Hereโ€™s what weโ€™ve agreed upon to scope the project effectively: -**1. Language and Frameworks:** +### ๐Ÿ› ๏ธ **Language and Frameworks** -- Use Python (minimum version 3.10.0). +- ๐Ÿš€ Use **Python** (minimum version **3.10.0**). **(a). Naming Conventions:** -- File names must be in lowercase and use underscores (e.g., `good_fruit_names.py`). +- ๐Ÿ“‚ File names: Must be lowercase with underscores (e.g., `good_fruit_names.py`) -- Testing files must follow the naming pattern `test_.py` (e.g., `test_good_fruit_names.py`). +- ๐Ÿ“‚ Test files: Follow `test_.py` (e.g., `test_good_fruit_names.py`). **(b). Collaboration Tools:** -- Use GitHub Issues and Projects for task tracking. +- ๐Ÿ“‹ Use **GitHub Issues** and **Projects** for task tracking. -- Use Slack for communication. +- ๐Ÿ’ฌ Communicate via **Slack**. -**2. Team Roles:** +### ๐Ÿค **Team Roles** - **(a). Developer:** Writes the main logic for the module. +Everyone plays their part to make magic happen: - **(b). Tester:** Develops unit tests and ensures code coverage. + **(a). Developer:** ๐Ÿ–ฅ๏ธ Writes the main logic for the module. - **(c). Documenter:** Prepares project documentation, including a README.md file. + **(b). Tester:** ๐Ÿ“‹ Develops unit tests and ensures code coverage. - **(d). Reviewer:** Reviews pull requests before merging to the main branch. + **(c). Documenter:** ๐Ÿ“– Prepares project documentation, including a README.md file. -**3. Scope of the Module:** + **(d). Reviewer:** ๐Ÿ” Reviews pull requests before merging to the main branch. + +### ๐ŸŽฏ **Scope of the Module** - Input: A name (string). @@ -85,8 +91,12 @@ Some boundaries around our project are here now live. - Edge cases: Handle special characters, empty strings, and numeric values gracefully. -**4. Documentation:** +### ๐Ÿ“š **Documentation** + +- ๐Ÿ“– Include a **README** file with clear usage instructions + +- ๐Ÿ› ๏ธ Provide **example input and output** for better understanding -- Include a README file with clear instructions on usage. +--- -- Provide example input and output. +๐ŸŽ‰ Letโ€™s stick to these constraints and make our project shine! ๐Ÿš€ diff --git a/collaboration/retrospective.md b/collaboration/retrospective.md index ef1974f8f..ef30b3504 100644 --- a/collaboration/retrospective.md +++ b/collaboration/retrospective.md @@ -1,82 +1,98 @@ -# Retrospective +# ๐Ÿ”„ Retrospective -## Stop Doing +Reflecting on our journey helps us grow stronger as a team! ๐ŸŒŸ +Hereโ€™s what weโ€™ve learned and how weโ€™ll evolve for the next project. ๐Ÿš€ -- Overwriting code during merge conflicts without resolving - them collaboratively. +--- -- Working in isolation for too long without syncing progress with the team. - -- Committing untested code, which led to integration issues. - -## Continue Doing +## ๐Ÿ›‘ Stop Doing + +- โŒ Overwriting code during merge conflicts without resolving them + collaboratively. + +- ๐Ÿ› ๏ธ Working in isolation for too long without syncing progress +with the team. + +- ๐Ÿšซ Committing untested code, which led to integration issues. + +--- + +## โœ… Continue Doing -- Regularly using GitHub to track progress and organize tasks. +- ๐Ÿ“Š Regularly using **GitHub** to track progress and organize tasks. -- Writing clear and descriptive commit messages to improve traceability. +- โœ๏ธ Writing clear and descriptive **commit messages** to improve traceability. -- Sharing updates during team check-ins to stay aligned. +- ๐Ÿค Sharing updates during **team check-ins** to stay aligned. + +--- + +## ๐ŸŒŸ Start Doing + +- ๐Ÿค Implementing a formal process for handling **merge conflicts** collaboratively. -## Start Doing +- ๐Ÿ“† Scheduling more frequent sync sessions to review and integrate changes incrementally. -- Implementing a formal process for handling merge conflicts collaboratively. +- ๐Ÿ” Conducting **mandatory code reviews** before merging changes into the main branch. -- Scheduling more frequent sync sessions to review and integrate changes - incrementally. +- ๐Ÿ“š Writing **modular and well-documented code** to ease collaboration. -- Conducting mandatory code reviews before merging changes into the main branch. +--- + +## ๐Ÿ“š Lessons Learned -- Writing modular and well-documented code to ease collaboration. +- ๐Ÿ’ก **Communication is key** to preventing duplicated efforts and resolving + conflicts efficiently. + +- ๐Ÿ› ๏ธ Merge conflicts are manageable with proper workflows and proactive + resolution practices. -## Lessons Learned +- ๐Ÿ”„ Regular integration reduces the chances of encountering large, complex conflicts. + +- โœ๏ธ Clear documentation helps the team understand and build on each other's work. -- Communication is key to preventing duplicated efforts and resolving conflicts - efficiently. +--- -- Merge conflicts are manageable with proper workflows and proactive conflict - resolution practices. +## โš–๏ธ Strategy vs. Board + +### โœ… What parts of your plan went as expected? + +- ๐Ÿ“‹ Tasks were tracked and organized effectively using **GitHub**. -- Regular integration reduces the chances of encountering large, complex - conflicts. +- ๐Ÿ•’ Milestones were met on time for specific deliverables. -- Clear documentation helps the entire team understand and build on each - other's work. +- ๐Ÿ‘ Most team members followed the planned development workflow. --- -## Strategy vs. Board +### โŒ What parts of your plan did not work out? -### What parts of your plan went as expected? +- โšก Handling merge conflicts wasnโ€™t planned adequately, causing delays. -- Tasks were tracked and organized effectively using GitHub. - -- Milestones were met on time for specific deliverables. - -- Most team members followed the planned development workflow. - -### What parts of your plan did not work out? +- ๐Ÿ”‡ Communication gaps led to duplicated work and inconsistencies in code integration. -- Handling merge conflicts was not planned adequately and caused delays. - -- Communication gaps led to duplicated work and inconsistencies in code - integration. +--- -### Did you need to add things that weren't in your strategy? +### โž• Did you need to add things that weren't in your strategy? -- Introduced a process for resolving merge conflicts and added extra sync - sessions for better coordination. -- Added steps to review pull requests and conduct code reviews before merging. - -### Or remove extra steps? +- ๐Ÿ› ๏ธ Introduced a process for **resolving merge conflicts** collaboratively. + +- ๐Ÿค Added extra **sync sessions** for better coordination. + +- ๐Ÿ” Established steps for **pull request reviews** and mandatory code reviews +before merging. + +--- + +### โž– Or remove extra steps? + +- ๐Ÿšฎ Removed redundant tasks that became unnecessary due to shifting priorities. -- Removed redundant tasks that became unnecessary due to shifting project - priorities. -- Simplified parts of the strategy to focus more on conflict resolution - and integration. +- โœ‚๏ธ Simplified parts of the strategy to focus on **conflict resolution and integration**. --- -This retrospective highlights areas for improvement while celebrating the - team's successes, ensuring better collaboration and outcomes in the next project. +๐ŸŽ‰ This retrospective captures our strengths and areas for improvement, +paving the way for even greater success in future projects! ๐Ÿ’ช diff --git a/solutions/tests/README.md b/solutions/tests/README.md index b78852e4f..4685fa514 100644 --- a/solutions/tests/README.md +++ b/solutions/tests/README.md @@ -1,75 +1,47 @@ -# TESTS FILES README.md +# ๐ŸŽ‰Test Solutions README ๐ŸŽ‰ -## ๐ŸŒŸ**Welcome to the Python Playground** ๐Ÿš€ - -Welcome to the **Tests HQ** where creativity meets problem-solving! -Here, you'll find an epic collection of Python-powered tests, tackling -coding challenges with finesse. - Written by a diverse team of passionate coders, -this repository is the ultimate showcase of - teamwork and innovation. Dive in, -explore, and let the problem-solving adventures - begin! ๐Ÿ’ก -Tests - ---- - -## ๐Ÿ“ **Table of Contents** - -Every solution is a story. Here's what we have for you: - -| ๐Ÿ”ข **#** | ๐Ÿท๏ธ **File Name** | โœ๏ธ **Author** | ๐Ÿ› ๏ธ **Description**| -|----------|-----------------------------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | [test_add_binary.py](./test_add_binary.py) | Abraham Anyak |Test Add and manipulate binary numbers like a pro. ๐Ÿ’ป | -| 2 | [test_calculate_bmi.py](./test_calculate_bmi.py) | Cynthia-Wairimu |Test Calculate BMI and unlock the mysteries of weight categories! ๐Ÿ’ช | -| 3 | [test_double_letter.py](./test_double_letter.py) | WuorBhang |Test Hunt down consecutive duplicate letters using recursion. ๐Ÿ”„ | -| 4 | [test_friend_or_foe.py](./test_friend_or_foe.py) | Cynthia-Wairimu |Test Find your true friends โ€“ filter out the foes! ๐Ÿค | -| 5 | [test_is_even_number.py](./test_is_even_number.py) | Saeed Ali |Test Decide whether a number is even or odd with style. โš–๏ธ | -| 6 | [test_is_prime.py](./test_is_prime.py) | Ibrahim-Elmisbah | Test your number's prime-time status! ๐ŸŒŸ | -| 7 | [test_is_square.py](./test_is_square.py) | WuorBhang |Test Find out if a number is perfectly square. โฌ› | -| 8 | [test_is_unique.py](./test_is_unique.py) | Ava Abdullah |Test Check if a string is truly one of a Test. ๐ŸŒŸ | -| 9 | [test_length_of_longest_substring.py](./test_length_of_longest_substring.py) | SADAM HUSEN ALI |Test Solve the mystery of the longest substring without repeats. โœจ | -| 10 | [test_longest_palindromic_substring.py](./test_longest_palindromic_substring.py) | Nahom Tekle |Test Unravel the longest palindromic substring โ€“ magic guaranteed! โœจ | -| 11 | [Test_max_area.py](./tes_max_area.py) | SADAM HUSEN ALI |Test Determine the maximum area of water a container can hold. ๐ŸŒŠ | -| 12 | [test_most_frequent_character.py](./test_most_frequent_character.py) | Ava Abdullah |Test Identify the most frequent character in a string. ๐Ÿ” | -| 13 | [test_palindrome_checker.py](./test_palindrome_checker.py) | Hasan Zemzem | Spot palindromes โ€“ strings that read the same backward and forward. ๐Ÿ”„ | -| 14 | [test_pascal_triangle.py](./test_pascal_triangle.py) | Nahom Tekle |Test Generate Pascal's triangle โ€“ math never looked so cool! ๐Ÿ”บ | -| 15 | [test_review_date_calculator.py](./test_review_date_calculator.py) | Novel Yonas |Test Plan spaced repetition like a time management wizard! โณ | -| 16 | [test_specific_gravity_calculator.py](./test_specific_gravity_calculator.py) | Novel Yonas |Test CalculaTesthe specific gravity of substances โ€“ science meets simplicity! โš—๏ธ | -| 17 | [test_square_number.py](./test_square_number.py) | Saeed Ali |Test Square numbers like a math maestro. ๐Ÿ”ข | -| 18 | [test_sum.py](./test_sum.py) | Abraham Anyak |Test Compute the sum of two numbers effortlessly. โž• | -| 19 | [test_sum_proper_divisors.py](./test_sum_proper_divisors.py) | Ibrahim-Elmisbah |Test Calculate the sum of proper divisors with mathematical finesse. โž— | -| 20 | [Test_vowel_counter.py](./test_vowel_counter.py) | Hasan Zemzem |Test Count vowels like a linguistic genius! ๐Ÿ”ค | - ---- - -## ๐ŸŒŸ **Why This Repository Rocks** - -- ๐Ÿ **Python Power:** Every test is written in Python โ€“ sleek, modern, -and powerful. -- ๐ŸŒ **Team Collaboration:** Crafted by talented group members from all -walks of life. -- ๐Ÿ’ก **Diverse tests:** From binary operations to palindrome magic -thereโ€™s something for everyone. -- ๐Ÿ“š **Learning Opportunity:** Dig into the code and uncover -pro-level techniques and logic. - ---- - -## ๐Ÿค **Contributing** - -Got ideas? Spotted bugs? Want to make it even cooler? -We welcome all contributions! Open a pull request or start a discussion -in the Issues section. Letโ€™s make this repository even more amazing together! - ---- - -## โš–๏ธ **License** - -This repository is licensed under the MIT License. -Check out the [LICENSE](./LICENSE) file for details. +Welcome to the **Testing Playground**โ€”where bugs fear to tread and code proves +its worth! ๐Ÿ’ป๐Ÿž This isnโ€™t just about testing; itโ€™s about showing your solutions +whoโ€™s boss while having some serious fun. Ready to dive in? ๐Ÿš€ --- -๐ŸŽ‰ **Happy Coding!** -Stay curious, keep learning, and always aim for the stars! ๐ŸŒŒ +## ๐ŸŒŸ Testing Ideas Galore + +Testing isnโ€™t just a choreโ€”itโ€™s an adventure! ๐Ÿง—โ€โ™‚๏ธ Your mission: push each +solution to its limits, find its quirks, and uncover those hidden edge cases. +Each solution has its own personality; letโ€™s get to know them better: + +| **Solution** | **How to Challenge It** | +|------------------------------------- |-----------------------------------------------------------| +| **`add_binary.py`** | Test with large binary numbers . | +| **`calculate_bmi.py`** | Try with extreme heights/weights | +| **`double_letter.py`** | Test with words like `"apple"`, and `"Aaahhh"`.| +| **`friend_or_foe.py`** | Use lists with various names,friends/random.| +| **`is_even_number.py`** | Check with large and small numbers,`0`.| +| **`is_prime.py`** | Test primes, non-primes, and edge case numbers| +| **`is_square.py`** | Test perfect squares & non-squares numbers| +| **`is_unique.py`** | Try words with duplicates.| +| **`length_of_longest_substring.py`** | Test with strings`"abcabcbb"`& empty ones.| +| **`palindromic_substring.py`** | Check with strings like `"racecar"`&`"a"`| +| **`max_area.py`** | Test with random wall heights for area calculation.| +| **`most_frequent_character.py`** | Test with strings of varied lengths.| +| **`palindrome_checker.py`** |Test sentences with punctuation and spaces.| +| **`pascal_triangle.py`** |Check if the triangles are correct | +| **`review_date_calculator.py`** | Test with varied intervals and schedules.| +| **`specific_gravity_calculator.py`** | Validate with liquids, solids, and extremes.| +| **`square_number.py`** | Try `0`, negatives, and perfect squares.| +| **`sum.py`** | Add integers, decimals, and large numbers.| +| **`sum_proper_divisors.py`** | Try primes, composites, and perfect numbers| +| **`vowel_counter.py`** | Count vowels in short/long,mixed-case strings| + +## ๐ŸŽ‰ Make Testing a Blast + +Who says testing canโ€™t be fun? + +- **Compete with Friends:** Who can write the sneakiest edge case ๐Ÿ‘ฏ +- **Bug Hunt:** Spot that one stubborn bugโ€”victory is yours! ๐Ÿ•ต๏ธโ€โ™€๏ธ +- **Celebrate Wins:** When it works, do a little happy dance! ๐Ÿ’ƒ + +Ready to make these solutions shine? Test away, have a laugh, and build some +bulletproof code! ๐Ÿ’ช๐ŸŽŠ