Learn Unit Testing and Improve Sexual Performance
Download as PPT, PDF0 likes461 views
The document discusses unit testing and test-driven development (TDD), providing opinions both for and against TDD. It notes that while TDD helps ensure code is tested, some argue it should not dictate overall design and developers should decide when to write tests. The document also lists resources about TDD best practices and debates on its effectiveness.
Learn Unit Testing and Improve Sexual Performance
- 1. Learn Unit Testing and Improve Sexual Performance bacfug 11.19.08 MXUnit.org
- 2. “ Just wait will ya? I ’ m in the middle of running a test suite! ”
- 3. “ Continuous Integration so totally r0x0r!”
- 4. We test because we don't trust. Why test?
- 5. Trust This?
- 6. “ I hope that was hours and not days, Tim. ”
- 7. Testable apps are agile .
- 8. “ I like agile, Timmy …”
- 9. “ You ’ re lucky to still have your job, douche bag. ”
- 10. Good designs are testable.
- 11. Simplify
- 12. Feedback
- 13. Bad
- 14. Good
- 15. TDD Controversy
- 16. ” ... it has become infeasible ... for a software developer to consider himself professional if he does not practice test driven development. ” - ” Uncle ” Bob Martin ObjectMentor
- 18. "TDD is a good practice to keep you honest about writing tests, but it should not be the dictator of your design. Writing tests should be a priority, but whether you write these tests first or last remains a decision that only you, the developer, can make." -Cedric Beust TestNG
- 19. Just Test
- 20. Use the right tools
- 21. Test And Be Happy http://mxunit.org
- 22. Resources InfoQ : Coplien and Martin Debate http://www.infoq.com/interviews/coplien-martin-tdd I nfoQ: Design for Testability (Cedric Beust) http://www.infoq.com/interviews/beust-designing-testability T he Flawed Theory Behind Unit Testing (Michael Feathers) http://michaelfeathers.typepad.com/michael_feathers_blog/2008/06/the-flawed-theo.html MXUnit http://mxunit.org
Editor's Notes
- #2: The title slide will be intentionally distracting while we introduce ourselves. MXUnit, where we're from Our first job is writing software. We are hardcore testers Bill – US Treasury off-duty, just in case I ’ m being followed … fuck you … ear-wax What ’ s so funny? Ajax is sexy, right? But, did you know that even though JQuery and ExtJs are sexy, Unit Testing is Hot . Really …
- #3: This is Jan, a guy recently mentored by Marc Esher
- #4: A Ed and Tammy who met on the mxunit google group
- #5: Soap box talk about why testing is important then we ’ ll show the cool toys and tools to play with. Seems like an obvious question, but really consider it … Why don ’ t we just write our code and ship it? Why are automated tests better? Yet, we test all the time in life.
- #6: Nice UI! Not beating up at all on this. It ’ s really slick. But we don ’ t know what we ’ re getting into. Many organizations only value what they can see and what they can get out the door. Now what's under the hood. Yeah it looks good, but how quickly can we change it? Are there any defects? How is it tested? Many companies see the UI look slick, or the output/end result is what they want, but when they need changes done quickly and you say, well, that ’ s going to take some time …
- #8: Testing is more important to developers and smart organizations. Why? Your tests are automated and touch many parts of your application. They are also fast. So, when making changes, you can run your test suite and get immediate feedback.
- #9: Dream on, code monkey …
- #10: Ah, this is more like it. This is my boss.
- #11: Testability naturally leads to good designs.
- #13: Many organizations only value what they can see. Testing is more important to developers and smart organizations. Many companies see the UI look slick, or the output/end result is what they want, but when they need changes done quickly and you say, well, that ’ s going to take some time …
- #20: Many organizations only value what they can see. Testing is more important to developers and smart organizations. Many companies see the UI look slick, or the output/end result is what they want, but when they need changes done quickly and you say, well, that ’ s going to take some time …
- #21: Cut out the crap. Refactor.