Ir al contenido principal

unit testing

  1. Forgetting Red to Green
  2. Poor Naming Conventions
  3. Unclear purpose
  4. Code Organization
  5. Unit vs Integration Test Confusion [24:06]
  6. No Code Coverage on Exceptions
  7. Giving Up On The User Interface [50:04]
  8. Fixing Bugs Without Unit Tests
  9. Useless Code Coverage
  10. Stop Mocking Me!
Bonus:
  • Giving Up On Legacy Apps
  • Un-testable Architectures
  • Not Doing Interface-Driven Programming
  • Not Doing Dependency Injection

Phrases...

  • QA's Are People Too... you'll really should treat them ... they are human beens [53:00]
  • Just because you have 100% code coverage, doesn't mean that your code works. It only means that you've executed every line. (Scot Hanselman).









Get Microsoft Silverlight



http://www.msteched.com/2010/NorthAmerica/DPR204


Etiquetas:

Comentarios

Publicar un comentario

Entradas populares de este blog

GNUstep ProjectCenter/Gorm/AClock running Ubuntu 10.04

Download sources GNUstep (stable or unstable) to compile; Dependencies First you need to check dependencies in ubuntu and install with sudo apt-get or search before with apt-cache command; almost every package ends with *-dev in ubuntu repositories this command will install all dependencies for compile: ~$ sudo apt-get install libffi-dev libssl-dev libxml2-dev libxslt1-dev libcairo2-dev libxt-dev GNUstep Make compiling GNUstep make is our first target; it's the primary package to compile GNUstep applications. get the package, untar and change into the folder and compile: ~$wget ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-make-2.4.0.tar.gz ~$tar xzvf gnustep-make-2.4.0.tar.gz ~$cd gnustep-make-2.4.0/ ~$./configure --prefix=/usr/local/GNUstep/ --enable-native-objc-exceptions ~$make ~$sudo make -E install *NOTE: the options /usr/local/GNUstep/ is the folder where all the GNUstep is going to install. the second option --enable-native-objc-exceptions enable th...
1 comentario
Leer más

Capacitación en línea

Python, uno de los lenguajes soportados en la GoogleApps beginning: python , ShowMeDo . jQuery commercial screencast: Peepcode.com SharePoint 2010, la tecnología de mayor crecimiento en micro$oft intro: Building Solutions on SharePoint 2010 SharePoint 2010 Beta Developer Center Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008 CriticalPath Technical Articles Driving SharePoint adoption SharePoint Server 2010 capacity management: Software boundaries and limits Learning Snack for Developers: Developing Solutions with Microsoft SharePoint 2010 (20 min) Experiencing the Microsoft SharePoint Server 2010 User Interface (20 min) Managing and Troubleshooting with Microsoft SharePoint Server 2010 (17 min) Microsoft eLearning: Clinic 10277: What's New in Microsoft SharePoint 2010 for Developers SharePoint 2010 for Internet Sites Implementers' Course Developing on SharePoint 2010 Getting Sta...
Publicar un comentario
Leer más

meta:progid

The meta:progid attribute on the Page directive is necessary if the page will ever be opened in SharePoint Designer. You should include this as site pages are supposed to support customization and thus, be opened in SharePoint Designer. If you don't want to allow pages to be opened and customized in SharePoint Designer, then you should do that through permissions, not at the page level. Using ASP.NET 2.0 Code Behind Files in SharePoint v3 Sites SPFile.ProgID gets a string that identifies the application in which the file was created. That's all the meta:progid is about. It's a identifier for SharePoint and you probably should not use other attributes, they might cause run-time error. Ref: msdn forum thread explanation
Publicar un comentario
Leer más