Some general questions via conversation with Google Summer of Code student

Harnum, Alan aharnum at ocadu.ca
Fri Jul 13 14:48:02 UTC 2018


Hi everyone,

I had my weekly check-in this today with Kunal Mohta, who’s working with me on this GSoC project: https://wiki.fluidproject.org/display/fluid/Google+Summer+of+Code+2018+with+the+Fluid+Project#GoogleSummerofCode2018withtheFluidProject-Buildaserviceforadaptivecontentandlearningsupports
Kunal asked some astute questions based on his work with building an API-based project in Kettle that I didn’t have particularly great answers for, so I thought I’d throw them out to the community to see what others think.


  1.  What’s the best way to keep track of internal dependencies (‘require’ statements focusing on your own project assets) in large multi-directory projects, especially in regards to not having to change things in a lot of places when you restructure. My thought on this was to have something like a per-directory “require” index.js file that can be referred to where necessary (I believe this is what GPII does).
  2.  When running many jqUnit tests at once from CLI (like the Kettle testing framework does, especially in an all-tests context), what’s the best way to pinpoint which one is failing and where in order to get more information? (I confess my current “solution” to this is often to pipe things to a text file, then search that file)

I’d be curious as to the thoughts of others about these questions.

ALAN HARNUM
SENIOR INCLUSIVE DEVELOPER
INCLUSIVE DESIGN RESEARCH CENTRE, OCAD UNIVERSITY

E aharnum at ocadu.ca<mailto:aharnum at ocadu.ca>
OCAD UNIVERSITY
100 McCaul Street, Toronto, Canada, M5T 1W1
www.ocadu.ca<http://ocadu.ca/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20180713/436058a0/attachment.html>


More information about the fluid-work mailing list