how to test a custom build bundle
michelle.dsouza at utoronto.ca
Wed Sep 9 13:48:52 UTC 2009
Where do we plan to test this? Are we going to test on everything in
the testing environments matrix? http://wiki.fluidproject.org/x/j4w7
If so, I'd think option 1 is good enough for most of the testing and I
would select a single environment and do option 3 there.
On 8-Sep-09, at 11:13 AM, Laurel A. Williams wrote:
> 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
> 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
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto
More information about the fluid-work