--- title: "Readability Practices" url: "https://courses.osherove.com/courses/tdd-in-net-in-hebrew/readability-practices.md" canonical: "https://courses.osherove.com/courses/tdd-in-net-in-hebrew/readability-practices/" tags: [] author: "Roy Osherove" description: "Lesson 19 of 22 in TDD in .NET in Hebrew (Day 3 - Unit Testing Practices), 1:23. Free video by Roy Osherove." usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # Readability Practices 1. [Courses](https://courses.osherove.com/#courses) 2. [TDD in .NET in Hebrew](https://courses.osherove.com/courses/tdd-in-net-in-hebrew/) 3. Day 3 - Unit Testing Practices Lesson 19 of 22 Duration: 1:23 [Watch on YouTube](https://www.youtube.com/watch?v=QvHaaU5xaoA) Spoken in Hebrew ## In this lesson Roy Osherove recommends ordering tests so that each one changes only one thing in the inputs compared with the test before it, such as one more character in a string, which makes the pattern readable and shows how the feature was built step by step. He sums up his [three pillars](https://livebook.manning.com/book/the-art-of-unit-testing-second-edition/chapter-8 "The pillars of good unit tests (The Art of Unit Testing, 2nd ed., ch. 8)"), tests that are easy to read, easy to maintain and [trustworthy](https://livebook.manning.com/book/the-art-of-unit-testing-third-edition/chapter-7 "Trustworthy tests (The Art of Unit Testing, 3rd ed., ch. 7)"), and calls [TDD](https://livebook.manning.com/book/the-art-of-unit-testing-third-edition/chapter-1#sigil_toc_id_27 "Test-driven development (The Art of Unit Testing, 3rd ed., ch. 1)") almost the only way he knows to see tests both fail and pass, though [bugs in tests](https://livebook.manning.com/book/the-art-of-unit-testing-third-edition/chapter-11 "How can we know we don’t have bugs in our tests? (The Art of Unit Testing, 3rd ed., ch. 11)") can still mislead. ## Transcript 191 words [\[00:02\]](https://www.youtube.com/watch?v=QvHaaU5xaoA&t=2s) לראות טestטים ואני אומר הטestט הזה בא אחרי הטest הזה. כל מה שמשתנה בין הטestט הזה לטסט שמתחתיו זה דבר אחד בלבד. אם משתנים שני דברים באינפוטים, לדוגמה גם האורך וגם פרפרטי אחר, לדוגמה שהוא גם invalid, אז זה הרבה יותר קשה להבין את זה מאשר שיש לי סטרינ ועכשיו ההבדל הוא שהוא בקרקטר אחד יותר. אני רואה פטרה ואני רואה את המהלך הדרגתי שבו אני בודק כל חלק של פיצ'ר. מבחינתity זה מאוד מאוד עוזר עם הטestינג טובים ככה לפעמים אני ממש יכול לעשות טריקבק ולראות את הדרך שבא הפיצ'ר נכתב [\[00:37\]](https://www.youtube.com/watch?v=QvHaaU5xaoA&t=37s) נורא נורא מעניין להסתכל על זה ככה זה גם מאוד קרי אלה בעצם שלושת העמודי התוך מבחינתי של טestינג שקל לקרוא אותם קל לעשות להם מטנס ואני סומך עליהם עכשיו ttd היום זאת הדרך כמעט היחידה שאני יודע כדי באמת לוודא שאני סומך על הטestטים שלי כדי לראה אותם גם במצב של קיש שלו וגם במצב של הצלחה. אמ אבל לפעמים אפילו זה יכול לשקר לי אם יש לי באגים בטestטים וכולי. [\[01:08\]](https://www.youtube.com/watch?v=QvHaaU5xaoA&t=68s) אז גם צריך מאוד להיזהר מהנושא הזה של פאס. בוא נעשה הפסקה של רבע שעה ואחרי זה ניכנס ללגסיקות. כן יש שאלות רבע שעה סק >> רגע ## Related - [Writing readable tests](https://livebook.manning.com/book/the-art-of-unit-testing-second-edition/chapter-8#ch08lev1sec3) · The Art of Unit Testing, 2nd ed., ch. 8 Writing readable tests, the pillar this lesson extends with ordering tests one input change at a time. - [RTM ready tests](https://osherove.com/blog/2009/12/31/rtm-ready-tests.html) · osherove.com A short way to describe tests that are readable, maintainable and trustworthy, the three pillars summed up here. - [Testing the test](https://livebook.manning.com/book/the-art-of-unit-testing-third-edition/chapter-2) · The Art of Unit Testing, 3rd ed., ch. 2 Testing the test: seeing it fail as well as pass, which the lesson says TDD gives you. - [A buggy test gives a false failure](https://livebook.manning.com/book/the-art-of-unit-testing-third-edition/chapter-7#sigil_toc_id_137) · The Art of Unit Testing, 3rd ed., ch. 7 A buggy test gives a false failure, the lesson's warning that bugs in tests can still mislead. ### Also linked in this lesson #### The Art of Unit Testing, 3rd ed. - [Trustworthy tests](https://livebook.manning.com/book/the-art-of-unit-testing-third-edition/chapter-7), ch. 7 - [Test-driven development](https://livebook.manning.com/book/the-art-of-unit-testing-third-edition/chapter-1#sigil_toc_id_27), ch. 1 - [How can we know we don’t have bugs in our tests?](https://livebook.manning.com/book/the-art-of-unit-testing-third-edition/chapter-11), ch. 11 #### The Art of Unit Testing, 2nd ed. - [The pillars of good unit tests](https://livebook.manning.com/book/the-art-of-unit-testing-second-edition/chapter-8), ch. 8 [Previous lesson Maintainability Practices](https://courses.osherove.com/courses/tdd-in-net-in-hebrew/maintainability-practices/) [Next lesson Legacy BlogEngine Project Overview](https://courses.osherove.com/courses/tdd-in-net-in-hebrew/legacy-blogengine-project-overview/) --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/