Jmeter is a well known open source performance/load testing tool and to be fair it does a lot of stuff really well. if you wants to do some quick performance testing without a whole lots of infrastructure around it then it is great.
I started out my task with jmeter with some objectives:
<li> A tool that i could integrate into a CI tool such as teamcity</li> <li> Meaningful graphs that could be easily interpreted by any one in the team</li> <li> Able to integrate the graphs into teamcity</li> <li> Able to monitor the performance of the website under test.
Sometime i would use my blog as a place to keep interesting stuff for future exploration.
I came across the chrome net internals today and i think it exposes a lot of useful information that might be useful to testers when testing a web application.
To access the chrome net internals, navigate to chrome://net-internals/ on a google chrome browser.
I would be spending some more time in the future exploring this but for now its back to work.
I have been working at this client where i am opportuned to use cucumber, watir-webdriver and i came across this problem today. The application i am testing is an e-commerce site and i am writing test for a page on which i click on an item and the item appears on the shopping basket area of the site.
My code look like
[code]
def select_item(item_name) @browser.li(:text => /#{item_name}/).link(:class_name => “addOptions”).click Watir::Wait.
I moved my blog from the blogger one to wordpress and i wanted to ensure that people that have bookmarked post on my old blog get redirected to the new one on wordpress as i wouldnt be update the old blog anymore.
I found a lot of effort by different people and all the stuff that was suggested using javascript didnt work for me, what i got was regardless of the page you are on my old blogger site, you would be redirected to my homepage on the wordpress site which is not very helpful.
Having just finished an engagement with a client where the development practices include kanban and BDD. Kanban for us meant that we give priority to work on the right side of the board. So as a tester, I would rather spend my time doing some manual testing on a story that is in the QA queue, than writing automated acceptance tests for a story in the queue for Acceptance Tests.