We are going to test an application that will be used through Touch Screen PC's. We do not have any Touch Screen Machine with us but we are advised to use a browser called 'ICE' to test this application and we are told that application will behave same on ICE as with Touch Screen.
I wish to know: What would be General Check List for such Application & What should be the General Approach.
The approach would be the same as that of testing an app without a touch screen form of stimulus.
Hopefully the developer/vendor has adequately tested the touch screen app so that you don't have to test it. I think the only consideration you need give the touch screen are the known issues that should be documented in the release notes for it.
Thanks JP. Approach may be the same but there are few things that are troubling me (I haven't got the feel of the application yet as it is in the design phase):
1. We have to use IE in full screen mode and without any toolbar ('iexplore -k').
2. We are not supposed to use Mouse.
3. We will be using the normal keyboard in a way that it is similar to that of the Tocuh screen Machine.
Besides, there may be some compatibility and portability issues.
We are preparing ourselves to test this application but because of time pressure and such limitations, it will be a real challenge.
Originally posted by vivekkumar: 1. We have to use IE in full screen mode and without any toolbar ('iexplore -k').
2. We are not supposed to use Mouse.
3. We will be using the normal keyboard in a way that it is similar to that of the Touch screen Machine.
...it will be a real challenge.
<font size="2" face="Verdana, Arial, Helvetica">I agree. You've got a real challenge there.
Try thinking of it as two seperate test efforts. One to test the functionality of the application. You'll be doing this on your normal desktop and IE. The second effort is a compatibility issue. You've tested that all the functionality has worked in at least one situation, now all you have to do is verify that basic functionality still works on the new platform.
One thing you might want to rethink is the not using a mouse. A mouse is a pointing device you use to interact with things on the screen. When using a touch screen you are using your finger as the pointing device. There is no real difference.
For the most part, you can test as if you were on a touch screen when you are on a normal desktop. However, there are usibility issues when you are using only your finger on the touch screen. On the app I'm working on now we found out that we won't be able to use normal sized controls because fingers can't "click" on the little things like a mouse can. We also had a problem with the narrow vertical scroll bar. It was very difficult to reach on the touch screen. And that we found out in the first five minutes.
Another thought. Find out what the screen resolution is of the touch screens. Ours are not square like a regular monitor and the resolution can't be set near as high as a desktop. I'm going to try and set the size of the browser on the desktop to match what it will be on the touch screen so that when I'm on my normal PC I can get a feel for how things will be displayed to the end users with the touch screen.
Please keep us informed about how things progress. I'm very interested. It seems I'm in a very similar boat.
Thanks, Mark. I also thought of testing Functionality separately and then checking the compatibility and usability. However the same points that you mentioned later in your reply, will crop up like enter button could not be clicked or scroll bar could not be used. However i am trying to discuss with customer regarding the impact he can bear if any such thing is missed. In other words, these type of bugs may very well be taken up in Beta Testing, if customer is ready to plan Beta testing in Detail.