Of course, there is no much fancy stuff,
You will notice that i removed the qooxdoo path variable to be able to
change it via a macro definition.
Plus the job definition
Cheers
{
"name" : "ifsr",
"include" :
[
{
"path" : "${QOOXDOO_PATH}/tool/data/config/application.json"
}
],
"export" :
[
"api",
"api-data",
"build",
"clean",
"distclean",
"fix",
"info",
"inspector",
"lint",
"migration",
"pretty",
"profiling",
"source",
"source-all",
"simulation-build",
"simulation-run",
"test",
"test-source",
"translation"
],
"default-job" : "source",
"let" :
{
"APPLICATION" : "ifsr",
//This avriable is now set via a macro definition
// "QOOXDOO_PATH" : "os.getenv(QOOXDOO_HOME)",
"QXTHEME" : "ifsr.theme.Theme",
"API_EXCLUDE" : ["qx.test.*", "${APPLICATION}.theme.*",
"${APPLICATION}.test.*", "${APPLICATION}.simulation.*"],
"LOCALES" : [ "en" ],
"CACHE" : "${TMPDIR}/cache",
"ROOT" : "."
},
//this was the solution to add some sort of mock
"jobs":
{
"testrunner::build-tests-script":
{
"add-script":[ {"uri":"../resource/ifsr/script/jshamcrest-source.js"},
{"uri":"../resource/ifsr/script/jsmockito-source.js"}]
}
}
// You only need to edit the remainder of this file, if you want to customize
// specific jobs, or add own job definitions.
/*
"jobs" :
{
// Uncomment the following entry to add a contrib or library to your
// project; make sure to adapt the path to the Manifest.json; if you are
// using a contrib: library, it will be downloaded into the path specified
// by the 'cache/downloads' config key
"libraries" :
{
"library" :
[
{
"manifest" : "contrib://SkeletonApplication/trunk/Manifest.json"
}
]
},
// If you want to tweak a job setting, see the following sample where
// the "format" feature of the "build-script" job is overridden.
// To see a list of available jobs, invoke 'generate.py x'.
"build-script" :
{
"compile-options" :
{
"code" :
{
"format" : false
}
}
}
}
*/
}
2011/3/30 thron7 <[email protected]>:
> Can you post your config.json?
>
> T.
>
> On 03/30/2011 03:08 PM, Benjamin Dreux wrote:
>> First thanks for your quick answers.
>>
>> Sorry for this sentence, i should i read myself before post it.
>> What I mean is, when i a definition for the job
>> testrunner::build-tests-script, in the script tests.js there is no
>> reference to the library i wanted to use.
>>
>> I looked at the the tests.js when i built with the add-script for the
>> job test. I've seen that the qx.$$loader.urisBefore should contain the
>> uri of the library.
>> Then i built with the key add-script in the
>> testrunner::build-tests-script job, and there is nothing being added
>> to the qx.$$loader.urisBefore.
>>
>> Do you understand why is this doesn't work?
>>
>> Regards
>>
>> 2011/3/30 thron7<[email protected]>:
>>>
>>>
>>> On 03/23/2011 03:59 PM, Benjamin Dreux wrote:
>>>> 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??
>>>
>>> No, the testrunner::* jobs you mention are the right places. The script
>>> should only show up in tests.js or tests-source.js, depending on the job
>>> you chose, not in testrunner.js.
>>>
>>> I don't get the sentence "the script are not added called...". Is there
>>> no reference to the external script file in the generated code? Or is it
>>> not loaded when you run the Testrunner in your browser? Scripts are not
>>> "called" anyway ...
>>>
>>> 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
>>>
>>
>>
>>
>
> ------------------------------------------------------------------------------
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> _______________________________________________
> 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
------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
