From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19802 invoked by alias); 13 Feb 2007 21:27:05 -0000 Received: (qmail 19794 invoked by uid 22791); 13 Feb 2007 21:27:05 -0000 X-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 13 Feb 2007 21:26:58 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l1DLQlDr014622; Tue, 13 Feb 2007 16:26:47 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1DLQliZ028164; Tue, 13 Feb 2007 16:26:47 -0500 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1DLQk9r030985; Tue, 13 Feb 2007 16:26:46 -0500 Message-ID: <45D22D0D.10803@redhat.com> Date: Tue, 13 Feb 2007 21:27:00 -0000 From: Andrew Cagney User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: Kris Van Hees CC: frysk@sourceware.org Subject: Re: frysk ui concall References: <45CA94F2.2000707@redhat.com> <20070212211157.GA14346@ca-server1.us.oracle.com> In-Reply-To: <20070212211157.GA14346@ca-server1.us.oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00120.txt.bz2 Kris, You asked about accessibility, two pieces of background that might help clarify what is going on: - frysk is using JUnit for unit-level testing For instance frysk-gui contains a test to verify that the paths to the files required by the UI are all valid. - frysk is using DOGTAIL for UI testing (a.k.a. integration testing) For instance, sequencing through the operation of selecting a set of process and monitoring them, thus ensuring that the entire frysk program works as expected. In the latter case, DOGTAIL uses accessibility information to identify and control widgets. So in addition to the obvious reasons, accessibility is important to frysk as it allows us to pursue automated testing. More information on DOGTAIL is available here: http://people.redhat.com/zcerza/dogtail/ And you can run the dogtail tests with /usr/lib/frysk/ftail. Andrew