how to test a custom build bundle

Laurel A. Williams laurel.williams at utoronto.ca
Tue Sep 8 15:13:32 UTC 2009


The custom build tool allows you to select various infusion modules and 
download a custom bundle (a zip file containing either a source or 
minified js file and all accompanying required files). How do we test 
that the downloaded bundle contains the infusion components that we want 
(and does not contain the components we do not want).

Here are some options we have discussed so far:

1) Open the zip file and check for the appropriate directories which are 
related to the infusion modules you selected. Also ensure that 
components that were not selected are not included in the directories.

2) Do 1 and also do some sort of manual searching within the js file 
(minified) to ensure that components are  included/excluded as selected.

3) Do 1 and/or 2 and take the downloaded bundle and deploy it somewhere 
to test the existence of various components.

I'm wondering what method others in the community think of these 
techniques and to what degree do we need to test the downloaded bundle?

Laurel






-------------- next part --------------
A non-text attachment was scrubbed...
Name: laurel_williams.vcf
Type: text/x-vcard
Size: 269 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090908/ca6b4ee8/attachment.vcf>


More information about the fluid-work mailing list