banshee858 | 2 Jul 01:34 2008
Picon

TDD with WIndowsCE

Anyone have any tool recommendations for TDD with WindowsCE?  Thanks.

Carlton

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/testdrivendevelopment/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/testdrivendevelopment/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:testdrivendevelopment-digest <at> yahoogroups.com 
    mailto:testdrivendevelopment-fullfeatured <at> yahoogroups.com

<*> To unsubscribe from this group, send an email to:
    testdrivendevelopment-unsubscribe <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Anthony Williams | 2 Jul 09:24 2008
Picon

Re: TDD with WIndowsCE

"banshee858" <cnett858 <at> hotmail.com> writes:

> Anyone have any tool recommendations for TDD with WindowsCE?  Thanks.

For starters, build everything for desktop Windows as well as
WindowsCE, and use your "normal" TDD tools with the desktop build.

If your test framework is written in portable code (or has been ported
to WinCE), it should compile for CE anyway, in which case you can run
your tests either in the CE emulator or directly on the target
hardware. Boost Test runs on Windows CE, for example.

Anthony
--

-- 
Anthony Williams            | Just Software Solutions Ltd
Custom Software Development | http://www.justsoftwaresolutions.co.uk
Registered in England, Company Number 5478976.
Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/testdrivendevelopment/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
(Continue reading)

Andrew Badera | 2 Jul 13:18 2008
Picon

Re: Re: TDD with WIndowsCE

Ahhhh but then you're not really testing CE code if you build it on the
desktop ... .NET's Compact Framework != the desktop framework, and testing
the desktop version will not give you reliable results for the CE version.

I think even C++ suffers from the same issue here.

On Wed, Jul 2, 2008 at 3:24 AM, Anthony Williams <anthony_w.geo <at> yahoo.com>
wrote:

>   "banshee858" <cnett858 <at> hotmail.com <cnett858%40hotmail.com>> writes:
>
> > Anyone have any tool recommendations for TDD with WindowsCE? Thanks.
>
> For starters, build everything for desktop Windows as well as
> WindowsCE, and use your "normal" TDD tools with the desktop build.
>
> If your test framework is written in portable code (or has been ported
> to WinCE), it should compile for CE anyway, in which case you can run
> your tests either in the CE emulator or directly on the target
> hardware. Boost Test runs on Windows CE, for example.
>
> Anthony
> --
> Anthony Williams | Just Software Solutions Ltd
> Custom Software Development | http://www.justsoftwaresolutions.co.uk
> Registered in England, Company Number 5478976.
> Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL
>
>  
>
(Continue reading)

Brad Stiles | 2 Jul 14:26 2008
Picon

Re: Re: TDD with WIndowsCE

> "banshee858" <cnett858 <at> hotmail.com> writes:
>
> Anyone have any tool recommendations for TDD with WindowsCE?  Thanks.

If you are targeting the .NET Compact Framework, NUnitLite 
(http://easternhealingarts.com/Articles/softanswer.html) is based on a 
subset of NUnit's features, and is intended to be used as part of the 
project you are testing, as source code, rather than as a separate test 
runner.

Brad 

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/testdrivendevelopment/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/testdrivendevelopment/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:testdrivendevelopment-digest <at> yahoogroups.com 
    mailto:testdrivendevelopment-fullfeatured <at> yahoogroups.com

(Continue reading)

Kim Gräsman | 2 Jul 14:29 2008
Picon

Re: Re: TDD with WIndowsCE

Brad, Carlton,

On Wed, Jul 2, 2008 at 14:26, Brad Stiles <bradley.stiles <at> gmail.com> wrote:
>> "banshee858" <cnett858 <at> hotmail.com> writes:
>>
>> Anyone have any tool recommendations for TDD with WindowsCE?  Thanks.
>
> If you are targeting the .NET Compact Framework, NUnitLite
> (http://easternhealingarts.com/Articles/softanswer.html) [...]

That article was nice, but NUnitLite is available here:
http://www.nunitlite.com/

:-)

Cheers,
- Kim

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/testdrivendevelopment/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/testdrivendevelopment/join
(Continue reading)

Brad Stiles | 2 Jul 14:35 2008
Picon

Re: Re: TDD with WIndowsCE

Kim Gräsman <kim.grasman <at> gmail.com> wrote:

> Brad, Carlton,
>
> That article was nice, but NUnitLite is available here:
> http://www.nunitlite.com/

Stupid keyboard. :)

Actually, I was trying to point to this one: 
http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite.

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/testdrivendevelopment/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/testdrivendevelopment/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:testdrivendevelopment-digest <at> yahoogroups.com 
    mailto:testdrivendevelopment-fullfeatured <at> yahoogroups.com

(Continue reading)

Anthony Williams | 2 Jul 15:06 2008
Picon

Re: TDD with WIndowsCE

"Andrew Badera" <andrew <at> badera.us> writes:

