How do I start the Tennis Refactoring Kata in Java?

Clone the repository, navigate to the Java directory, and run the tests with your preferred IDE or build tool. Start with TennisGame1 as suggested to practice refactoring incrementally.

What are the most common code smells in this kata?

Look for hard-coded values, duplicated logic, and complex conditional structures. The kata intentionally includes these to give you specific issues to identify and refactor.

Tennis Refactoring Kata vs Gilded Rose: which is better for learning?

Tennis is more focused on a single domain with clear rules, making it easier for beginners. Gilded Rose has more complex requirements, so Tennis is better for foundational refactoring practice.

Can I use this for team training workshops?

Yes, it's excellent for team exercises. The multiple implementations allow members to compare refactoring approaches and discuss code quality improvements in a controlled setting.

How long does it take to complete one implementation?

Typically 1-2 hours per implementation, depending on your experience. The scenario suggests spending about an hour, making it suitable for short, focused practice sessions.

What programming languages are supported?

The GitHub repo includes implementations in languages like Java, C#, Python, and JavaScript. Check the subdirectories for specific versions and setup details.

Open-Awesome

Tennis Refactoring Kata

MITTypeScript

A refactoring exercise based on tennis scoring rules to practice improving existing code.

Visit Website GitHub

816 stars1.4k forks0 contributors

What is Tennis Refactoring Kata?

Tennis Refactoring Kata is a practice exercise where developers refactor existing code that implements tennis scoring rules. It simulates a real-world scenario of taking over a colleague's work, with multiple flawed implementations to clean up while keeping tests passing. The goal is to improve code design and maintainability without altering functionality.

Target Audience

Software developers, coding bootcamp participants, and teams looking to practice refactoring techniques, code reading, and test-driven development in a controlled environment.

Value Proposition

It offers a safe, structured way to hone refactoring skills with fast, comprehensive tests and multiple starting points. Unlike generic exercises, it includes realistic design flaws and guided resources, making it ideal for learning through hands-on correction.

Overview

This is a Refactoring Kata based on the rules of Tennis

Use Cases

Best For

Practicing test-driven refactoring on a small, focused codebase
Learning to identify and fix common code smells like hard-coded values
Improving code reading skills with guided scanning exercises
Workshops or coaching sessions on software craftsmanship
Preparing for technical interviews that involve legacy code tasks
Team exercises to discuss code quality and refactoring strategies

Not Ideal For

Developers seeking a production-ready tennis scoring library for immediate integration
Teams focused on learning new programming syntax without prior codebase context
Projects requiring rapid feature development over code quality exercises

Pros & Cons

Pros

Multiple Implementation Variants

Includes several versions like TennisGame1 and TennisGame3, each with unique design smells, providing diverse practice scenarios for refactoring.

Comprehensive Test Suite

Fast-running tests verify correctness, enabling test-driven refactoring and ensuring no behavior changes during improvements, as highlighted in the README.

Realistic Work Scenario

Simulates taking over a colleague's incomplete work with billable hours, adding practical context to the refactoring exercise.

Guided Learning Resources

Offers video demos and exercises like 'Scanning for Code Smells' to build code reading and refactoring skills, as linked in the README.

Cons

Niche Problem Domain

Focused solely on tennis scoring logic, which may not directly apply to refactoring challenges in other business domains or complex systems.

Artificially Inserted Flaws

Deliberate errors like hard-coded player names are simplified and may not reflect the nuanced, emergent issues found in real legacy codebases.

Limited Setup Guidance

While tests are provided, the README lacks detailed instructions for environment setup in all languages, potentially hindering beginners.

Frequently Asked Questions

Related Projects

The Quantum Katas

Tutorials and programming exercises for learning Q# and quantum computing

Stars4,854

Forks1,247

Last commit1 year ago

Gilded Rose - Many languages

Starting code for the GildedRose Refactoring Kata in many programming languages.

Stars4,222

Forks6,010

Last commit2 months ago

Git katas

A set of exercises for deliberate Git Practice

Stars1,640

Forks1,073

Last commit3 months ago

RPG Game kata

My list of code katas

Stars768

Forks235

Last commit2 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub