eXtreme .NET: Introducing eXtreme Programming Techniques to .NET Developers [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

eXtreme .NET: Introducing eXtreme Programming Techniques to .NET Developers [Electronic resources] - نسخه متنی

Neil Roodyn

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید












User-Interface Testing


An excuse I often hear in my line of work is this: "It is not possible to use the practices because we build user-interface code." This chapter dispels that myth by introducing you to techniques to develop better user-interface code. These techniques enable you to test your user-interface code. I include additional ideas about test-driven development as well as cover some refactoring techniques.


It's Not Possible!


It seems like a human trait to find an excuse why something is not possible and therefore cannot be applied. This seems especially true when people do not see the reasoning behind doing something. Many of the XP techniques at first don't seem to add up to a sensible option for developing software. I have found the only way to prove whether something makes sense is to try it. After I have tried something, I can make a judgment as to its validity for the software I am developing. Reserve your belief that it is not possible until you have tried some of the exercises in this chapter. Then see whether you can see how to apply these ideas to your everyday project.


"We Are a Special Case"


"We are a special case" is another of the common cries I hear as an excuse as to why it is not possible to develop testable user-interface code. In my experience, most development teams are doing something reasonably special and different; that's why they are getting paid. If most teams are doing something different, does that mean they are all special cases?

The trick is to work out how to use a best practice to your advantage in the "special case" code you are developing. Let's examine some of the issues with user interfaces and then try some exercises. Then this chapter shows you how to write software with user interfaces that is more testable and therefore gives you more confidence in its correctness.


    / 117