> Ahhhh but then you're not really testing CE code if you build it on the
> desktop ... .NET's Compact Framework != the desktop framework, and testing
> the desktop version will not give you reliable results for the CE version.

That's true, but it's a good place to start. If you ensure your code
compiles for CE as well, you won't accidentally use a feature only
in the desktop version. Of course, things might behave subtly
differently, but that's less likely. If you *also* run your tests on
the target hardware or emulator (using NUnitLite, for example), then
you'll get the best of both worlds: fast TDD on the desktop, with
WinCE tests to ensure you still have the desired functionality on the
target. I've had good success doing this.

> I think even C++ suffers from the same issue here.

Certainly the Win32 desktop API has more functions than the Windows CE
API, but that's not a particular problem: any attempt to compile for
Windows CE will catch usage of missing functions.

Anthony
--

-- 
Anthony Williams            | Just Software Solutions Ltd
Custom Software Development | http://www.justsoftwaresolutions.co.uk
Registered in England, Company Number 5478976.
Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL

------------------------------------

(Continue reading)

Andrew Badera | 2 Jul 15:17 2008
Picon

Re: Re: TDD with WIndowsCE

You can't write code the compiles on the desktop that also compiles on the
device. The Compact Framework is a fairly narrow subset of the full
framework. That gets better with every version, but there continue to be a
number of features not available, or that function significantly
differently, have different signatures, etc. etc. etc. that compiling for
the desktop means porting the app.

On Wed, Jul 2, 2008 at 9:06 AM, Anthony Williams <anthony_w.geo <at> yahoo.com>
wrote:

>   "Andrew Badera" <andrew <at> badera.us <andrew%40badera.us>> writes:
>
> > Ahhhh but then you're not really testing CE code if you build it on the
> > desktop ... .NET's Compact Framework != the desktop framework, and
> testing
> > the desktop version will not give you reliable results for the CE
> version.
>
> That's true, but it's a good place to start. If you ensure your code
> compiles for CE as well, you won't accidentally use a feature only
> in the desktop version. Of course, things might behave subtly
> differently, but that's less likely. If you *also* run your tests on
> the target hardware or emulator (using NUnitLite, for example), then
> you'll get the best of both worlds: fast TDD on the desktop, with
> WinCE tests to ensure you still have the desired functionality on the
> target. I've had good success doing this.
>
> > I think even C++ suffers from the same issue here.
>
> Certainly the Win32 desktop API has more functions than the Windows CE
(Continue reading)

Brad Stiles | 2 Jul 15:28 2008
Picon

Re: Re: TDD with WIndowsCE

Andrew Badera <andrew <at> badera.us> wrote:

> You can't write code the compiles on the desktop that also compiles
> on the device. The Compact Framework is a fairly narrow subset of the
> full framework. That gets better with every version, but there
> continue to be a number of features not available, or that function
> significantly differently, have different signatures, etc. etc. etc.
> that compiling for the desktop means porting the app.

You must be doing some really funky stuff then.  When I'm working on a 
device app, I always use the method Anthony mentioned.  I target the CF 
for the entire codebase and run my unit tests as I develop.  Yes, the 
features of the CF framework are a subset of the full framework, but I 
have yet to see a method that functions "significantly differently" or 
which has a signature on the CF that is *not* present on the on the full 
framework.  I also have yet to be unable to do something on the CF that 
I can do on the full framework, even if the code itself wouldn't be the 
same as if I had access to those features.

'Course, maybe I'm not doing enough to have encountered those pain 
points yet.

Brad

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/testdrivendevelopment/
(Continue reading)

Andrew Badera | 2 Jul 15:57 2008
Picon

Re: Re: TDD with WIndowsCE

Remoting is a good example. It didn't exist in 1.0, don't think it did in
2.0, and it's handicapped in 3.5 as CompactWCF.

Another good example is when working with Symbol or other devices with their
own libraries that won't run on the desktop.

On Wed, Jul 2, 2008 at 9:28 AM, Brad Stiles <bradley.stiles <at> gmail.com>
wrote:

>   Andrew Badera <andrew <at> badera.us <andrew%40badera.us>> wrote:
>
> > You can't write code the compiles on the desktop that also compiles
> > on the device. The Compact Framework is a fairly narrow subset of the
> > full framework. That gets better with every version, but there
> > continue to be a number of features not available, or that function
> > significantly differently, have different signatures, etc. etc. etc.
> > that compiling for the desktop means porting the app.
>
> You must be doing some really funky stuff then. When I'm working on a
> device app, I always use the method Anthony mentioned. I target the CF
> for the entire codebase and run my unit tests as I develop. Yes, the
> features of the CF framework are a subset of the full framework, but I
> have yet to see a method that functions "significantly differently" or
> which has a signature on the CF that is *not* present on the on the full
> framework. I also have yet to be unable to do something on the CF that
> I can do on the full framework, even if the code itself wouldn't be the
> same as if I had access to those features.
>
> 'Course, maybe I'm not doing enough to have encountered those pain
> points yet.
(Continue reading)


Gmane