| || |
Content Testsing for Mobile Services
I am current developing a Content Test plan for a Mobile Web Server. I was hoping that you could help me with something. I am
currently looking at trying to define what constitutes bad content. What
structure will bad content take ? What can go wrong and how does a Mobile Web server effectively deal with bad content ? And for some good examples of what
constitutes bad content.
This is only at a high level for the moment. I am wondering if you know
of any documents or sites that exist that deal with this topic or could
you give me any pointer as to how I could approach this. Or do you know
of any good examples that exist which deal with bad content.
Re: Content Testsing for Mobile Services
Well, presumably you are creating page templates of some sort (either with a tool or manually) that the server utilizes.
I also presume you have some sort of automated adaptation of HTML/XML to whatever your mobile format is (WML, HDML, C-HTML, etc.)
What I am not able to presume: are you talking about the nature of your content or the presentation abilities of your content? In other words, content in general (such as "Gee, should I really include this in there?") or content in application (such as "I wonder if I just chuck this template and put my own code in").
I assume you mean the latter, but I am not sure. If that is the case, however, one element of your test plan is definitely going to be the content templates that are used. The other will be the adaptation mechanism. You are also going to be concerned in the test plan with the performance elements of the content - how much of there is it, how much of it needs to be transmitted at once, etc.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by diarmundo:
I am currently looking at trying to define what constitutes bad content.<HR></BLOCKQUOTE>
In general, based on what I said above, content that does not adhere to the template. Content that does not follow the adaptation scheme from, say, HTML to XHTML (or something along those lines).
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>What structure will bad content take ? What can go wrong and how does a Mobile Web server effectively deal with bad content ?<HR></BLOCKQUOTE>
The structure of bad content will be that which does not adhere to the standards you are using. For, for example, using WML or HDML will mean that any content that violates the "markup constraints" is bad. Usually what goes wrong is that the conversion into the mobile markup fails or is not done properly thus rendering some content hard-to-read, totally unreadable, or even completely invisible.
As far as how the Mobile Web Server handles the "bad content" (and I am still not sure we are on the same page with that) depends on the nature of the Web server - i.e., which one are you using? Also, knowing what markup you are going to use will be helpful.