I've found the cause of my problem but not a solution.
As I've noticed, the #assert has no effect in the test app.

If i modify the test job, then my external lib are added two time.
There are called from testrunner.js, and from tests.js. Unfortunalty
with the same path. Unfortunatly testrunner.js and tests.js are not
called from the same page. So i can etheir have one call correct, or
the other.

Then as Thron7 emtionned it, we can use the
testrunner::source-tests-script or testrunner::build-tests-script. But
if i do so, the script are not added called neither in tests.js or
testrunner.js

Is there another job that i can use to add my script file to the test app??

Regards

2011/3/23 Benjamin Dreux <[email protected]>:
> Hi
>
> I read the message [qooxdoo-devel] Qooxdoo Main Application with
> externed javascript files?
> Thron7 posted an answer there.
>
> I follow the explaination there.
> And now i's working BUT, there is always a but, the script i try to
> add are requested a second time with a different path.
>
> My 3rd party script now live in
> $app_home/source/resource/$app_name/script/$script_name
>
> I added in my test files an assert for each script needed
> /**
> * #assert($app_name/script/$script_name)
> **/
>
> And in the config.json of my app i add this job definition
>  "jobs":
>  {
>        "=test":
>        {
>          "add-script":[ {"uri":"resource/$app_name/script/$script_name"},
>                         
> {"uri":"resource/$app_name/script/$another_script_name"}]
>        }
>  }
> Then i run the test job with the generator
> And i copy the $app_home/test folder in my http server
>
> As i sayed the scripts are corretly loaded, and then after the test.js
> file is loaded, on of my 3rd party script is loaded with this path
> http://localhost/test/html/resource/$app_name/script/$script_name
>
> Did i make something wrong, one more time??
>
> Regards
>
> 2011/3/22 Benjamin Dreux <[email protected]>:
>> I think we've got something that need a some more explaintion in the wiki.
>> I will propose a text as soon as i fully understand what i'm missing.
>>
>> Ok so if i want to deploy the test folder in a simple http server to
>> run my tests. I need to add the script in the test folder, eg.
>> $app_home/test/resource/script
>>
>> Then i need to add a job definition, like this one
>>  "jobs":
>>  {
>>        "testrunner::build-tests-script":
>>        {
>>          "add-script":[ {"uri":"resource/script/script.js"}
>>        }
>>  }
>> And then run "./generator test"
>>
>> Then copy the test folder to my http server.
>> cp -r $app_home/test /var/www/
>>
>> And then the test, when it's running can use the defintions inside the
>> file script.js.
>> Is that the correct way of doing things ?
>>
>> I did it this way but i still can't use the definitions inside simple
>> js script. I surely miss something.
>>
>> in my last message, sorry for y english. I was asking if there is a
>> message when the generator add a script, to show that the add script
>> was made correctly. If not it could be nice, isn't it?
>>
>>
>> 2011/3/22 thron7 <[email protected]>:
>>>
>>>
>>> On 03/22/2011 06:33 PM, Benjamin Dreux wrote:
>>>> You were right. It wasn't clear to me to me that the path need to be
>>>> relative to the test index.html
>>>>
>>>> After correcting this error, it stil doesn't work.
>>>> My external script are no added to the $app_home/test/script folder.
>>>
>>> Well, it *is not* added anywhere, particularly not in any script folder.
>>> The browser retrieves it directly from the URI you specify. It could be
>>> anywhere.
>>>
>>>>
>>>> Do i need any message about script addition when i run my test job, is
>>>> that normal?
>>>
>>> Message?
>>>
>>> T.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Enable your software for Intel(R) Active Management Technology to meet the
>>> growing manageability and security demands of your customers. Businesses
>>> are taking advantage of Intel(R) vPro (TM) technology - will your software
>>> be a part of the solution? Download the Intel(R) Manageability Checker
>>> today! http://p.sf.net/sfu/intel-dev2devmar
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>
>>
>>
>> --
>> Benjamin Dreux
>> Analyste-Programmeur
>> Chaire de logiciel libre-Finance Social et solidaire
>> UQAM
>> Montréal
>>
>
>
>
> --
> Benjamin Dreux
> Analyste-Programmeur
> Chaire de logiciel libre-Finance Social et solidaire
> UQAM
> Montréal
>



-- 
Benjamin Dreux
Analyste-Programmeur
Chaire de logiciel libre-Finance Social et solidaire
UQAM
Montréal

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to