• 空间首页
• 空间管理
• 51Testing软件测试网
• 站点论坛
• 添加我的日志

我的最新日志

• java应用测试

  2008-8-25

  今天看到一个小短文，关于java应用测试的，感觉不错，与大家共同分享

  I am intrested to share my experience of testing with you, let me give you some basic procedures to follow mobile application testing in j2me.
  
  Application Conforms to Manifest File Attributes:
  1) Check the MIDlet Jar URL and JAR size from JAD file.
  
  2)Check the MIDlet-Name, MIDlet-Version, MIDlet-Vendor, MIDlet-n, MicroEdition-Profile and Micro-Edition Configurations fields are included in the manifest file Check the MIDlet-Name, MIDlet-Value and MIDlet-Vendor in the manifest file matches the value in the JAD file
  
  3) Installation testing:The application must install via OTA.
  Steps to conduct the test:
  Open the browser application of the
  device
  Type the URL of the application JAD file
  Connect to the typed URL
  Accept the installation of the application.
  
  4)Loading Screens: Loading screens must include some animated element to indicate to the user that the game hasn't frozen.
  When navigating from any screen to another, if the delay is more than about 3 seconds, then there should be a loading screen. This can vary depending on the situation.
  
  5)Text scrolling: In all help files if it contain more then 1 screen of text, there needs to be a clear indication to the user that the text can be scrolled through. This is usually done with a scroll bar on the height side of the screen or up/down arrow icons above & below the text block. In most cases text can be scrolled through with both the nav arrows & the 2/8 keys, but it's only required that the nav arrows function.
  
  6) Access all the main menu options as well sub menu's.
  
  7) Soft Keys: Whenever a softkey has any functionality it should be labelled properly with either text or an icon. When menu's change the softkey labelling should change appropriatly. Some small screen handsets don't have the room to support softkey labels.The softkey labels should remain as consistant as possible & match the softkey functionality in the phone OS whenever possible
  
  8) Interruption testing : Give a any kind of interruption
  through out the application like call interruption(incoming call,accepting the call,rejecting the call),SMS,MMS,alarm,timer,Blietooth and calender notification.
  
  9) Key pressing : Pressing red key and checking the behaviour of appliaction and rapidly pressing keys in loading screen and server communicating screens.
  
  10)Clamp shell or flip flop:Check application can handle clam shell or flip flop closing while loading,Main Menu,sub menus.
  
  11)Uninstallation testing : Check the application by deleting or removing from app manager.
  
  Few testcases should be added depends upon the carrier
  for T-mobile the carrier will provide TNS test plan.
  
  For nokia handsets follow the Nokia_Test_Criteria_for_Java_ME_Applications_v1_1_en from nokia forums
  
  
  For BREW platform follow the TRUE BREW TESTCASES provided by qualcomm.
  
  

  查看(39) 评论(0)

• 开始

  2008-7-02

  从今天开始准备写写日志了,我主要是做手机客户端的测试,希望和同行们多多交流

  查看(12) 评论(0)

我的主题

• 关于hopper
• 关于测试的个人总结