I had a great time talking about TaaS and BDT at WCNGT conference in Bangalore on 11th July 2013.
Here is more information about the talks:
Integrated Testing in Enterprises using TaaS:
http://essenceoftesting.blogspot.in/2013/07/taas-in-wcngt-bangalore-and-agile-2013.html
The audio recording of the talk is available here.
The slides for the talk are available here.
TaaS is available on github and as a gem on rubygems.org.
http://essenceoftesting.blogspot.com/2013/07/building-right-regression-suite-using.html
The audio recording of the talk is available here.
The slides for the talk are available here.
Anyone heard or used the tool "thucydides"- for ATDD / BDD / BDT before?
Whats your review / thoughts on it? Any pros / cons?
http://www.thucydides.info/
https://github.com/thucydides-webtests/thucydides
From their website: "Thucydides is a tool that lets you use WebDriver-based unit or BDD tests to write more flexible and more reusable WebDriver-based tests, and also to generate documentation about your acceptance tests, including a narrative description of test, along with the corresponding screen shots, and also high-level summaries and aggregations of the test results."
I have pushed in the latest changes to WAAT to get over the limitation of not working in a pure https environment (http://essenceoftesting.blogspot.in/2011/06/waat-and-https.html).
The solution is creating a new type of plugin - called JS_SNIFFER.
This plugin requires the user of WAAT to do a little more work than before.
They need (to work with their development team) to figure out what JS script they need to invoke in the browser to get the URL of interest that is sent as a pure https request over the wire. WAAT then takes this request, and does the tag matching for you.
This generation of the JS script is a one-time effort - unless the way the tags are reported changes in the product. Then the test framework can work in a seamless fashion as before to test this is working consistently in an automated fashion.
Another advantage of this is that with this approach, we do not need to install jpcap or run the tests as a "super-user" - a restriction posed by the network packet capture library.
The WAAT_v1.5.0.jar is available on here (https://github.com/anandbagmar/WAAT/tree/master/dist) on github.
Similarly, I have also updated the WAAT-ruby gem (WAAT-1.5.0.gem). This gem is not yet pushed out to rubygems.org - as I am still testing it out. However, if you are interested, you can download it from here.
As usual, feedback / comments / suggestions most welcome!
