Topic
  • 3 replies
  • Latest Post - ‏2007-04-09T22:27:42Z by SystemAdmin
SystemAdmin
SystemAdmin
210 Posts

Pinned topic testing tools and methods for UI

‏2007-03-28T20:03:38Z |
any suggestions on the systematic testing of ui and systems that require real time interaction with custom devices and users at the same time?
Updated on 2007-04-09T22:27:42Z at 2007-04-09T22:27:42Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    210 Posts

    Re: testing tools and methods for UI

    ‏2007-04-02T22:00:15Z  
    Hello,

    > any suggestions on the systematic testing of ui and
    > systems that require real time interaction with
    > custom devices and users at the same time?

    What do you mean by [i]custom devices[/i]? About systematic: There are different approaches to be systematic:

    • Whitebox Tests: For every UI component go through the code and try to
    write UI tests which follow each possible path through the code. This
    is good for code coverage but is hard to realize for huge untested
    legacy code.

    • Use Case Oriented: Define common Use Cases and build automatic tests for
    them.

    • Regression Tests for fixed bugs: Every time you fix a bug write a
    regression test that will detect this bug and ensure that it is
    green after the bug fix.

    The last two are applicable especially for untested legacy code. I am sure there are more, but these are the three I currently think of.

    As tool I currently prefer qftest by QFS (http://www.qfs.de/). It's easy to understand, it's written in Java and it has great support for data driven testing which eases getting a good code coverage of tests in a short amount of time.
  • SystemAdmin
    SystemAdmin
    210 Posts

    Re: testing tools and methods for UI

    ‏2007-04-03T16:43:30Z  
    Hello,

    > any suggestions on the systematic testing of ui and
    > systems that require real time interaction with
    > custom devices and users at the same time?

    What do you mean by [i]custom devices[/i]? About systematic: There are different approaches to be systematic:

    • Whitebox Tests: For every UI component go through the code and try to
    write UI tests which follow each possible path through the code. This
    is good for code coverage but is hard to realize for huge untested
    legacy code.

    • Use Case Oriented: Define common Use Cases and build automatic tests for
    them.

    • Regression Tests for fixed bugs: Every time you fix a bug write a
    regression test that will detect this bug and ensure that it is
    green after the bug fix.

    The last two are applicable especially for untested legacy code. I am sure there are more, but these are the three I currently think of.

    As tool I currently prefer qftest by QFS (http://www.qfs.de/). It's easy to understand, it's written in Java and it has great support for data driven testing which eases getting a good code coverage of tests in a short amount of time.
    Thanks for the pointer to QFS!
  • SystemAdmin
    SystemAdmin
    210 Posts

    Re: testing tools and methods for UI

    ‏2007-04-09T22:27:42Z  
    Hello,

    > any suggestions on the systematic testing of ui and
    > systems that require real time interaction with
    > custom devices and users at the same time?

    What do you mean by [i]custom devices[/i]? About systematic: There are different approaches to be systematic:

    • Whitebox Tests: For every UI component go through the code and try to
    write UI tests which follow each possible path through the code. This
    is good for code coverage but is hard to realize for huge untested
    legacy code.

    • Use Case Oriented: Define common Use Cases and build automatic tests for
    them.

    • Regression Tests for fixed bugs: Every time you fix a bug write a
    regression test that will detect this bug and ensure that it is
    green after the bug fix.

    The last two are applicable especially for untested legacy code. I am sure there are more, but these are the three I currently think of.

    As tool I currently prefer qftest by QFS (http://www.qfs.de/). It's easy to understand, it's written in Java and it has great support for data driven testing which eases getting a good code coverage of tests in a short amount of time.

    > What do you mean by [i]custom devices[/i]?

    Thank you for your comments. To be specific a project i am working on requires a pocket pc to interact with a proprietary device using raw infrared serial communication. That means that besides the pure logic aspect of the application there are timing issues that need to be tested. Furthermore, in an event based approach there are multiple threads servicing possible events and the user may try a nonsensical sequence of operations and the UI dynamically activates and deactivates controls depending on context. my question was about methods to take all these factors into account