
	Where results make sense

Topic: GUI testing

Related Topics

Graphical user interface

In the News (Wed 16 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	GUI Testing: Pitfalls and Process
		Testing GUI's is different from testing regular software because typical software testing uses test coverage criteria as a guideline, but this does not work with GUI's because the GUI software is different from the underlying application code and mapping GUI events to the application code is not simple or straightforward.
		In GUI testing the oracle is invoked during the test execution because the GUI state can end up with an unexpected screen, which may make further testing impossible or useless until the current problem is solved.
		Testing GUIs is different than testing a program because when you test a program, you have guidelines to follow such as code coverage.
	cs.allegheny.edu /wiki/cs290F2002/50 (1126 words)

	TWiki . Javapedia . TestingGUIApplications
		GUI applications are expensive to test because their nature involves human interaction which tends to require manual testing (high expense).
		That is, because the Windows platform has a wide choice of GUI test automation tools, this means applications developers for Windows can afford to do more testing, and as a result it's likely they'll find more bugs in their application.
		Depending on your testing goals the push AWT events into the queue model may be enough for you, just know that your test will not be "complete" in that it will not cover the whole AWT "stack".
	wiki.java.net /bin/view/Javapedia/TestingGUIApplications (1115 words)

	ITworld.com - Testing GUI applications, part 1
		A good test plan makes explicit not only what happens when everything is going well, but also what happens when the user asks for something silly or makes an impossible selection, or when the network goes down, or when a system administrator forgets to renew an authentication value in a permissions table.
		Regression tests are essential for many products, and vendors have quite a few satisfied customers, despite their steep licensing fees (often over $10,000 to start) and uneven technical support.
		Management of a test suite is so much different in the two modes that they generally should be considered as two distinct categories: record-and-playback testing tools and scriptable testing tools.
	www.itworld.com /AppDev/1262/UIR010316testinggui1 (2824 words)

	Gui Testing
		The constraints on developing GUIs which fit the framework annoy new GUI developers, who complain to their managers that the coding rules are uselessly delaying their projects and forbidding their use of the most recent GUI technology.
		No one is maintaining the GUI regression test suites (see RegressionTesting) nor the environment/test apps which run them, which therefore become quickly obsolete....
		This seems to be a harder problem than GUI testing in general, because often with GUI testing the layout isn't a huge concern; rather, you just want to verify the interactions between components, and that can be done by watching events and similar strategies.
	c2.com /cgi/wiki?GuiTesting (3868 words)

	GUI Localization and Testing
		You need to edit the GUI content in order to make sure that the application's windows, dialogs, and other GUI pieces have the correct appearance after their text language content has been translated.
		The GUI pieces of the application reside in files with the extension "nib".
		Test your application and go back to editing strings as well as nib files to fix any problems you may encounter.
	developer.apple.com /internationalization/localization/gui.html (574 words)

	JavaGu(i)(y): Java GUI Testing
		I need the gui testing for nyx, which depends on swing and swt (swt is a work in progress thougb, which currently breaks nyx completely).
		My goal with gui testing is to also test things that are under the covers in eg swing.
		For now my conclusion is that gui testing is way too bad to be usefull and not very timesaving, especially when there is a fast rate of changing the gui itself.
	weblog.isallineed.net /javagui/archives/000023.html (314 words)

	ITworld.com - Testing GUI applications, part 2
		The most important natural test of the application is one that validates the value of the display.
		We'll make the GUI elements very simple, so simple that they can be designed correctly and validated easily "by hand." The full power of "classical" command-line testing verifies the textual parts.
		We're done; we've reduced the problem of testing this GUI application to the two simpler problems of testing a purely textual, or "command line" part, and a very thin, purely automated GUI part.
	www.itworld.com /AppDev/1243/UIR010323testinggui2 (1890 words)

	ONJava.com -- Agile User Interface Development
		Tests that exercise the GUI can be tedious and error-prone, involving complex code to simulate user events, wait while events propagate and controls redraw, and then attempt to check the state as it would appear to the user.
		The functional application behavior is covered by unit tests, and the generic display code doesn't require complex GUI tests.
		One thing about this pattern, is that it won't cut all unit test to the form, but it would more easily decouple those between the functionality of the form and those specific to the user interaction with the form itself.
	www.onjava.com /pub/a/onjava/2004/11/17/agileuser_1.html (2853 words)

	Extreme Java GUI Testing
		TestCase implements the Test interface and provides the methods to set up the test condition, run tests, collect the results, and tear down the tests once they are complete The TestResult class is used to collect the results of a TestCase.
		If you wanted to use the Robot class to test Swing applications, you would have to create an additional API that could be used to find the location of the components that you want to test.
		If you were to test this Swing application, what you would do is to start the application, type some text into the top field, then press the Copy Text button and make sure the text in the two fields matched.
	www.developer.com /java/other/article.php/1016841 (1492 words)

	KwikPeg GUI Testing
		The procedure followed to test a stand-alone application GUI is similar to that described for building the KwikPeg examples.
		The procedure followed to test an AMX application GUI using TAPS is similar to that described for testing a stand-alone GUI application.
		Hence, when your GUI is moved to the target hardware with a video screen driver derived from the template, display discrepancies will probably be attributable to your custom, controller-dependent code sequences in the modified driver.
	www.kadak.com /manual/kwikpeg/kpg_ref/html/kdkp1930.htm (1699 words)

	redhat.com \| Automated GUI testing with Dogtail
		If you've ever had to create automated tests for your applications' GUI, then you've generally been in luck, as there are several fine test packages to choose from--provided, of course, that you're working on Windows® and have lots of money to throw at the problem.
		One of the main functions of any GUI testing framework is the identification of the elements in the GUI.
		It's possible to locate and identify GUI elements by their X and Y matrix coordinates, but this approach is limited by the requirement that the GUI layout not change.
	www.redhat.com /magazine/020jun06/features/dogtail (2555 words)

	GUI Designers - Usability Testing and Evaluation Services
		Effective usability testing is based on a clear understanding of your application's or web site's business goals and user population.
		Testing is performed with at least six users.
		Following the completion of usability testing, GUI Designers prepare a report that details our findings and provides recommendations on how to improve your user interface.
	www.gui-designers.co.uk /testing/testing.htm (318 words)

	Software Quality Assurance Testing and Test Tool Resources
		Testers simply enter test data into a spreadsheet which is used to populate the objects that appear for the particular test scenario defined.
		Tests can be contained in a single file and each test can be configured to connect to different data sources.
		The same test suite used for server functional testing can also be used as a load test suite that not only monitors the servers response rate with the specified number and mixture of simultaneous requests, but also verifies whether the test loads cause functionality problems.
	www.aptest.com /resources.html (9630 words)

	SQAtester.com - Testing GUI
		GUI standards may vary from company to company and also from application to application.
		Validation testing mainly depends on the fields set in the dialog box and the functions it has to perform.
		The first step to test the Functionality aspect of the Application is to check whether all the requirements are covered in the software.
	www.sqatester.com /methodology/testingGUI.htm (1312 words)

	The GUITAR Project
		Software testing is a critical component of the software development process and is required to ensure the safety, robustness and usability of software.
		Second, we strongly encourage GUI testing researchers to use GUITAR as a forum to collaborate, share results and ideas so that we all can get a better understanding of the problems of GUI testing and develop better solutions.
		If you perform GUI testing and/or are interested in GUI testing research and would like to be a part of the GUITAR group, please send an e-mail.
	www.cs.umd.edu /~atif/GUITARWeb (314 words)

	The weblog from Thomas Boshell
		The point is that seeing the to-test GUI map structure is an invaluable test tool for varification, test navigation, and diagnostics and tools that dismiss this out-of-hand are chopping themselves off at the knees.
		Since, they are often not techies a good GUI map tool is the guide that allows them a deaper insite into the application being testes, how it is built and reacts, and what properties are available to be tested without looking into the source code.
		Some GUI map implemenations are obviously not worth the effort; however, if it is feature rich, presents the GUI map in a heirarchial structure (like the DOM structure), allows for run-time analysis (inspection), and can be used to test--then it would be a valuable addition to your tool set and worth contemplating.
	jroller.com /page/tomboshell?entry=of_what_use_are_gui (1502 words)

	Bazman's Testing Pages
		Important considerations if you are thinking about implementing the "holy grail" of testing.
		Why testing CANNOT ensure quality and What is the difference between testing, quality, quality assurance anyway?
		Why you should consider outside help when planning for your next testing cycle.
	members.tripod.com /~bazman (110 words)

	perl.com: Test-Driving X11 GUIs
		Interfaces to GUI applications like DCOP or D-BUS allow you to interact with GUI applications in order to get at their internal states or set some arbitrary states.
		If you're writing such an application, you need some sort of regression tests for it to make sure your widget/windows are as accessible as they should be.
		One is tested.pl and it serves as an example GUI.
	www.perl.com /pub/a/2006/02/02/x11_gui_testing.html (557 words)

	KDE Edition of GUI Testing Tool Squish (Site not responding. Last check: 2007-11-03)
		Squish/KDE is a free of charge edition of the Qt GUI testing tool Squish to create and run tests on applications developed for the popular K Desktop Environment.
		But if these tests become part of official KDE test suites (as implied by the quotation from Adriaan), then to be an effective developer, or even bug reporter in some cases, you would indeed be forced use this software.
		And the tests are not just an optional help -- there was some large refactoring work I was involved in recently that depended massively on the test suite and have been just about impossible without it.
	dot.kde.org /1152025382 (2396 words)

	qa: The OpenOffice.org Automated GUI Testing Project
		The automated GUI testing provides a test framework with test scripts and an application (VCL TestTool) to test almost the whole office application automatically.
		To start the GUI testing it is recommended to download the scripts (TestTool Environment) and the VCL TestTool application for the platform where you want to run the tests.
		All scripts needed for testing the OOo 2.0.x with the VCL TestTool are available from CVS in the project: qa/qatesttool.
	qa.openoffice.org /qatesttool (585 words)

	GUI Testing Homepage
		Error detection and reproduction was always real challenges to the tester, because the tester must be able to remember the steps he or she took to trigger the error.
		Every point and click applied to the GUI application is recorded in a test script that is in C-like Test Script Language (TSL).
		This allows the tester to reproduce and generate modularized test scripts for the GUI application.
	www-mipl.jpl.nasa.gov /it/gui.html (177 words)

	JDC Tech Tips: July 11, 2000
		Imagine that you have a Java GUI program written using the AWT and Swing libraries, and you'd like to automate the program.
		For example, you'd like to automatically supply GUI input events from the keyboard and mouse to the program.
		This type of automation might be useful for testing purposes, or to produce a self-running demo program.
	developer.java.sun.com /developer/TechTips/2000/tt0711.html (1046 words)

	JUnit, Testing Resources for Extreme Programming (Site not responding. Last check: 2007-11-03)
		Abbot is a scripted Java GUI testing framework that supports recording and playback of semantic user events, as well as component state evaluation for both unit and functional testing.
		Jemmy is a Java library that is used to create automated tests for Java GUI applications.
		An extension to the JUnit framework that enables you to execute unit tests against code that presents a Swing based interface.
	www.junit.org /news/extension/gui/index.htm (275 words)

	Mercury Functional Testing - Functional Test and Regression Test Automation Software (Site not responding. Last check: 2007-11-03)
		Functional Testing from Mercury combines Mercury's functional testing products, Mercury QuickTest Professional and Mercury WinRunner, to deliver the industry's most complete software quality solution for automated functional testing, GUI testing and regression testing.
		Mercury Functional Testing™ combines Mercury’s functional testing products, Mercury QuickTest Professional™ and Mercury WinRunner®, to deliver the industry’s most complete solution for functional test, graphical user interface (GUI) test, and regression test automation — with support for practically every software application and environment.
		Mercury Service Test™ enables quality assurance teams to conduct both functional and performance tests for SOA services, ensuring that services meet both business and interoperability requirements.
	www.mercury.com /us/products/quality-center/functional-testing (310 words)

	GUI testing tool gains web app, tcl/tk support
		GUI testing tool gains web app, tcl/tk support
		FrogLogic is shipping a major new version of its testing tool for GUI-based applications.
		Similar to Squish/Qt and Squish/XView, the complete Tk widget set and its complete API are accessible from Squish Spy, and test scripts and actions can be recorded and replayed on all Tk controls, FrogLogic says.
	www.linuxdevices.com /news/NS8589032338.html (507 words)

	GUI Testing Checklist
		Section 3 - Validation Testing - Standard Actions
		Is the user required to fix entries which have failed validation tests?
		application (on a Windows for Workgroups platform) to be used in the initial screen validation testing phase.
	members.tripod.com /~bazman/checklist.html (2982 words)

	Pounder - Java GUI Testing Utility
		Pounder is a utility for automating Java GUI tests.
		Pounder differentiates itself from other utilities by allowing you to examine the results of a test run in source, while maintaining a separate GUI script that can be re-recorded if necessary.
		Some of the developers of the various GUI testing projects have gotten together and formed a mailing list to dicuss anything related to Java GUI testing.
	pounder.sourceforge.net (380 words)

	SourceForge.net: GUI Testing Tool
		Log in Need a SourceForge.net ID? Create account
		GTT is a GUI testing tool for for Java swing-based applications.
		In addition, GTT can be applied in a test-driven development style.
	sourceforge.net /projects/gtt (124 words)

Try your search on: Qwika (all wikis)