GeekArticles 
Testing Client/ServerTesting a Distributed Application Written in Embedded Windows CE
Author: stickyminds.com |
Published: 17th Aug 2005 |
Visited: 430 times |
Add CommentFiled in: Client ServerFor many of today’s smart devices, Windows CE is the new operating system of choice. Increasingly, developers are embedding Windows CE into many different types of appliances, including set-top boxes, gaming systems, bar code scanners, factory automation systems, and many more. As Windows CE has grown, so too has the need for off-the-shelf software development tools. Today there are many tools and off-the-shelf software kits on the market that save device designers significant amounts of time and effort throughout the device development process. Now, as more and more of these devices reach the final stages of development a new significant need has arisen: the need for testing tools. Now organizations can take advantage of a more cost- and time-effective solution for testing Windows CE-based smart devices; CEV (CEV) PassPORT. CEV PassPORT enables faster, and more accurate testing of a port of Windows CE to target hardware. The result of more than ten person years of development efforts, CEV PassPORT is has been thoroughly tested on every supported CPU platform and dozens of machine implementations.
Read Article Sponsored Links
Related Articles
• Swing Extreme Testing Book Review Swing Extreme Testing Book Review
Swing used to be a simple component offered as an add-on for Java. This plug-in can be used as a GUI (graphical user interface) to develop as an add-on for the Java application. It has the ability to emulate certain platforms eventually building a powerful applicat ...
• Swing Extreme Testing Swing Extreme Testing by Tim Lavers, Lindsay Peters
This book is a practical guide to automated software testing for extreme Java programming using Swing GUIs, with lots of ready-to-use real-life examples and source code for automated testing of the software components usually regarded as too hard ...
• Swing Extreme Testing - Outline of the Unit Test Outline of the Unit Test
The things we want to test are:
Initial settings:
The text field is empty.
The text field is a sensible size.
The Ok button is disabled.
The Cancel button is enabled.
The dialog is a sensible size.
...
• Swing Extreme Testing - Unit Test Infrastructure Unit Test Infrastructure
Having seen the broad outline of the test class and the UI methods needed, we can look closely at the implementation of the test. start with the UI Wrapper class and the init() and cleanup()method ...
• Swing Extreme Testing - The ShowerThread Class The ShowerThread Class
Since SaveAsDialog.show() blocks, we cannot call this from our main thread; instead we spawn a new thread. This thread could just be an anonymous inner class in the init()metho ...
• Swing Extreme Testing - The wasCancelled() Test The wasCancelled() Test
The first of our API tests is to check the wasCancelled() method. We will basically do three investigations. The first test will call wasCancelled()before the dialog has been cancelled. The second test will cancel the dialog and then call the method. In the third test we wil ...
• Swing Extreme Testing - The Data Validation Test The Data Validation Test
The Ok button of the SaveAsDialog should only be enabled if the name that has been entered is valid. A name can be invalid if it contains an illegal character, or if it has already been use ...
• Testing Multithreaded Java Code
In this interview from JavaOne 2008, Coverity chief scientist Andy Chou discusses why traditional unit tests often help in uncovering concurrency-related errors, and why a combination of static and dynamic analysis yields better results when testing multithreaded code.
...
