Does anyone mind if I get the unit tests to start running as part of
the checkintests target?
On 10 December 2014 at 16:18, Tom Chiverton wrote:
> On 10/12/14 14:21, Erik de Bruin wrote:
>>
>> [flexunit] Using the following settings for compilation:
>> [flexunit] FLEX_HOME: [c:\Jenkins\worksp
On 10/12/14 14:21, Erik de Bruin wrote:
[flexunit] Using the following settings for compilation:
[flexunit] FLEX_HOME: [c:\Jenkins\workspace\flex-sdk_test]
[flexunit] player: [flash]
Maybe that SDK hasn't been build with the new bits ?
Tom
Doh! First build the SDK, dude ;-)
All is well now, the tests run cleanly on the CI server.
EdB
On Wed, Dec 10, 2014 at 3:21 PM, Erik de Bruin wrote:
> And, like it's software development or something, stuff is not working
> on the CI machine. This is my ant 'stack trace':
>
> test-run:
>
And, like it's software development or something, stuff is not working
on the CI machine. This is my ant 'stack trace':
test-run:
[echo] Unit tests for
'c:\Jenkins\workspace\flex-sdk_test\frameworks\projects\apache'
[flexunit] Validating task attributes ...
[flexunit] Generating default val
Ah, and before I forget: I have added a new job to the build VM that
runs all tests on every commit or once daily (like the other jobs).
EdB
On Wed, Dec 10, 2014 at 2:17 PM, Erik de Bruin wrote:
> Hi,
>
> While working on the Promise class, I very much wanted to be able to
> use FlexUnit to te
