RocketModule - JavaScript http://rocket.local/categories/javascript en Backbone.js IS opinionated, or why is using nested models and collections in Backbone so hard? http://rocket.local/blog/backbonejs-opinionated-or-why-using-nested-models-and-collections-backbone-so-hard <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p><strong>Background</strong><br /> So after diving into the subject of nested models/collections in Backbone.js and being very frustrated at how Backbone doesn't handle them, I eventually discovered <a href="https://github.com/powmedia/backbone-deep-model/issues/14#issuecomment-15687361">a comment</a> by Backbone.js creator, Jeremy Ashkenas on GitHub:</p> </div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/backbonejs" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Backbone.js</a></div><div class="field-item odd"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div><div class="field-item even"><a href="/categories/nosql" typeof="skos:Concept" property="rdfs:label skos:prefLabel">noSQL</a></div></div></div> Fri, 04 Oct 2013 05:21:12 +0000 Caleb Gilbert 141 at http://rocket.local http://rocket.local/blog/backbonejs-opinionated-or-why-using-nested-models-and-collections-backbone-so-hard#comments Build your own JavaScript framework http://rocket.local/blog/build-your-own-javascript-framework <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>I've happily reached a significant milestone in the development of my project, finishing a foundational layer that by itself could be valid to open source at some point.</p> <p>Also:</p> <ul><li style="padding:0 0 10px 0;">In my last post I explained my reasons for passing on the current crop of JavaScript frameworks. This is a decision that I've been extremely pleased with, as I've managed to conceive/implement my own MVC/MVVM pattern for the project and the endeavor has pushed me much further into my JavaScript education.</li> <li style="padding:10px 0;">I have refactored the codebase from using 100% jQuery to about 80% raw JavaScript to 20% jQuery. It is nice to be able to know how to step outside of jQuery and/or deepen one's appreciation for what jQuery is doing under the hood. Also, if you've spent any time on jsperf.com at all you probably know that <a href="http://jsperf.com/comparing-jquery-and-native-js/11#bs-results">jQuery is much slower than raw JavaScript</a> for many things. When building an almost-entirely client-side app, speed starts to matter much more than when you have just a couple jQuery snippets on a page, and I want this app to be whip quick. It was a little ackward getting started with plain JS, but once underway I caught the hang of it fairly quickly, and the end result I'm definitely happy with.</li> <li style="padding:10px 0;">Currently, I am using <a href="https://developer.mozilla.org/en-US/docs/DOM/Storage">localStorage</a> for my data store, and it's been working great for development purposes - it's basically a mock mongoDB for me (I'm storing nested objects in localStorage using a small jQuery library called <a href="https://github.com/andris9/jStorage">jStorage</a>). I'm purposely putting off the server side of this application because I want to be able to use the Symfony 2.3 LTS release, which is scheduled for May as middleware between the client-side and mongoDB. The temptation to use node.js is strong, and arguably would be the most performant option, but the reasons for picking Symfony are probably obvious to any Drupal developer.</li> <li style="padding:10px 0;">Finally, don't forget - if you are using regex to parse the DOM, you're doing it <a href="http://stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags/1732454#1732454">brain-meltingly wrong</a>!</li> </ul><p>Cheers all, I'm off to <a href="http://sacdrupal.org/">DrupalCamp Sacramento</a> for the weekend.</p> </div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div><div class="field-item odd"><a href="/categories/drupal" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Drupal</a></div><div class="field-item even"><a href="/categories/symfony" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Symfony</a></div></div></div> Sat, 13 Apr 2013 02:46:46 +0000 Caleb Gilbert 129 at http://rocket.local http://rocket.local/blog/build-your-own-javascript-framework#comments Javascript Framework Redux http://rocket.local/blog/javascript-framework-redux <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p><em>Part II in a series of articles about an online web application I am working on. <a href="/blog/side-project-part-1-getting-started">Read Part I</a></em></p> <p>I'm am currently in the process of making my own web service, which will have a single-page-app (SPA) type of structure/interface. This is exactly the type of project that the bevy of JavaScript frameworks like Backbone.js, Angularjs, Ember.js, Knockout.js, and Meteor are build for, thus I've taken it for granted that I would use one of these frameworks as the client-side infrastructure for my app. After much review and fiddling around it turns out that I will not be using one of them. At least not for now. Below are some of reasons why <em>(note these reasons may not apply to you, you may rightly decide that a Javascript framework is a great choice for your project(s) - these are one person's opinions only)</em>:</p> <h3>Using any of the frameworks requires more commitment from my code base than I want to give right now</h3> <p>One of my biggest surprises/disappointments after spending a lot of time with Backbone.js and Angularjs was realizing that my (imho) perfectly awesome JavaScript/jQuery foundation layer, which I just slaved over creating, would not only have to be modified - it would have to be thrown out the window. This is because none of these frameworks are a container for your JavaScript - they are a replacement for it. Sure you might use a little bit of JavaScript/jQuery within any one of the frameworks, but overall you'll be doing-Backbone, or doing-Angular, or doing-Ember, or whatever. It's even common advice for Angular experts to tell newbies to not use jQuery at all while they are getting started, so that they can learn the 'Angular way'. Thanks, but no thanks.</p> <p>I don't want to abandon my universally usable and performant JavaScript/jQuery that I can take and integrate easily into almost anything (well almost anything but these frameworks, apparently). Maybe in the future as one of the JS frameworks becomes more mature and dominant I will reconsider. Honestly, I think a platform would have be as ubiquitous as jQuery has grown to be, for me to volunteer myself for platform lock-in on the level these frameworks require now.</p> <h3>I want to continue building my expertise in JavaScript/jQuery themselves and don't want to have it abstracted away from me</h3> <p>This is a big one for me. I can do what needs to be done with JavaScript, even reasonably well on a case by case basis. But I want to really master it. I don't want to just know Angular, or Backbone. I want to come up with solutions for the real-world, big-picture DOM/JS obstacles that I run into, presumably like the makers of the Javascript frameworks did. I want to eventually have the knowledge that I *could* make my own framework. And at that point, even if I decide to use someone else's framework I will have much more appreciation for my choice, and I will have more knowledge for how to leverage it.</p> <h3>Who are the frameworks a good choice for?</h3> <p>Don't get me wrong I am really glad I spent the time I did looking into Backbone.js and Angularjs (I actually looked at others, but I spent the most time with Backbone and Angular). They are demystified for me now, and there are a lot of good bits, patterns, and big-picture issues that I'm more informed about now than I was previously. I can easily imagine that someone who isn't a JavaScript expert and who just wants to commit to learning the idiosyncrasies of one of the frameworks can build some really great stuff. I can also imagine that true JavaScript masters might be taking their knowledge and one of these frameworks to bring their projects to an even higher level of organization and efficiency (though I'd actually be interested in hearing from the John Resigs of the world regarding their thoughts on current framework implementations).</p> </div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div><div class="field-item odd"><a href="/categories/drupal" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Drupal</a></div><div class="field-item even"><a href="/categories/jquery" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Jquery</a></div></div></div> Mon, 01 Apr 2013 18:06:12 +0000 Caleb Gilbert 128 at http://rocket.local http://rocket.local/blog/javascript-framework-redux#comments A Side Project: Part 1, Getting Started http://rocket.local/blog/side-project-part-1-getting-started <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p><em>"A Side Project" is a series of articles about an online web application I am working on. In Part 1 I share some of the thoughts and motivations which brought me to starting this project in the first place.</em></p> <p><img src="http://highervisibilitywebsites.com/files/newnold.jpg" alt="" style="float:right; margin: 0 0 0 .9em;" /><br /><strong>The seed for what is new, has some old roots</strong><br /> In 2005 I became involved with <a href="http://drupal.org">Drupal</a> after discovering it in the course of working on an ambitious <em>side project</em> of mine. It was a discovery that would change my life, professionally and otherwise, much for the better. Ironically, the very thing, which got me into Drupal in the first place (e.g., online side projects) had became one of the unfortunate casualties in more recent years as my professional Drupal activities increased. Sure, I had little projects - went to meetups, cons, made some patches here, contributed this there - but building my own online site/service from the ground up with the intention/hope of achieving something big, that went by the wayside.</p> </div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/drupal" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Drupal</a></div><div class="field-item odd"><a href="/categories/web-apps" typeof="skos:Concept" property="rdfs:label skos:prefLabel">web apps</a></div><div class="field-item even"><a href="/categories/saas" typeof="skos:Concept" property="rdfs:label skos:prefLabel">SaaS</a></div><div class="field-item odd"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div></div></div> Tue, 19 Mar 2013 05:17:11 +0000 Caleb Gilbert 126 at http://rocket.local http://rocket.local/blog/side-project-part-1-getting-started#comments Drupal security: video example of user account hijacking with XSS http://rocket.local/blog/drupal-security-video-example-user-account-hijacking-xss <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded">In this short screencast a variety of security holes are shown, as well as some malicious things which are made possible due to these lapses. We'll take a walk-through of two security issues showcased in the <a href="http://crackingdrupal.com/content/drupal-vulnerable-module">vulnerable.module</a>, as well as two other exploits which I put together: <ul><li>User account hijacking via cookie/session XSS thievery</li><li>User account hijacking via password-changing-inline-XSS</li></ul><div style="text-align:center;"> <div style="width:300px; margin-left:auto; margin-right:auto;"> <a href="javascript:playerPopUp('&lt;?php print base_path() . path_to_theme() ?&gt;/assets/drupal_security.html','900','601')"><img src="&lt;?php print base_path() . path_to_theme() ?&gt;/assets/drupal-security.png" alt="" /></a> </div> </div> <br />It's worth noting that in the screencast we demonstrate security exploits in the context of a Drupal installation which uses custom code (e.g., the examples in the video do not represent actual vulnerabilities in Drupal core). Likewise, these exploits and security holes potentially apply to any web site, Drupal or not, which accepts user input.<br /><br /><strong>Links</strong><br /><a href="http://crackingdrupal.com/">Cracking Drupal</a> (also, <a href="/improving-your-drupal-sites-security-cracking-drupal-review">my review</a>)<br /><a href="http://drupal.org/writing-secure-code">Drupal.org: Writing secure code</a><br /><a href="http://www.xssed.com/xssinfo">xssed.com</a></div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/drupal" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Drupal</a></div><div class="field-item odd"><a href="/categories/security" typeof="skos:Concept" property="rdfs:label skos:prefLabel">security</a></div><div class="field-item even"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div><div class="field-item odd"><a href="/categories/xss" typeof="skos:Concept" property="rdfs:label skos:prefLabel">xss</a></div></div></div> Tue, 02 Mar 2010 16:38:39 +0000 Caleb Gilbert 98 at http://rocket.local http://rocket.local/blog/drupal-security-video-example-user-account-hijacking-xss#comments Simple cross-browser Xdebug helper. Session starter and stopper, no add-ons needed. http://rocket.local/blog/simple-cross-browser-xdebug-helper-session-starter-and-stopper-no-add-ons-needed <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p><img src="/files/xdebug-logo2.png" style="display:inline;margin:5px 15px 3px 0pt;float:left;" alt="" />During a recent browser upgrade I found myself stuck in a bit of a corner. The Firefox add-on I had been using, Xdebug Helper, was discontinued, and the supposed replacement add-on for it didn't work correctly.</p> <p>Since the functionality of this now-defunct add-on made my life a lot easier (e.g., don't have to manually append/strip '?XDEBUG_SESSION_START=default' in my browser all day long to start/stop debugging sessions) I took it upon myself to keep this functionality and perhaps get rid of yet-one-more-add-on (which pays off when upgrade time comes).</p> <p>In all their simplicity, here are two bookmarklets you can use to start and stop a Xdebug session in your browser of choice. Note that if you are using a custom proxy key value then you'll need to change the '=default' part in the bookmarklet to '<code>=YourProxyKey</code>'.</p> <p><strong>The 'start session' bookmark</strong><br /><a href="javascript:(function(){location.href=location.href+'?XDEBUG_SESSION_START=default';})();">Save this bookmark</a> and then all you need to do to start a debugging session (assuming that you have Xdebug setup correctly and a breakpoint set in your code, of course) is to select the bookmark. I chose to put my bookmarks in the Toolbar at the top of window to make it even easier to get to. Also, just for the sake of posterity here is the code for the bookmark.<br /><code>javascript:(function(){location.href=location.href+'?XDEBUG_SESSION_START=default';})();</code></p> <p><strong>The 'stop session' bookmark</strong><br /><a href="javascript:(function(){var currentUrl=location.href;var gotoUrl=currentUrl.replace('?XDEBUG_SESSION_START=default','');document.cookie='XDEBUG_SESSION=default;expires=Fri, 3 Aug 2001 20:47:11 UTC;host=none;path=/';location.href=gotoUrl;})();">Save this bookmark</a> and put it next to your 'start session' bookmark. When you're done with your session, simply click this bookmark and viola. Again, here is the code:<br /><code>javascript:(function(){var currentUrl=location.href;var gotoUrl=currentUrl.replace("?XDEBUG_SESSION_START=default","");document.cookie='XDEBUG_SESSION=default;expires=Fri, 3 Aug 2001 20:47:11 UTC;host=none;path=/';location.href=gotoUrl;})();</code></p> </div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/drupal" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Drupal</a></div><div class="field-item odd"><a href="/categories/php" typeof="skos:Concept" property="rdfs:label skos:prefLabel">php</a></div><div class="field-item even"><a href="/categories/xdebug" typeof="skos:Concept" property="rdfs:label skos:prefLabel">xdebug</a></div><div class="field-item odd"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div></div></div> Mon, 01 Feb 2010 17:54:16 +0000 Caleb Gilbert 97 at http://rocket.local http://rocket.local/blog/simple-cross-browser-xdebug-helper-session-starter-and-stopper-no-add-ons-needed#comments Improving your Drupal site's security: Cracking Drupal review http://rocket.local/blog/improving-your-drupal-sites-security-cracking-drupal-review <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>If you're a Drupal professional, you owe it to yourself and your clients to internalize the lessons and techniques inside <a href="http://www.amazon.com/gp/product/0470429038?ie=UTF8&amp;tag=aaronwinborn-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0470429038">Cracking Drupal: A Drop in the Bucket</a>. This is true because, statistically, any insecurities in one's site are many times more likely to be introduced by one's own custom theming/modules than by Drupal core. The book mentions the audit of a high-profile Drupal site that uncovered 120 security issues, of which the vast majority were found in the customized theme layer! (much more than from contrib/custom modules even)</p> <p>There are many good things to choose from, but for me the best thing about Cracking Drupal is that I finally have a definitive one-stop place to go for information about Drupal security: what to watch out for, how to test it, best practices, worst practices. It's all there.</p> <p>Finally, keep in mind that just reading this book will not of itself make your site more secure. I've had to re-read certain things a few times before it sunk in all the way. A process helped along even more by downloading the vulnerable.module, the module the book uses for many of its examples, and testing out the examples inside of it for a few hours.</p> <p>Many thanks to <a href="http://drupal.org/user/36762">greggles</a> for putting this together for the Drupal community. For another review of Cracking Drupal see <a href="http://aaronwinborn.com/blogs/aaron/site-hacked-read-cracking-drupal?page=35">Aaron's write up of it</a>.</p> </div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/drupal" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Drupal</a></div><div class="field-item odd"><a href="/categories/security" typeof="skos:Concept" property="rdfs:label skos:prefLabel">security</a></div><div class="field-item even"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div></div></div> Fri, 31 Jul 2009 18:58:41 +0000 Caleb Gilbert 89 at http://rocket.local http://rocket.local/blog/improving-your-drupal-sites-security-cracking-drupal-review#comments Drupal Acceptance/QA Testing with Selenium - Screencast http://rocket.local/blog/drupal-acceptanceqa-testing-selenium-screencast <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><strong>Background</strong><br /> For the past 6 months I've been lucky to be part of the development team for the newly launched <a href="http://yoursphere.com/">Yoursphere.com</a>, a Drupal-powered social networking site which "provides one of the safest online destinations for youth ages 9 through 18 to interact*". To say that Yoursphere is the most customized Drupal site I've worked on would be quite an understatement. One example of that, and subject of this article, the user registration system went from the standard single page - to one which uses 4 unique user creation forms which are integrated within several possible 'registration flows'. The most complex of these involves two of the user creation forms, 8 total screens and third-party identity verification. <br /><br /> Besides being an opportunity to get to know <a href="http://api.drupal.org/api/function/hook_user/5">hook_user</a> real well, at the end of creating this system we were left with a larger-than-normal nightmare of, "Wow, I wonder if my new small change just exploded the entire registration system for the site. Hmmmmmm." <br /><br /><strong>Deciding on acceptance testing / Selenium</strong><br /> Faced with how to automate testing of these screens and use case, combined with limited time to implement the testing framework, a method of <a href="http://en.wikipedia.org/wiki/Acceptance_testing">acceptance testing</a> (using <a href="http://selenium.openqa.org/">Selenium</a>) was opted for instead of <a href="http://en.wikipedia.org/wiki/Unit_testing">unit testing</a> (e.g., using Simpletest) for several reasons (though perhaps in the future we'll have both unit and acceptance testing implemented): <ul><li>Facilitate testing of the registration system by non-developers</li> <li>There are registration screens which involve third-party interaction/functionality which cannot be unit-tested by us</li> <li>Selenium opens the possibility of testing the registration system across multiple browsers</li> <li>Seeing a browser step through all the registration steps just like a real person would do (except more quickly) is just so cool and offers a unique piece of mind about the integrity of the registration system</li></ul><strong>Selenium in action</strong><br /> When I <a href="http://highervisibilitywebsites.com/researching-drupal-and-acceptance-testing-or-where-simpletest-seems-fall-short">last wrote about Selenium</a>, I was trying to find an easy way to get Selenium RC to work *easily*, meaning without having to install a PEAR extension and/or PEAR itself. After (much) more research I can report conclusively that there is no *easy* way to get Selenium RC working, which in all honestly puts it outside my scope of interest, as I'm sure it would for most of the Drupal community. <br /><br /></div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/drupal" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Drupal</a></div><div class="field-item odd"><a href="/categories/selenium" typeof="skos:Concept" property="rdfs:label skos:prefLabel">selenium</a></div><div class="field-item even"><a href="/categories/acceptance-testing" typeof="skos:Concept" property="rdfs:label skos:prefLabel">acceptance testing</a></div><div class="field-item odd"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div></div></div> Mon, 06 Oct 2008 02:38:29 +0000 Caleb Gilbert 78 at http://rocket.local http://rocket.local/blog/drupal-acceptanceqa-testing-selenium-screencast#comments Researching Drupal and acceptance testing. Or where Simpletest admits it falls short. (so what'd we gonna do about it?!) http://rocket.local/blog/researching-drupal-and-acceptance-testing-or-where-simpletest-admits-it-falls-short-so-whatd-we-gonna-do-about-it <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p><em>(Since writing this article I've posted a <a href="http://highervisibilitywebsites.com/drupal-acceptance-qa-testing-selenium-screencast">newer article about Selenium here</a>)</em></p> <p>Based upon my recent research, there seems to be a sentiment in the Drupal-community-at-large (an undefinable thing to be sure) of, 'there's no need to look any further than simpletest for any testing needs' (unit, integration, acceptance, etc). This is counter to simpletest's <a href="http://simpletest.org/api/">own documentation</a> (bottom of page) which explicitly suggests to look for other alternatives for acceptance testing.</p> <p>After Googling to death 'selenium rc drupal', 'selenium rc php', etc I realized that almost no one seems to be implementing <a href="http://selenium-rc.openqa.org/">Selenium RC</a> within their Drupal workflows.</p> <p>Scratching my head at this I decided to figure out 'why' by doing an exhaustive search of all things Simpletest and found that it does indeed have <a href="http://www.lullabot.com/articles/introduction-unit-testing">support for making acceptance tests</a> (see bottom of article) - BUT - and it's a big but - there's no javascript support.</p> <p>So I started tracking down how the Drupal community plans to deal with the lack of JS support in Simpletest, and stumbled upon <a href="http://drupal.org/node/237566">this effort to get some kind of JS testing framework into Drupal 7 head</a>, which if I read things correctly appears to be more about unit testing than UI/acceptance testing. So the current Drupal roadmap for the latter doesn't seem to exist. (anyone have ideas/links to things related UI/acceptance testing for Drupal that I might have overlooked? <strong>UPDATE</strong>: Just found <a href="http://groups.drupal.org/node/9511">this link</a>, but also seems to be more on the unit testing side and it's currently seems to be inactive)</p> <p>At the moment I'm left wishing that getting Selenium RC to work wasn't so painful (it requires installing PHPUnit, which in-turn requires installing a PEAR extension, which for many requires installing PEAR itself).....or to put it another way....currently I'm feeling stuck between tackling something which does what I want but which isn't embraced (Selenium or acceptance testing) by the larger Drupal community, or else tackling something (Simpletest) which is supported by the larger Drupal community but doesn't offer the level of functionality I'm looking for.</p> <p>Wondering how I can help.</p> <p>Related articles:<br /><a href="http://groups.drupal.org/node/11186">Selenium and Drupal</a><br /><a href="http://groups.drupal.org/node/10107">Unit VS UI Testing</a><br /><a href="http://groups.drupal.org/node/9511">Develop an automated javascript testing framework</a></p> </div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/drupal" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Drupal</a></div><div class="field-item odd"><a href="/categories/selenium" typeof="skos:Concept" property="rdfs:label skos:prefLabel">selenium</a></div><div class="field-item even"><a href="/categories/simpletest" typeof="skos:Concept" property="rdfs:label skos:prefLabel">simpletest</a></div><div class="field-item odd"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div></div></div> Thu, 21 Aug 2008 18:12:04 +0000 Caleb Gilbert 77 at http://rocket.local http://rocket.local/blog/researching-drupal-and-acceptance-testing-or-where-simpletest-admits-it-falls-short-so-whatd-we-gonna-do-about-it#comments jQuery UI 1.5 and jQuery Enchant 1.0 alpha work with Drupal 6! http://rocket.local/blog/jquery-ui-15-and-jquery-enchant-10-alpha-work-drupal-6 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>The jQuery team has just released an alpha of <a href="http://jquery.com/blog/2008/02/08/jquery-123-air-namespacing-and-ui-alpha/">jQuery UI 1.5 and jQuery Enchant 1.0</a>, both of which will work with Drupal 6, as it is stated that the minimum requirements for the alphas are identical to the version of jQuery that ships with Drupal 6!</p> <p>Some links to help you get your tinker on:</p> <p><b>Download</b></p> <ul><li><a href="http://jqueryjs.googlecode.com/files/jquery.ui-1.5a.zip">jQuery UI 1.5 (Alpha)</a> (Requires jQuery 1.2.3 or higher)</li> <li><a href="http://jqueryjs.googlecode.com/files/jquery.enchant-1.0a.zip">jQuery Enchant 1.0 (Alpha)</a></li> </ul><p><b>Demos</b></p> <ul><li><a href="http://ui.jquery.com/1.5a/demos/">jQuery UI 1.5 (Alpha)</a></li> <li><a href="http://ui.jquery.com/enchant/1.0a/demos/">jQuery Enchant 1.0 (Alpha)</a></li> </ul><p><em>[Note: even if the jQuery version requirements for UI and Enchant change at some point before the final release, rest assured that someone in the Drupal community is sure to make an <a href="http://drupal.org/project/ui">upgrade path</a> available] ;-)</em></p> </div></div></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Categories:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/categories/drupal" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Drupal</a></div><div class="field-item odd"><a href="/categories/jquery" typeof="skos:Concept" property="rdfs:label skos:prefLabel">Jquery</a></div><div class="field-item even"><a href="/categories/ajax" typeof="skos:Concept" property="rdfs:label skos:prefLabel">AJAX</a></div><div class="field-item odd"><a href="/categories/ahah" typeof="skos:Concept" property="rdfs:label skos:prefLabel">AHAH</a></div><div class="field-item even"><a href="/categories/javascript" typeof="skos:Concept" property="rdfs:label skos:prefLabel">JavaScript</a></div></div></div> Sun, 10 Feb 2008 18:33:08 +0000 Caleb Gilbert 69 at http://rocket.local http://rocket.local/blog/jquery-ui-15-and-jquery-enchant-10-alpha-work-drupal-6#comments