Difference between revisions of "JavascriptCompressionTesting"
(New page: <noinclude><big>OurWork < DevelopmentTeam < Priorities < </noinclude>JavascriptCompressionTesting {{JustTinyEditIcon| JavascriptCompressionTesting...) |
|||
| Line 16: | Line 16: | ||
** On the other hand, there are many useful Java tools we may want to be able to use...and Mac OS already has it installed | ** On the other hand, there are many useful Java tools we may want to be able to use...and Mac OS already has it installed | ||
** You'd probably want to distribute the Rhino [jar|http://www.mozilla.org/rhino/download.html] with the repo. | ** You'd probably want to distribute the Rhino [jar|http://www.mozilla.org/rhino/download.html] with the repo. | ||
| − | + | * Shelling out to the command line is probably how to go. | |
| − | + | * Even if this doesn't prove useful I'm curious to know how it worked. -[[User:Stephen Judkins|Stephen Judkins]] 23:51, 30 January 2008 (PST) | |
[[Category:DevelopmentTeam]] | [[Category:DevelopmentTeam]] | ||
</noinclude> | </noinclude> | ||
Revision as of 07:51, 31 January 2008
What (summary)
We want an automated test to make sure our javascript doesn't have invalid syntax that emerges when packed.
Why this is important
It is annoying to have to set $auPackJavascript = true; every time one wants to deploy new code. Setting javascript packing to false is useful to keep on during development.
DoneDone
If the javascript files contain a syntax error that causes decompression to fail, running "rake test integration" both show an error.
Steps to get to DoneDone
- Check to see how easy it is to get [Rhino|http://developer.mozilla.org/en/docs/Rhino_Shell] running on everyone's computer.
- Is it easy to install Java? If it seems like a too difficult process then forget about this entire task.
- On the other hand, there are many useful Java tools we may want to be able to use...and Mac OS already has it installed
- You'd probably want to distribute the Rhino [jar|http://www.mozilla.org/rhino/download.html] with the repo.
- Shelling out to the command line is probably how to go.
- Even if this doesn't prove useful I'm curious to know how it worked. -Stephen Judkins 23:51, 30 January 2008 (PST)
