here's my choice of gems (my toolset):
# authentication
gem 'devise'
# http calls to external api's
gem 'restfulie' # or
gem 'http_party'
gem 'curb'
# performance management
gem 'newrelic_rpm'
on a recent project we used cucumber extensively for functional testing of our rails app using selenium webdriver to run it in the browser. all of us are convinced that it's a great tool, but there are many a things worth keeping an eye on otherwise it can lead to pain.
here i list top gotchas that we targetted and brought sanity back; but before i start, i'd like to point-out that these problems arise from the misuse of the freedom that cucumber gives us. cucubmer scenarios are plain english, and hence there are as many styles of writing scenarios as there are members on the team and that trickles down to steps as well.
here's what lspci tells me about my on-board graphics card and the xrandr (primitive command line interface to RandR extension) i executed to get my extended desktop on:
$ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) $ xrandr --output LVDS1 --auto --rotate normal --output VGA1 --auto --rotate left --left-of LVDS1
after endless attempts to get this working from the Display Settings (and then realizing that these options don't exist in there) Rajat helped me get this working.
If you are doing a deployment like: JBOSS_HOME/server/[config]/deploy/app.war where,
then you will not see a successful deployment till you instruct JBoss to follow these symlinks by tweaking your JBOSS_HOME/server/[config]/deploy/jboss-web.deployer/context.xml in this the Context element should have:
The ThoughtWorks University programme is over and I'm back in my home office Pune. It was an experience of a lifetime :) On the last day when the week-long project simulation was over we were doing a retrospective of the week that was and a group brainstorm came-up with these top 3 learnings from the activity.
The project simulation is supposed to be the most significant part of the University programme. Here we are expected to apply all the consulting skills, developer/analyst specific learnings, and agile practices that we learn through the programme. Trainers double-up as customers and are constantly watching us at work. It is set-up to give us a feel of how projects are done in ThoughtWorks.
