Home » Archived » DSDP - Mobile Tools for Java (MTJ) » Mobile JUnit
| |
Re: Mobile JUnit [message #8703 is a reply to message #8691] |
Wed, 23 November 2005 16:39 |
Eclipse User |
|
|
|
Originally posted by: thomas.bailey.sonyericsson.com
Hi Minna,
You are quite right - it is MIDlet slanted. I realise it also assumes and
mandates UEI-ish (XEI wrapped as much as we like) behaviour is available..
execute test -> device downloads package -> device installs package ->
invokes package -> removes package. If you have, for example, a CDC
set-top box, this behaviour cannot be assumed. I guess some context
specific implementation is unavoidable whilst we have an "out-of-the box"
answer available for most scenarios.
I will address this in the UC.
/T
Minna Bloigu wrote:
> Hi Thomas,
> the Mobile JUnit UC looked quite good.
> I would, however, like to see it in a more general level ie targeting the
> whole Java ME platform testing not just MIDlet based test cases. The
> description gives the idea that this UC would only enable testing of MIDlet
> enabled devices but we need to take into consideration that the application
> can be, in addition to a MIDlet, Applet, Xlet or the tradional static main()
> application. I think that this UC is a good strting point, but could be
> extended to target testing of all the Java ME platform application models.
> Rgds,
> Minna
|
|
|
Re: Mobile JUnit [message #8822 is a reply to message #8703] |
Wed, 30 November 2005 12:16 |
Fred Grott Messages: 96 Registered: July 2009 |
Member |
|
|
Keep in mind that J2MEUnit is MIDP slanted ie no reflection..
Thomas Bailey wrote:
> Hi Minna,
>
> You are quite right - it is MIDlet slanted. I realise it also assumes
> and mandates UEI-ish (XEI wrapped as much as we like) behaviour is
> available.. execute test -> device downloads package -> device installs
> package -> invokes package -> removes package. If you have, for example,
> a CDC set-top box, this behaviour cannot be assumed. I guess some
> context specific implementation is unavoidable whilst we have an
> "out-of-the box" answer available for most scenarios.
>
> I will address this in the UC.
>
> /T
>
>
> Minna Bloigu wrote:
>
>> Hi Thomas,
>
>
>> the Mobile JUnit UC looked quite good.
>> I would, however, like to see it in a more general level ie targeting the
>> whole Java ME platform testing not just MIDlet based test cases. The
>> description gives the idea that this UC would only enable testing of
>> MIDlet
>> enabled devices but we need to take into consideration that the
>> application
>> can be, in addition to a MIDlet, Applet, Xlet or the tradional static
>> main()
>> application. I think that this UC is a good strting point, but could be
>> extended to target testing of all the Java ME platform application
>> models.
>
>
>> Rgds,
>> Minna
>
>
>
|
|
| |
Re: Mobile JUnit [message #562704 is a reply to message #8691] |
Wed, 23 November 2005 16:39 |
Eclipse User |
|
|
|
Originally posted by: thomas.bailey.sonyericsson.com
Hi Minna,
You are quite right - it is MIDlet slanted. I realise it also assumes and
mandates UEI-ish (XEI wrapped as much as we like) behaviour is available..
execute test -> device downloads package -> device installs package ->
invokes package -> removes package. If you have, for example, a CDC
set-top box, this behaviour cannot be assumed. I guess some context
specific implementation is unavoidable whilst we have an "out-of-the box"
answer available for most scenarios.
I will address this in the UC.
/T
Minna Bloigu wrote:
> Hi Thomas,
> the Mobile JUnit UC looked quite good.
> I would, however, like to see it in a more general level ie targeting the
> whole Java ME platform testing not just MIDlet based test cases. The
> description gives the idea that this UC would only enable testing of MIDlet
> enabled devices but we need to take into consideration that the application
> can be, in addition to a MIDlet, Applet, Xlet or the tradional static main()
> application. I think that this UC is a good strting point, but could be
> extended to target testing of all the Java ME platform application models.
> Rgds,
> Minna
|
|
|
Re: Mobile JUnit [message #562965 is a reply to message #8703] |
Wed, 30 November 2005 12:16 |
Fred Grott Messages: 96 Registered: July 2009 |
Member |
|
|
Keep in mind that J2MEUnit is MIDP slanted ie no reflection..
Thomas Bailey wrote:
> Hi Minna,
>
> You are quite right - it is MIDlet slanted. I realise it also assumes
> and mandates UEI-ish (XEI wrapped as much as we like) behaviour is
> available.. execute test -> device downloads package -> device installs
> package -> invokes package -> removes package. If you have, for example,
> a CDC set-top box, this behaviour cannot be assumed. I guess some
> context specific implementation is unavoidable whilst we have an
> "out-of-the box" answer available for most scenarios.
>
> I will address this in the UC.
>
> /T
>
>
> Minna Bloigu wrote:
>
>> Hi Thomas,
>
>
>> the Mobile JUnit UC looked quite good.
>> I would, however, like to see it in a more general level ie targeting the
>> whole Java ME platform testing not just MIDlet based test cases. The
>> description gives the idea that this UC would only enable testing of
>> MIDlet
>> enabled devices but we need to take into consideration that the
>> application
>> can be, in addition to a MIDlet, Applet, Xlet or the tradional static
>> main()
>> application. I think that this UC is a good strting point, but could be
>> extended to target testing of all the Java ME platform application
>> models.
>
>
>> Rgds,
>> Minna
>
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 26 08:17:24 GMT 2024
Powered by FUDForum. Page generated in 0.03319 seconds
|