AscentialTest by Zeenyx

    By: Bruce Armstrong on Aug 01, 2013

    In this article, we’re going to take a look at a new automated testing tool that supports PowerBuilder. But, before we dive into that, a bit of history.

    Data Window Dilemma
    One of the many advantages of the DataWindow control in PowerBuilder is that at runtime the DataWindow isn’t a large collection of rows, columns and other objects (e.g., command buttons). Instead, what PowerBuilder does is renders the DataWindow as two controls no matter how complex the underlying DataWindow object is: a bitmap and a floating edit control. The bitmap shows the user the visible controls from the DataWindow object, and the edit control floats above whichever control currently has focus and handles data entry.

    This behavior of the DataWindow was particularly important in situations in which a lot of rows and columns were being displayed. Typical Window applications written in a tool like Visual Basic would render them as individual controls, each of which used a GDI handle. Visual Basic developers had to deal with operating system default limits on the number of GDI handles a single application could use as well as GDI leaks. Using a large number of GDI handles also consumed a lot of memory and slowed down the application. PowerBuilder developers don’t have to deal with any of that.

    However, this feature of the DataWindow caused a problem when you wanted to use an automated testing tool to create quality assurance testing scripts for your application. Most such tools determine how to interact with the application by getting the GDI handle to the controls in the applications. They can’t do that directly with the DataWindow control, making it difficult for most quality assurance testing tools to work adequately with PowerBuilder. Normally the only option would be to record cursor coordinates on the bitmap, which is hardly ideal. Without the ability to query the DataWindow for rows that meet certain criteria to be used for the test and then later examine the data to ensure that updates worked correctly, the usefulness of such testing scripts would be significantly reduced.

    Login to read the article. Not a member? Create a free account!

    Released: August 1, 2013, 9:50 am | Updated: January 27, 2014, 6:30 pm
    Keywords: PowerBuilder Article | Technical Journal | Bruce Armstrong | DataWindow | Development | PowerBuilder | Test Automation | Zeenyx


     

     

    TwitterLLinkedinLFacebook

    Copyright © 2014 ISUG-TECH. All Rights Reserved
    All material, files, logos and trademarks within this site are copyright their respective organizations

    Terms of Service - Privacy Policy - Contact the Help Desk