|
|
Boost Testing : |
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2006-10-24 12:13:01
Rene Rivera wrote:
> Mateusz Loskot wrote:
>> Stefan Slapeta wrote:
>>> Mateusz Loskot wrote:
>>>
>>>> Do you mean space on a Windows CE device/emulator,
>>>> for regression.py output?
>>>>
>>> Space for libs, executables, obj's etc.
>>> For my tests (2 configurations) I need about 13 GB.
>> Right. On my development machine, where Boost is
>> compiled I have a lot of space.
>> But only final dll/exe files will be copied to mobile device.
>
> There is one problem you'll have to figure out... The regression.py
> automates everything, which includes compiling and running of the tests,
> hence why Stefan mentions the disk space issue.
Ah, that's a detail I've missed.
Right, this may be a problem.
> In your case you are compiling the tests on one machine and running on another.
Exactly. The cycle is 1) compile 2) deply on a device 3) run
> So you need to make regression.py copy the tests binaries to the test machine and
> then copy back the results. Not sure how to do that though.
OK, that should be easy.
Generally, I need to change the regression.py script to only run tests.
> Anyone know how to make regression.py do remote testing?
Remote testing for Windows CE platform would need to be based on
platform-specific regression.py script.
There is a dedicated API (RAPI [1]) for operating device remotely, from
desktop.
Remote regression tests run for Windows CE may look as follows:
1. regression_wince.py script runs on desktop machine
2. The script uploads Boost binaries on WinCE device(using RAPI)
3. Execute regression tests runner on a device (using RAPI call
CeCreateProcess)
4. Download file(s) with regression tests results
5. Process tests results on desktop
6. Upload results on the Web
This scenario seems to be feasible using Python and Python port for
Windows CE [2].
[2] http://sourceforge.net/projects/pythonce
Cheers
-- Mateusz Loskot http://mateusz.loskot.net