Logo

What's in my DNA today?

over 1 year ago | Yashashree Barve: Life is Beautiful !!

Around 4-5 years back, when I was a loyal reader of Times of India, I saw this advertisement of a new newspaper being launched. It read "What's BMC digging for? a) Water b) gold c) Petrol". It was so apt looking at the roads that are always dug by BMC for some reason or the other. I tried to give DNA a shot, and really fell in love with it. Today after 5 years, it has become a part of my life, and I really look forward to what's in the DNA today.

It brought in many concepts of Web 2.0 such as readers contributing to news, as well as opinions on latest happenings. It also has a separate edition for kids on sunday called YA! which my kids simply love.

DNA is celebrating its 5th anniversary, and enjoy a snapshot of the cartoons published over these 5 years !
Looking forward to a continued relationship with you DNA ! 

Agile NCR 2010

over 1 year ago | Shakti Choudhary: Smiling Assassin

Hi, Flashback: On 14th July 2010, my manager and my buddy asked me to join Agile NCR 2010 and my perception was ” OH MY GOSH, another conference!!” and also to make it more interesting, it was on a weekend and to make it more dramatic, my travel time to the location was 90 minutes. [...]

Tum...

over 1 year ago | Sukhpal Bhatti: life

Dil ki awazShayar ki shayari ho tum,Tumhare hone meinDuniya, gam, khushi sab ho jayein gum,Lehrati zulf hai ke chehre se hat-ti nahiDhadkan hai ke tumhe dekh ke ghat-ti nahi,Wo shaam ke doobte sooraj ke aasman si gehrayi liyeNazar se tumhari nazar hamari hat-ti nahi,Naino ki zuban ki koi rah nahi hotiDil ki dhadkan ki awaz nahi hoti,Gar hoti in sabki bhi koi kitabTum ab tak samajh gayi hoti... :-)

Easily add/remove Vim scripts

over 1 year ago | Ryan Kinderman: kinderman.net :

I like being able to easily add and remove Vim scripts, whether it's to try one out or easily upgrade to a newer version down the line. Since the directory structure of a script almost always follows the standard runtime directory structure, I simply wrote a script that adds each directory under $HOME/.vim/vendor to Vim's runtimepath, so that Vim includes the vendor directories in its script-searching behavior. That way, I can simply download something like rails.vim, which has files in autoload, doc, and plugin, and would be very annoying to remove manually, uncompress it into its own directory under $HOME/.vim/vendor, restart Vim, and the script is loaded. Removing the script is as easy as removing the directory under vendor and restarting Vim.

To add this behavior, simply put the following in your $HOME/.vimrc file:

let vendorpaths = globpath("$HOME/.vim", "vendor/*")

let vendorruntimepaths = substitute(vendorpaths, "\n", ",", "g")
set runtimepath^=vendorruntimepaths

let vendorpathslist = split(vendorpaths, "\n")
for vendorpath in vendorpathslist
  if isdirectory(vendorpath."/doc")
    execute "helptags ".vendorpath."/doc"
  endif
endfor

For the latest and greatest version of this code, refer to my vimrc.

Auto-saving sessions in Vim

over 1 year ago | Ryan Kinderman: kinderman.net :

Back when I used Textmate, I liked that you could save projects to a file so that you could quit Textmate and come back later, load the project file up, and have all the files and tabs set up and open the way you had them. Since switching to Vim, I've gotten the same functionality (and more!) using the :mksession command. One thing that's missing in Vim, however, is the ability to auto-save a session. There are a few add-ons that do this, but add a bunch of other functionality that I find unnecessary. Below is a little script I wrote that adds auto-saving sessions to Vim:

function! AutosaveSessionOn(session_file_path)
  augroup AutosaveSession
    au!
    exec "au VimLeave * mks! " . a:session_file_path
  augroup end
  let g:AutosaveSessionFilePath = a:session_file_path

  echo "Auto-saving sessions to \"" . a:session_file_path . "\""
endfunction

function! AutosaveSessionOff()
  if exists("g:AutosaveSessionFilePath")
    unlet g:AutosaveSessionFilePath
  endif

  augroup AutosaveSession
    au!
  augroup end
  augroup! AutosaveSession

  echo "Auto-saving sessions is off"
endfunction

command! -complete=file -nargs=1 AutosaveSessionOn call AutosaveSessionOn(<f-args>)
command! AutosaveSessionOff call AutosaveSessionOff()

augroup AutosaveSession
  au!
  au SessionLoadPost * if exists("g:AutosaveSessionFilePath") != 0|call AutosaveSessionOn(g:AutosaveSessionFilePath)|endif
augroup end

To begin auto-saving sessions, simply run:

:AutosaveSessionOn <session filename>

Your session will then be automatically saved to the given session filename when Vim exits. Also, if you have globals in your sessionoptions list, when you load the auto-saved session, auto-saving will continue to occur to that session file. To turn auto-saving to the session file off, run:

:AutosaveSessionOff

For the latest and greatest version, refer to my vimrc.

"Right thing all the time"

over 1 year ago | Riju Kansal: Riju's Thoughts Captured...

Doing the right thing all the time. Every minute, every day, thruout the year. This is the hidden meaning behind the saying - 'Right thing @ Right time'. When you do right thing all the time, automatically when right time comes, the results accelerate. People call it luck. :)

Experienced power of Automation Testing!

over 1 year ago | Riju Kansal: Riju's Thoughts Captured...

Recently I experienced a wonderful effect of Automation Test Suite. I think I'd like preserve this experience in the form of few words and share it with friends.


Present Scenario:
Cycle 3 Started beginning of this week.
The 26 Test Sets totalling 3000+ automated test cases started to be executed.
Test data was prepared as a pre-requisite by SME manual testing team.
The very first day of Cycle 3 execution the application which was nearing UAT completion, started crying.
23 Critical, High and Medium defects were logged the very first day.
The management lost confidence in the build.
No Go.

Scenario a couple of months back:
Automation suite creation in progress.
The scripts are failing due to problems within themselves.
The automation review process is identifying a lot of issues within scripts.
The naming conventions are not being followed completely.
No test data management strategy is documented.
Testing team starts estimating 100% manual regression cycle.
Management sees low confidence in automation testing.

How did the perspective change within a couple of months?
Results.

Business looks for results to accept success on ROI.
But someone in the top leadership had the "vision" to be patient and invest in building an Automation test suite. They accepted waiting and waiting for the build and review cycle of automation test suite, to be complete.

Recently, just on click of a button the 3000+ test cases drilled thru the huge complex application with a huge business value. Helping the leadership to decide quickly not to launch the product at this point in time, and wait for the desired quality in the product to be built.