Have you tried step by step reporting Selenium Tests Framework? Grab free selenium step by step rreporting framework today!

Sunday, May 18, 2014

And we reached 1 million page views

thanks to all of you, testing enthusiasts :-)

Monday, May 12, 2014

Manual Testing Checklist


This check list comprises of use cases which can be applied to any web application. Thought there are many areas covered but no checklist could cover all the possible checks under the sun. I am sure you would find that many more use cases can be added to this list. So here is the list I could think of -

General Validation:

·                               ·         Verify page focus on a field on page load. For example login page would have cursor blinking in user name field
·         Tabbing may let you bring control on fields and submit form which are supposed to be disabled and. Don’t rely if a field “looks” disabled as it may be exercised using tab key
·         Verify navigation of toolbar, menu items and fields using tab key. Tab order should be left to right and up to down
·         Using tab key should not bring control on read only and disabled fields
·         When brining control on a field then it should stand out by cursor blinking in text box or highlighted field
·         The colors, fonts, and font widths should be as per the specified standard for the field and also for the field prompts and display text
·         Application font should render uniform across targeted browsers
·         The vertical scroll bars or horizontal scroll bars should  not appear unless required or explicitly mentioned


Sunday, December 22, 2013

Git Branching

If you use Git version control system then following commands may come handy for creating new branch for selenium tests -

Create new branch and commit tests/features to branch – 

git checkout –b <branchname>

Work on branch and commit

git commit –m “developed awesome feature” 

Merge branch to your local master

git checkout master

pull if remote master is updated and then merge the branch

git pull

If you want to avoid creation of merge commit then rebase else merge and push to remote master

git pull --rebase
 
git merge <branchname>
 
git push

Once done with branch then delete it

git branch –d <branchname>

If you want local branch to be pushed to git so that more than one committer could work on it

git push -u origin <branchname>
If origin does not have a <branchname>, then it is created on the fly. The -u tells git that you want to be able to easily push and pull changes to that branch in the future. This is needed when multiple committers are working on same branch
Now you can commit changes to remote local branch.

If another committer wants to use the <branchname>

git fetch origin
 
git checkout --track origin/<branchname>

The first command updates repository with the changes from the remote repository. The second command creates a local branch  that matches the origin/plugin branch and tells git that new committer wants to be able to easily push and pull from the branch on GitHub.

Deleting branch locally and from git 

git branch –d <branchname>
 
git push origin --delete <branch name>

In case there are conflicts when merging branch to master

  • Resolve conflicts manually
  • git commit
The commit message would be like this “””Merge branch 'branch name’””” and the push -
  • git push

ShareThis