View source for SE401:Group32

{| align="right" width="20%"
| __TOC__ 
|}

==Project Information==
[[Image:Autobot_1680_new.jpg]]
:{|
!width="15%" align="right" |'''Category:''' 
|Distributed systems (SE)

|-
!width="15%" align="right" |'''Code:'''
|[http://www.ece.auckland.ac.nz/p4p/projects/detailsByCode/?code=32 32]

|-
!width="15%" align="right" |'''Supervisor:'''
|[mailto:ian-w@cs.auckland.ac.nz Dr. Ian Warren]

|-
!width="15%" align="right" |'''Second Examiner:'''
|[mailto:m.abhari@cs.auckland.ac.nz Dr. Morteza Biglari-Abhari]

|-
!width="15%" align="right" |'''Students:'''
|[mailto:sshe088@ec.auckland.ac.nz Sakura She] and [mailto:ssiv025@ec.auckland.ac.nz Sasindran Sivapalan]  
   
|-
!width="15%" align="right" valign="top" |'''Description:'''
|With the increase in mobile device complexity there is a need for more intricate applications to be developed for these devices. Consequently, automated testing on these mobile devices becomes apparent.  The testing we want to conduct consists of a mixture of usability testing, functional testing and non-functional testing (such as performance and memory).  Currently, typical testing processes are time consuming and not easily repeatable because testing is frequently done via black box testing by the user.  Error messages are also a problem as they are often unhelpful by not revealing the root cause of a problem.  Therefore, steps need to be taken to make good quality automated testing tools for mobile devices. The goal is to investigate development techniques that support automated testing on multiple mobile devices and decide on the best architecture for such a system.  Subsequently a generic testing tool can be developed which can be supported on diverse mobile devices.  The system should involve the server-side generating test scripts and sending them to various clients (mobile devices) on the client-side to be executed.  After each test script has completed a test report should be sent back to the server-side indicating the results of the test.  An in depth evaluation and critique should be conducted to guide future development in this area.  

|-
!width="15%" align="right" |'''Outcome:'''
|Produce a tool which supports automated testing on different mobile devices

|}

==Project Objectives==
Develop a tool:
*That supports functional and non-functional testing of mobile applications.
*That masks the heterogeneity of the differing mobile device platforms.
*That supports automation of test script execution.
*That generates concise test reports after each test script is executed.
*Incorporates minor usability heuristic checking into the tool (if time is available).

==Progress==
:'''Project Stage''': ''Final Report/Exhibition/Compendium''

===Notice Board===

====Before 5 September====
*Finished presentation preparation -> DONE
*Finished poster -> DONE

====Before 31 August====
*Finished evaluation section -> DONE
*Finished conclusions section

====Before Friday 15 August:====
*Research Evaluation methods -> DONE
*Conduct evaluation on Hermes -> DONE

====Before Sunday 3 August:====
*Flesh out kinds of commands we can test -> DONE

====Before 27 July====
*Finished Hermes design section -> DONE

====Before Friday 18 July:====
*XML schema -> DONE
*Test reports presentation  -> DONE

====Before Friday 11 July:====
*Revise scenarios -> DONE
**How we're going to express all these scenarios in XML -> DONE
*Implement fully the testing application i.e. simulate events on phone and send data back to PC -> DONE

====Before Monday 30 June:====
*Investigation of how to connect phone to computer via bluetooth and RMI -> DONE
*Investigation of coding XML schema -> DONE

Before Sunday 15 June:

*Investigation of cellphone acting as a server -> DONE
*Extract inner class of background processes application -> DONE
*Decompile jar files for source code -> DONE
*RMI implementation over bluetooth -> DONE

Before Tuesday 4 June:

*Demonstrate simulation of simple events on a J2ME application -> DONE

Before Sunday 25 May:

*Implement minimal protoypes in J2ME and .NET -> DONE

Before Friday 2 May:

*Come up with 3-4 project objectives -> DONE
*Develop 5-10 concrete scenarios -> DONE
*Research of the comparison of J2ME and .NET-> DONE

Before Monday 21 April:

*Finish wishlist -> DONE

Before Friday 18 April:

'''Sakura''' - Read first 7 readings -> DONE

'''Sasi''' - Read last 7 readings -> DONE

===Tasks===
*Research current technologies
**Client-server communication
**Testing on multiple devices
**Test script generation
**Test report generation

*[[SE401:Group32:Tool Wishlist|Tool Wishlist]]
*[[SE401:Group32:Tool Scenarios|Tool Scenarios]]
*[[SE401:Group32:Tool J2ME vs .NET|Technology Comparison]]
*[[SE401:Group32:Tool LOW-FI Prototype|LOW-FI Prototype]]
*[[SE401:Group32:Tool Investigation|Technology/Tool Investigation]]

*Implementation of tool
**Client-server communication
**Testing on multiple devices
**Test script generation
**Test report generation

===Meeting Times===
Friday - 3pm

===[[SE401:Group32:Meeting Minutes|Meeting Minutes]]===

===Concerns===
::''(If you have a reliable and concrete answer to some unanswered questions; post them under the question as a link)''

==Resources==

===Useful Links===
[http://java.sun.com/products/javadevice/overview.html Java Device Test Suite]

[http://www.testquest.com/index.cfm TestQuest Pro]

[http://www.useit.com/papers/heuristic/heuristic_list.html Ten Usability Heuristics]

[http://www.tometasoftware.com/J2Me_vs_Net_whitepaper.asp J2ME vs .NET]

[http://www.javaworld.com/javaworld/jw-05-2003/jw-0516-wireless.html?page=1 Javaworld comparison of J2ME and .NET]

[https://mermi.dev.java.net/howto.html J2Me RMI How-to]

===General References===