SunQuest
 
       ASP
  Home arrow ASP arrow Smarter Tools, Dumber Developers?
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Dedicated Servers  
Actuate Whitepapers 
Moblin 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
ASP

Smarter Tools, Dumber Developers?
By: Linda Hayes
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 4
    2003-01-30

    Table of Contents:

    Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT

    Stay one step ahead of the competition. Evaluate and give feedback on some of the hottest web development tools on the market today. Make your opinion heard! Click Here

    Are you better off slowing development down to speed up the testing phase? Linda discusses the implication of using wizards and "quick-development" tools and why we should think twice before using them.I see a train wreck happening in slow motion. Faster development techniques and technologies are crashing into traditional manual testing approaches. No one seems to understand that just because you can develop faster doesn't mean you can deliver faster. The friction factor is testing.

    Look at it this way. If you make any change at all to an application, you run the risk of accidental -- and therefore unanticipated -- breakage. In order to protect operations from potential failure, testing needs to be performed not only for the changes but also all previously existing functionality…So even a 5% development change requires 100% testing.

    Do the math. Do you have 20 testers to each developer and 20 times longer to test than develop? I didn't think so.

    So you have a choice. Deliver dangerous code fast, or safe code slow? Now, you would think that the obvious answer to this conundrum would be test automation, and you would be right. Only automation can replicate all previous tests while testers add new ones within anything approaching a reasonable time frame. But the glaring reality is that most testing is still done manually because automation is too hard.

    And it is probably all your fault. Applications are becoming less and less testable because developers are using less and less discipline. I have seen major, mission-critical Web applications where the pages and objects seem to change names every time you log in -- not that the names were any good to begin with. Button1, text3 and similar names aren't much help, but when they spontaneously become button2 or text2 they are worse than useless -- they are disastrous. When did this swashbuckling approach to programming become OK?

    It's like because new tools use wizards, drag-and-drop functionality and other ways of generating code quickly, the code itself is somehow seen as disposable. I've actually had developers argue that it is easier to just throw code away than to fix it. After all, it only took a few hours, days, weeks or whatever to develop, so who cares?

    Testers, that's who. Disposable code creates disposable tests. To automate a test I have to be able to tell my script how to interact with the application in a way that is repeatable and maintainable. If the application has all the predictability of a dice game, then there is simply no way to ever re-run the same test. Imagine trying to interface to an object where the names of the interfaces, methods and properties all changed often and without warning or meaning. Wouldn't work, would it? But if you can't rerun tests then you can't solve the original dilemma: how to retest previous functionality with the miserly time and resources allocated.

    But where I really go off the deep end is when I raise this issue to developers and they say something like "Well that's just the GUI, so it's not that important", or "The HTML code is dynamic anyway, so it doesn't matter what things are called." As though I am focusing on some trivial, cosmetic aspect that doesn't merit the waste of their valuable time and talent.

    Excuse me? The middle letter in GUI is User, as in the poor person who paid for the software and has to use it. If the interface to the end user is not important, then what is?

    Let me give you a real life example. A major rental car company redesigned their Web GUI for corporate car rentals to adopt a new look and feel. Following the logic that it was just GUI changes and the back end -- where all the real work happened -- was still intact, testing was cursory at best.

    But when they rolled it into production, their corporate customers (think 80% of their revenue) could not rent cars at all. They lost revenue in excess of $25 million, received thousands of hate e-mails, and sustained serious if not permanent damage to key customer relations. Why? Because the GUI was redesigned to change how the renter specified whether insurance was wanted; the old option of Y/N was too cryptic for the new look and the drop-down was changed to Accept or Decline. Too bad the database was expecting Y or N. So the hapless user went through the entire effort to enter all required information, only to get to the very last page and receive an error.

    There are a million other examples I could regale you with, but suffice it to say that unless developers start building applications with some semblance of discipline, we are all going to pay the price. Testing already takes too long and costs too much, and the only way to deliver increasing functionality within collapsing cycle times is to use automation.

    The ultimate irony of all this is that it looks to management as though it is the testers who are bottlenecks, roadblocks or worse. What's wrong with them, anyway? Why does it take them so long when development gets it done so fast? Why can't they get their tests automated? Why are they slowing everything down, are they just lazy or actually stupid? And all the while they are working overtime, tearing their hair out, and puzzling over how a test that ran yesterday won't run today.

    So how about it? Can anyone explain to me how tools can get so much smarter and developers get so much dumber? What do we need, training wheels for wayward developers to keep their code stable enough to be tested? Or am I missing something?

    DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

    More ASP Articles
    More By Linda Hayes

     

    IBM® developerWorks developerWorks - FREE Tools!


    NEW! The dirty dozen: preventing common application-level hack attacks

    As organizations have grown increasingly dependent on online software, the risk of malicious attacks has also become far more serious. Fortunately, well-governed organizations can protect their Web applications by injecting vulnerability assessments and ethical hacks into their software development and delivery processes. This paper describes 12 of the most common hacker attacks and provides basic rules that you can follow to help create more hack-resistant Web applications.
    FREE! Go There Now!


    NEW! Rational Testing eKits

    Discover how Rational tools and best practices for testing can make your job easier. The new Rational Testing eKits provide you with valuable resources – including demos, webcasts, tutorials, and articles – that help you address your specific testing needs across the software lifecycle. Five new eKits are available covering the topics of Requirements and Test Management, Functional Testing, Performance Testing, Code Quality and Embedded Systems, and SOA and Web Services Testing.
    FREE! Go There Now!


    NEW! Trial download: IBM Rational Functional Tester V7.0.1

    Get a free trial download of the latest version of IBM Rational Functional Tester V7.0.1. Rational Functional Tester is an automated functional and regression testing solution for QA teams concerned with the quality of their Java, Microsoft Visual Studio .NET, and Web-based applications.
    FREE! Go There Now!


    NEW! Try the IBM SOA Sandbox for People

    Visit IBM developerWorks to try the IBM SOA Sandbox for people. The SOA Sandbox for people provides a trial environment with the necessary tooling and components required to enable consistent human and process interaction and collaboration, showing how you can improve user experience and business productivity.
    FREE! Go There Now!


    NEW! Using Rational Business Developer to enhance your developer productivity

    Join this Rational Talks to You teleconference, to hear how Enterprise Generation Language (EGL) eliminates the need for tedious and error-prone low level coding, so developers can focus on business requirements. EGL extends the Rational software development platform with a simplified programming language that enables developers who have little or no experience with Java, Web technologies or Service Oriented Architecture, to create enterprise-class applications and services quickly and easily. It also allows developers who may have little or no mainframe programming experience to quickly create traditional mainframe components.
    FREE! Go There Now!


    NEW! Rational Build Forge Express eKit

    Rational Build Forge Express Edition is an automation framework that packages the latest enterprise-grade technologies into a reliable, flexible and robust configuration designed and priced specifically for small to midsize businesses. The new Rational Build Forge Express eKit provides you with valuable resources – including a case study, podcast, demo, and articles – to help you increase staff productivity, compress development cycles and deliver better software, fast.
    FREE! Go There Now!


    Role of Integrated Requirements Management in Software Delivery

    As organizations integrate software into every aspect of business, they are constantly pressured to deliver faster, better, and cheaper results. Unfortunately, a “dis-integrated” software delivery approach reduces returns while increasing costs. This IBM Rational White Paper shows how Integrated Requirements Management aligns organizations around maximizing value and keeping pace with change.
    FREE! Go There Now!


    NEW! Using IBM Rational Developer for System z and IBM Rational ClearCase together to manage application development

    Whether you are creating new applications or modifying existing ones, managing integration of new components with traditional z/OS elements is a critical part of building and deploying modern applications. Listen to this webcast to see how IBM can help you optimize your development process using an IDE like Rational Developer for System z that integrates with management tools, such as ClearCase to manage your application development on mainframes.
    FREE! Go There Now!


    NEW! IBM Rational AppScan Standard Edition V7.7

    Secure your Web applications with IBM Rational AppScan Standard Edition V7.7, previously known as Watchfire AppScan. This Web application security testing tool automates vulnerability assessments and scans and tests for common Web application vulnerabilities. Visit IBM developerWorks to download a free trial of IBM Rational AppScan Standard Edition V7.7.
    FREE! Go There Now!


    NEW! Webcast: Introducing the new Information Server and Solutions community: LeverageInformation

    User communities play an important role in communication and collaboration around products, solutions and other areas of special interest to members. Successful communities are able to provide the right mix of content and services to deliver a value proposition that resonates with each audience. Join Tom Inman, VP of Marketing for Information and Platform Solutions as he introduces the new LeverageINFORMATION community. During this webcast, learn about the value provided by the community and how customers and partners derive value from the community in addressing their own technical and business challenges.
    FREE! Go There Now!



    All FREE IBM® developerWorks Tools!

    ASP ARTICLES

    - Central Scoreboard with Flash and ASP
    - Calorie Counter Using WAP and ASP
    - Creating PGP-Encrypted E-Mails Using ASP
    - Be My Guest in ASP
    - Session Replacement in ASP
    - Securing ASP Data Access Credentials Using t...
    - The Not So Ordinary Address Book
    - Adding and Displaying Data Easily via ASP an...
    - Sending Email From a Form in ASP
    - Adding Member Services in ASP
    - Removing Unconfirmed Members
    - Trapping HTTP 500.100 - Internal Server Error
    - So Many Rows, So Little Time! - Case Study
    - XDO: An XML Engine Class for Classic ASP
    - Credit Card Fraud Prevention Using ASP and C...







    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 2 hosted by Hostway