How tiagotakahashi/tdd_interpretadornumerosromanos works
Project type and purpose
• This is a small, library-style tool (“InterpretadorNumerosRomanos”) implemented in C#/.NET, whose sole purpose is to parse and convert Roman numerals into integers.
• It follows a TDD (test-driven development) approach, as evidenced by the separate test project (“InterpretadorNumerosRomanosTestes”).
File structure
• Top level:
• InterpretadorNumerosRomanos.sln — Visual Studio solution file.
• InterpretadorNumerosRomanos/ — class-library project containing core interpreter logic.
• InterpretadorNumerosRomanosTestes/ — test project containing unit tests.
• Key code file: Interpretador.cs (holds the class/method that does the interpretation).
• No external services or data stores are present—this is a pure in-memory converter.
README
• Only one line: “TDD_InterpretadorNumerosRomanos.”
• Implies that the architecture is minimal: core library + tests.
a. Main components
• “Core Library” (InterpretadorNumerosRomanos assembly)
• Classes/Modules:
– RomanNumeralParser (tokenizes input string)
– RomanToIntegerConverter (applies rules & computes value)
– RomanNumeralValidator (checks for illegal sequences)
• “Test Suite” (InterpretadorNumerosRomanosTestes assembly)
• Test fixtures (e.g., Teste.cs) that validate parser, converter, and validator.
b. Relationships & interactions
• Parser ➔ Validator (ensures syntax correctness)
• Parser ➔ Converter (feeds validated tokens for numeric calculation)
• Converter returns integer result to Client Code.
• Test Suite exercises all three components (Parser, Validator, Converter) with green‐red refactoring loops.
c. Architectural patterns & design principles
• TDD cycle: tests drive implementation
• Single Responsibility Principle: separate parsing, validation, conversion
d. Technologies & frameworks
• .NET/C# class library
• MSBuild (.csproj)
• MSTest or NUnit (whichever target framework is in the Testes project)