Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Revision as of 15:13, 26 June 2007 by aaumala (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

UI test criteria

From Wiki
Jump to: navigation, search

Here are some considerations to simplify some of the UI related SSfN test cases. Here are some of the most important topics of the S60 UI Style Guide, so this page attempts to be a "good enough" test set to get your application through the UI test cases.

Options Menu

  • Test that the first item in the options menu is the functionality that is triggered by the selection key / joystick press. This is usually open, select, change, etc.
  • Options menu items after the first one should be arranged by the frequency of use, most infrequent functions to the ned of the list.
  • Exit should be the last item in the options menu.
  • Check that your options menu reacts to your applicaitons states, meaning that there should not be any items in the options menu that cannot be triggered from the current application state. Such items need to be hidden - or they need to return a sensible error message.

Then, a content specific options menu (a menu that concerns only one focused list item) must not contain any general options menu item (such as open, exit, etc). It should only contain the few functions that can be triggered on the selected item.

- softkeyt, niiden käyttö: left ok, middle/joystick select, right back - menee takaisin yhen stepin hierarkiassa - jos ollaan päätasolla, tämä teksti on "exit" ja se sulkee koko applikaation etc. - editable forms with options menu / without options menu (the right key can be Done if left is Options, otherwise itse done - cancel). - selection keyn käyttö: select, open, never back or close

- settings: oikean terminologian käyttö, yhdenmukainen muiden applikaatioiden (system sw) kanssa. Settingsien otsikoiden kuuluu vastata sitä mitä ryhditään editoimaan. Saving settings: settings should be saved while the app is running vs. when app is closed down (ie. app restart must not be needed to get settings saved) esim muokkaat käytettävää IAP:ta ja uusi IAP otetaan käyttöön vasta seur känn kerralla.

- themejen toiminta on/off

- sovelluksen navigointi, vaikeaa vs intuitiivista (eli consistent with other apps). - by default all lists loop. scroll bar on the right hand side if the list spans over the screens edge. - editable componentit, kun editointi aloitetaan komponentin kuuluu olla oikeassa formaatissa (numeric, alphabetic), ei hyväksy invalidia inputtia. - esim: gridin käyttöä tabbed panella ei suositella. - UI komponenttien totuttua funktionaalisuutta ei rikota: multiselection vs radio button, oikeaoppinen käyttö!

- 6.7 information notet / query dialogit vastaamaan tarkasti kyseistä tilannetta (valittuna monta entryä: "Do you want to delete the selected entry? -> eli ei tiedä mihin netryyn monesta tässä viitataan).

161 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.